dbcve.org
Jboss Enterprise Application PlatformApplication · Redhat

CVE-2014-0093

MEDIUM · 5.8 CVSS v2.0 Published 2014-04-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
67/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
Red Hat JBoss Enterprise Application Platform (JBEAP) 6.2.2, when using a Java Security Manager (JSM), does not properly apply permissions defined by a policy file, which causes applications to be granted the java.security.AllPermission permission and allows remote attackers to bypass intended access restrictions.

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 confidence

In JBoss EAP 6.2.2, when the Java Security Manager (JSM) is enabled, the security policy file permissions are not properly applied, causing all applications to be granted java.security.AllPermission. This effectively disables all security sandboxing and allows applications full access to system resources, bypassing all intended access restrictions.

MitigationUpgrade JBoss EAP to a patched version or apply the relevant security update. If JSM is not essential, consider disabling it while ensuring alternative security controls are in place. Verify that policy files are correctly configured and being loaded.

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 Enterprise Application PlatformApplication
Affected:= 6.2.2

CVSS 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
M
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
None

AV:N/AC:M/Au:N/C:P/I:P/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed JBoss EAP version
    Check the JBoss EAP version by examining the version file or running the version command from the bin directory (run.sh or standalone.sh --version). Common paths include $JBOSS_HOME/bin/version.sh or checking $JBOSS_HOME/jboss-modules.jar properties.
    Affected if The installed version is JBoss EAP 6.2.2 exactly.
  2. Verify if Java Security Manager is enabled
    Check the JBoss startup configuration files for JSM enablement. Examine standalone.conf (or standalone.conf.bat on Windows) in the bin directory for the -Djava.security.manager property, or check if the security manager is set in the startup scripts or configuration XML files.
    Affected if JSM is enabled via -Djava.security.manager in the startup configuration.
  3. Locate and inspect the security policy file
    Find the java.security.policy setting in the JBoss configuration (standalone.conf or domain.conf). Locate the referenced policy file (often named jboss.policy in the configuration or server data directory).
    Affected if A security policy file is configured and being loaded by the JVM.
  4. Examine policy file permissions for AllPermission
    Open the security policy file and search for 'permission java.security.AllPermission' or 'grant codeBase'. Check if any grant block contains AllPermission that would apply to application code.
    Affected if The policy file grants java.security.AllPermission to application codebases, effectively disabling the security sandbox.
  5. Verify policy file is actually being applied
    At runtime, check if security manager is active by calling System.getSecurityManager() in a deployed application or by inspecting the JVM process arguments. Also verify the policy file path is valid and accessible.
    Affected if JSM is enabled but the policy file is not being properly loaded or applied, resulting in default AllPermission behavior.

You are affected if running JBoss EAP 6.2.2 with Java Security Manager enabled and the security policy file is either missing, misconfigured, or not being properly applied, resulting in applications receiving unrestricted system access.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade JBoss EAP to a patched version or apply the relevant security update. If JSM is not essential, consider disabling it while ensuring alternative security controls are in place. Verify that policy files are correctly configured and being loaded.

Fix this in Jboss Enterprise Application Platform Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-0093 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2014-0093 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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