Jboss Operations NetworkApplication · Redhat
CVE-2019-3834
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 · uneditedIt was found that the fix for CVE-2014-0114 had been reverted in JBoss Operations Network 3 (JON). This flaw allows attackers to manipulate ClassLoader properties on a vulnerable server. Exploits that have been published rely on ClassLoader properties that are exposed such as those in JON 3. Additional information can be found in the Red Hat Knowledgebase article: https://access.redhat.com/site/solutions/869353. Note that while multiple products released patches for the original CVE-2014-0114 flaw, the reversion described by this CVE-2019-3834 flaw only occurred in JON 3.
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 · moderate confidenceIt was found that the security fix for CVE-2014-0114 was reverted in JBoss Operations Network 3 (JON), re-introducing a ClassLoader manipulation vulnerability. Attackers can exploit exposed ClassLoader properties to conduct attacks, as the original mitigation was removed.
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 Operations NetworkApplication
> 3.2.1, < 3.3.11CVSS 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
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
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.
-
Confirm JBoss Operations Network installationLocate JON installation directory or check for running JON processes/services. Common locations include /opt/jboss-on/ or looking for 'jboss-on' process.Affected if JON is not installed or not running - not affected
-
Identify installed JON versionCheck version file in JON installation directory, typically found in version.properties or about.xml, or use CLI: ./rhqctl --version or check the administration console for version information.Affected if Version is greater than 3.2.1 AND less than 3.3.11 - vulnerable version range
-
Verify ClassLoader properties exposureExamine JON server configuration files (such as web.xml or jmx-invoker security configuration) for exposed ClassLoader-related MBean properties or servlet parameters. Look for properties related to getClassLoader or similar ClassLoader access points.Affected if ClassLoader manipulation endpoints or MBeans are publicly accessible without proper authentication
-
Check for CVE-2014-0114 mitigation removalInspect the jmx-invoker or web invoke servlet configuration for the presence of ClassLoader protection filters. The original CVE-2014-0114 fix should restrict access to ClassLoader-related operations.Affected if The ClassLoader protection filter is missing or disabled, indicating the fix was reverted
Environment is affected if JON version is greater than 3.2.1 and less than 3.3.11, AND ClassLoader properties are exposed without proper access controls.
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 data3.3.11
Re-apply the CVE-2014-0114 fix to JON 3 or upgrade to a patched version that includes the proper ClassLoader protection. Refer to Red Hat Knowledgebase article for specific remediation steps.
Fix this in Jboss Operations Network
Scoped from the published advisory
- Consultation4.0 h
- Implementation6.0 h
- Testing4.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 $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-3834 — 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-3834 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