Rekordbox is one of the worst pieces of software I have to interact with regularly, and it reminds me of others descriptions of IoT software/firmware.
"PRO DJ LINK" enables you to access rekordbox libraries (and load music files) remotely from other devices, whether that be on a computer or dedicated Pioneer/AlphaTheta hardware.
The vulnerability in question requires the attacker to be on the same local network as the instance of rekordbox and for the remote library feature to be enabled. Interested in the full writeup once it's released
Preach! I spent several hours this weekend trying to move my library between computers. So many popups and warnings telling me that I need to do something with no explanation of why. The docs are a mess. The library compatibility is a mess. Every few months they do something that fucks up libraries or makes them incompatible with some hardware. I just refuse updates now.
Rather than trying to make a new, shiny library, they should just release rekordbox 2.0, and then everyone would have a common lexicon to ask whether something is “rekordbox 2 compatible”. But instead we have this questionably compatible library plus as part of old, busted software that tries to brow best you into wrecking your old libraries.
I just use Claude to explain rekordbox to me now, and it is a bit more helpful than forums, though it also often gets confused from the conflicting advice/docs on the internet
They do not care, AlphaTheta is well down the enshittification road. They captured all the DJs, then they captured all the venues, and now they'll squeeze both for profits until a sufficient critical mass has built to trigger a collective switch away from them. At which point executive bonuses will be paid, investors will get their returns, and the PioneerDJ brand will be sold to an even scummier company to wring a few more dollars out of it.
I too also have a special place of hate for Rekordbox. However I'm somewhat confused by this vulnerability, isn't plug n play unauthenticated file access essentially a core feature of "PRO DJ LINK"? The security mitigation, and best practice, being to have the involved devices connected on a entirely private LAN. I've never tried connecting them to a "public" network.
The feature definitely does what it says it does, but I think that the mount is generally accessible outside the software may be where the “surprise” lies.
I definitely would not have used this feature on a public network or exposed the mount to the open internet as well.
You and crtasm both make an excellent point about where the problem lies. I suffered from a critical imagination failure by never considering the implications of running the link on anything other then a controlled and isolated network.
Truly terrible platform. I engineer DJ events and every single time there will be someone who had used either too new or too old version of rekordbox for the model of CDJ/controller the venue got in. This is seemingly random and totally undocumented. If I had hair I would have torn them out long time ago.
There are some DJs who lug their own Pioneer controllers with them. Precisely because they can make sure that their library will work! No other reason.
I dabbled with it for a while and hated how I couldn’t work with the library programatically. A few people found a way to decrypt the database (yes, it’s encrypted for obfuscation, rolls eyes) and manipulate it but it’s akin to brain surgery.
Comments
Rekordbox is one of the worst pieces of software I have to interact with regularly, and it reminds me of others descriptions of IoT software/firmware.
"PRO DJ LINK" enables you to access rekordbox libraries (and load music files) remotely from other devices, whether that be on a computer or dedicated Pioneer/AlphaTheta hardware.
The vulnerability in question requires the attacker to be on the same local network as the instance of rekordbox and for the remote library feature to be enabled. Interested in the full writeup once it's released
Preach! I spent several hours this weekend trying to move my library between computers. So many popups and warnings telling me that I need to do something with no explanation of why. The docs are a mess. The library compatibility is a mess. Every few months they do something that fucks up libraries or makes them incompatible with some hardware. I just refuse updates now.
Rather than trying to make a new, shiny library, they should just release rekordbox 2.0, and then everyone would have a common lexicon to ask whether something is “rekordbox 2 compatible”. But instead we have this questionably compatible library plus as part of old, busted software that tries to brow best you into wrecking your old libraries.
I just use Claude to explain rekordbox to me now, and it is a bit more helpful than forums, though it also often gets confused from the conflicting advice/docs on the internet
They do not care, AlphaTheta is well down the enshittification road. They captured all the DJs, then they captured all the venues, and now they'll squeeze both for profits until a sufficient critical mass has built to trigger a collective switch away from them. At which point executive bonuses will be paid, investors will get their returns, and the PioneerDJ brand will be sold to an even scummier company to wring a few more dollars out of it.
I too also have a special place of hate for Rekordbox. However I'm somewhat confused by this vulnerability, isn't plug n play unauthenticated file access essentially a core feature of "PRO DJ LINK"? The security mitigation, and best practice, being to have the involved devices connected on a entirely private LAN. I've never tried connecting them to a "public" network.
The feature definitely does what it says it does, but I think that the mount is generally accessible outside the software may be where the “surprise” lies.
I definitely would not have used this feature on a public network or exposed the mount to the open internet as well.
You and crtasm both make an excellent point about where the problem lies. I suffered from a critical imagination failure by never considering the implications of running the link on anything other then a controlled and isolated network.
Access to files in your rekordbox library yes, but this sounds like it may be allowing access to any file on your computer/USB stick.
Truly terrible platform. I engineer DJ events and every single time there will be someone who had used either too new or too old version of rekordbox for the model of CDJ/controller the venue got in. This is seemingly random and totally undocumented. If I had hair I would have torn them out long time ago.
For this exact case I have built https://chiph.art/en/project/2026/dj-usb-toolkit
The parity repair in the app should make the USB compatible with all CDJs because it makes both of the DBs identical.
I have also been able to repair the DBs that have been corrupted for example by disconnecting USB while Rekordbox is exporting to it.
I'm also just now building a website where you can send the DB repair requests for cases that need special attention.
I will make my DJ friends test this. Thank you.
Thank you!
Added repair service for Rekordbox USBs: https://chiph.art/en/dj-usb-tkit/repair
Do DJs just use whatever equipment is at the venue?
Don't they bring their own setup?
DJs are typically playing on promoter or venue provided equipment, which is usually industry standard of pioneer/AT.
Otherwise, they bring their own, especially if it’s anything custom or specific to their performance.
There are some DJs who lug their own Pioneer controllers with them. Precisely because they can make sure that their library will work! No other reason.
I dabbled with it for a while and hated how I couldn’t work with the library programatically. A few people found a way to decrypt the database (yes, it’s encrypted for obfuscation, rolls eyes) and manipulate it but it’s akin to brain surgery.