Jboss Core ServicesApplication · Redhat
CVE-2016-9596
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 · uneditedlibxml2, as used in Red Hat JBoss Core Services and when in recovery mode, allows context-dependent attackers to cause a denial of service (stack consumption) via a crafted XML document. NOTE: this vulnerability exists because of an incorrect fix for CVE-2016-3627.
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 confidencelibxml2 contains a stack consumption vulnerability when processing crafted XML documents in recovery mode, leading to denial of service. This issue is a regression stemming from an incorrect fix for CVE-2016-3627, indicating the original vulnerability mitigation was incomplete or flawed.
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
Jboss Core ServicesApplication
all versions< 2.9.4CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/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 the installed libxml2 versionRun `xml2 --version` or check the shared library with `ldd --version` and look for libxml2, or use `rpm -q libxml2` on Red Hat systemsAffected if The installed version is earlier than 2.9.4 (for example, 2.9.3, 2.9.2, 2.7.x, etc.)
-
Determine if recovery mode is enabled for XML parsingSearch application code and configuration files for the XML_PARSE_RECOVERY flag, or `xmlParseRecovery` function calls, or similar recovery mode settings used during XML processingAffected if Applications or services parse XML with recovery mode enabled, especially on untrusted input
-
Check for Red Hat JBoss Core Services installationRun `rpm -qa | grep -i jboss` or check for JBoss installation directories such as /opt/jboss or /usr/share/jbossAffected if Red Hat JBoss Core Services is installed (all versions are affected)
-
Inspect XML processing components and dependenciesUse package managers or dependency scanners (like `dpkg -l | grep libxml2`, `yum list installed libxml2`, or examining application WAR/JAR files) to identify all libxml2 instancesAffected if Any component links to or bundles a vulnerable libxml2 version (< 2.9.4)
You are affected if your environment has libxml2 version earlier than 2.9.4 AND processes XML documents using recovery mode, particularly with untrusted input.
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 data2.9.4
Update libxml2 to a version with a complete, verified fix for this regression. Avoid using recovery mode with untrusted or unvalidated XML input until the patch is applied. Consider input validation and resource limits for XML parsing as additional defense-in-depth.
Fix this in Jboss Core Services
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,416.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-9596 — 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-2016-9596 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