CVE-2023-39423
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe RDPData.dll file exposes the /irmdata/api/common endpoint which is vulnerable to SQL injection. Attackers can exploit this by using UNION-based SQL injection to extract session data from the database, obtaining valid session tokens and impersonating currently logged-in users.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 5.3.2.15CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate RDPData.dll fileSearch the file system for RDPData.dll, typically found in the web application's bin directory, installation root folder, or under the IIS web root for the Resortdata applicationAffected if The file exists and belongs to Resortdata Internet Reservation Module Next Generation
-
Determine installed version of RDPData.dllRight-click the RDPData.dll file, select Properties, then view the Version tab; alternatively, use PowerShell command 'Get-Item "C:\path\to\RDPData.dll" | Select-Object VersionInfo' to retrieve version detailsAffected if File version is exactly 5.3.2.15
-
Verify /irmdata/api/common endpoint is exposedMake an HTTP GET or POST request to http(s)://<yourserver>/irmdata/api/common using curl, Invoke-WebRequest, or a browser; check if the endpoint responds (even with an error)Affected if The endpoint is accessible over the network and responds to requests
-
Confirm application is runningCheck if the Resortdata Internet Reservation Module Next Generation web application is currently deployed and running on the server or IISAffected if The application is actively running and serving requests
You are affected only if RDPData.dll version 5.3.2.15 is present in a running deployment AND the /irmdata/api/common endpoint is accessible.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement parameterized queries or prepared statements to sanitize user input in the /irmdata/api/common endpoint, and patch RDPData.dll to the latest secure version. As an interim measure, restrict network access to this API endpoint.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-39423 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-39423 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data