OpenstackApplication · Redhat
CVE-2018-10899
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 flaw was found in Jolokia versions from 1.2 to before 1.6.1. Affected versions are vulnerable to a system-wide CSRF. This holds true for properly configured instances with strict checking for origin and referrer headers. This could result in a Remote Code Execution attack.
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 confidenceJolokia versions 1.2 through 1.6.0 contain a system-wide CSRF vulnerability that bypasses strict origin and referrer header checks. An attacker can exploit this to perform actions on behalf of authenticated users, potentially achieving Remote Code Execution.
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
OpenstackApplication
= 13>= 1.2.0, < 1.6.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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/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.
-
Identify if Jolokia is installedLook for jolokia JAR files, WAR deployments, or running processes named 'jolokia'. Check application directories, lib folders, or container images for jolokia jars or wars.Affected if Jolokia software is found running or deployed in the environment
-
Determine the installed Jolokia versionCheck the jolokia JAR/WAR file name for the version, inspect the MANIFEST.MF file inside the jolokia artifact, or query the /jolokia/version HTTP endpoint if accessible.Affected if The version is 1.2.0 through 1.6.0 (any version >= 1.2.0 and < 1.6.1)
-
Check if running on Red Hat OpenStack 13Identify the OpenStack version in use by checking the system documentation, openstack CLI output, or the underlying platform configuration.Affected if Red Hat OpenStack version 13 is deployed
-
Verify Jolokia HTTP endpoints are network accessibleConfirm that Jolokia endpoints (typically /jolokia/) are exposed on a network-accessible interface rather than localhost-only, as the CSRF attack requires the attacker to send requests to the endpoint.Affected if Jolokia endpoints are reachable from non-local network sources
You are affected if Jolokia version 1.2.0 through 1.6.0 is installed and its HTTP endpoints are network accessible, or if running Red Hat OpenStack 13 which bundles a vulnerable Jolokia version.
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 data1.6.1
Upgrade Jolokia to version 1.6.1 or later. If immediate upgrading is not possible, consider disabling Jolokia endpoints or implementing additional request validation at the proxy/container level.
Fix this in Openstack
Scoped from the published advisory
- Consultation3.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,552.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-10899 — 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-2018-10899 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