Resort Data Processing vulnerabilities
We track 5 vulnerabilities in Resort Data Processing products. 5 are rated high or critical, and none are known to be exploited. The most recent was published on September 7, 2023.
Latest Resort Data Processing vulnerabilities
- 8.8 High severity
IRM Next Generation: Unrestricted Upload of File with Dangerous Type
A vulnerability in RDPngFileUpload.dll, as used in the IRM Next Generation booking system, allows a remote attacker to upload arbitrary content (such as a web shell component) to the SQL database and execute it with SYSTEM privileges. This vulnerability requir
- 9.1 Critical severity
IRM Next Generation: Improper Neutralization of Special Elements used in an SQL Command
The RDPData.dll file exposes the /irmdata/api/common endpoint that handles session IDs, among other features. By using a UNION SQL operator, an attacker can leak the sessions table, obtain the currently valid sessions and impersonate a currently logged-in user
- 9.8 Critical severity
IRM Next Generation: Use of Hard-coded Credentials
The /irmdata/api/ endpoints exposed by the IRM Next Generation booking engine authenticates requests using HMAC tokens. These tokens are however exposed in a JavaScript file loaded on the client side, thus rendering this extra safety mechanism useless.
- 7.7 High severity
IRM Next Generation: Use of Hard-coded Credentials
The RDPWin.dll component as used in the IRM Next Generation booking engine includes a set of hardcoded API keys for third-party services such as Twilio and Vonage. These keys allow unrestricted interaction with these services.
- 8.8 High severity
IRM Next Generation: Use of Hard-coded Credentials
The RDPCore.dll component as used in the IRM Next Generation booking engine, allows a remote user to connect to customers with an "admin" account and a corresponding password computed daily by a routine inside the DLL file. Once reverse-engineered, this routin