JrockitApplication · Oracle

CVE-2015-4803

MEDIUM · 5.0 CVSS v2.0 Published 2015-10-21

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

59/100

Remediation priority · Elevated

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

Unspecified vulnerability in Oracle Java SE 6u101, 7u85, and 8u60; Java SE Embedded 8u51; and JRockit R28.3.7 allows remote attackers to affect availability via vectors related to JAXP, a different vulnerability than CVE-2015-4893 and CVE-2015-4911.

Technical summary

dbcve analysis · moderate confidence

Unspecified vulnerability in Oracle Java SE's JAXP (Java API for XML Processing) component allows remote attackers to impact availability. Affects Java SE 6u101, 7u85, 8u60; Java SE Embedded 8u51; and JRockit R28.3.7.

MitigationApply Oracle Critical Patch Update October 2015 (or subsequent updates) to obtain patched Java versions, or upgrade to a currently supported Java version receiving security updates.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

JrockitApplication

Affected:= r28.3.7

JdkApplication

Affected:= 1.6.0= 1.7.0= 1.8.0

JreApplication

Affected:= 1.6.0= 1.7.0= 1.8.0

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Authentication: None
Confidentiality: None
Integrity: None
Availability: Partial

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

Am I affected?

dbcve checks

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

Identify Java/JDK/JRE installation

Run 'java -version' or 'java -fullversion' from command line to see the installed Java version. Also check for multiple Java installations with 'which java' and review JAVA_HOME environment variable.

Affected if The installed version matches Java SE 6u101 or earlier, Java SE 7u85 or earlier, Java SE 8u60 or earlier, or JRockit R28.3.7 exactly.
Verify JAXP is in use

Check if the application or environment uses XML processing by searching for import statements like 'javax.xml.parsers', 'org.w3c.dom', 'org.xml.sax', or look for XML configuration files being processed. JAXP is included in the JDK/JRE but the vulnerability triggers when XML is processed.

Affected if Java is processing XML documents using JAXP libraries (typically via DocumentBuilder, SAXParser, or TransformerFactory).
Check if Java Web Start or Java Plug-in is enabled

Review browser settings and system configuration for Java Web Start (javaws) or Java plug-in usage. These are common vectors for remote JAXP exploitation.

Affected if Java Web Start is installed and has been used, or the Java browser plug-in is enabled, as this provides the remote attack surface.
Review Java policy and security settings

Examine the java.security file in the JRE/lib/security directory and any deployed security.policy files for permissions granted to untrusted code.

Affected if The security manager is not enforcing strict policies, allowing untrusted code to access JAXP processing capabilities.

A system is affected if it runs any of the specific Oracle Java/JDK/JRE versions listed (6u101 and earlier, 7u85 and earlier, 8u60 and earlier, or JRockit R28.3.7) and uses JAXP to process XML from untrusted sources.

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

Remediation

From vendor data

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Apply Oracle Critical Patch Update October 2015 (or subsequent updates) to obtain patched Java versions, or upgrade to a currently supported Java version receiving security updates.

Fix this in Jrockit Scoped from the published advisory

Consultation3.0 h
Implementation4.0 h
Testing6.0 h
Review / QA2.0 h

15.0 hours of engineering $2,580

Get help mitigating

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2015-4803 — 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

Primary sources

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2015-4803?

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.

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

At a glance

A fix existsA vendor remedy is published

Severity 5.0 Medium

Exploit likelihood EPSS, next 30 days 5.3%

Affects: Jrockit

Remediation

Need this fixed?

Fix this in Jrockit 15 hrs · Moderate

Typical engagement from $2,580

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2015-4803 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

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

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References