CVE-2019-11773
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 · uneditedPrior to 0.1, AIX builds of Eclipse OMR contain unused RPATHs which may facilitate code injection and privilege elevation by local users.
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 Eclipse OMR library builds for AIX contain unused RPATH (runtime library search path) entries embedded in the binaries. These unnecessary RPATH directories can be exploited by local users who can place malicious libraries in those paths, causing the application to load attacker-controlled code via DLL/Hijacking attacks, potentially leading to code injection and privilege elevation.
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< 0.1CVSS 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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.
-
Verify the operating system is AIXRun 'uname -a' or 'oslevel' to confirm the system is AIX. This vulnerability only affects Eclipse OMR builds for AIX.Affected if The system is running AIX and has Eclipse OMR installed.
-
Locate Eclipse OMR binariesSearch for OMR-related executables or shared libraries on the system, typically in installation directories or standard library paths. Common locations include /opt, /usr/local, or user-defined paths.Affected if Eclipse OMR binaries exist on the AIX system.
-
Determine installed Eclipse OMR versionUse 'strings' or a binary analysis tool to extract version information from the OMR binaries, or check the package/binary metadata if available.Affected if The version extracted is less than 0.1.
-
Inspect RPATH values in binariesOn AIX, use the 'dump -H' or 'od -c' command on the OMR executables and shared libraries to examine embedded RPATH entries. Look for runtime library search path directives.Affected if Unused or unnecessary RPATH directories are present in the binary that could be exploited for DLL hijacking.
A user is affected if running Eclipse OMR version below 0.1 on AIX, with unused RPATH entries embedded in the binaries that could allow a local attacker to inject malicious code via library hijacking.
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 data0.1
Upgrade to Eclipse OMR version 0.1 or later where the unused RPATHs have been removed. If upgrading is not feasible, rebuild the OMR library from source with RPATH explicitly disabled or removed from the build configuration.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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 $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-11773 — 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-2019-11773 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