CVE-2024-11220
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 · uneditedA local low-level user on the server machine with credentials to the running OAS services can create and execute a report with an rdlx file on the server system itself. Any code within the rdlx file of the report executes with SYSTEM privileges, resulting in privilege escalation.
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 confidenceThis is a local privilege escalation vulnerability in Open Access Software (OAS) where a low-privileged user with valid credentials to running OAS services can create and execute reports using rdlx files. The rdlx file executes arbitrary code with SYSTEM-level privileges, allowing complete control of the server.
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< 20.0.0.76CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
-
Identify installed OAS versionLocate the Open Automation Software installation directory and check the version information, typically found in the software's About or Version dialog, or in installed program metadataAffected if The installed version is below 20.0.0.76
-
Verify OAS services are runningCheck if Open Automation Software services are running on the system using service management tools (such as Windows Services or PowerShell Get-Service)Affected if OAS services are active and accessible on the system
-
Assess user access to OAS report functionalityDetermine which user accounts have the ability to create or execute rdlx report files within the OAS platform, typically through user role or permission configurationsAffected if Low-privileged or non-administrative user accounts can create or run rdlx report files within OAS
-
Confirm OAS report execution feature is enabledInspect whether the rdlx report creation and execution capability is enabled in the OAS configuration or settingsAffected if The rdlx report feature is accessible and not explicitly disabled in OAS settings
A system is affected if OAS version is below 20.0.0.76, OAS services are running, and low-privileged users have the ability to create or execute rdlx report files within the OAS platform.
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.
dbcve · scoped20.0.0.76
Restrict and monitor access to OAS services to authorized personnel only. Implement proper authorization controls to prevent low-privileged users from creating or executing reports. Apply vendor patches when available.
20.0.0.76 or later
- Back up the current OAS configuration and any custom reports or settings
- Download OAS version 20.0.0.76 or later from the official Open Automation Software website (openautomationsoftware.com)
- Stop all OAS services before upgrading
- Install the updated OAS version
- Restart OAS services
- Verify that low-level users can no longer create or execute rdlx reports with SYSTEM privileges
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.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 $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-11220 — 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-2024-11220 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