Icedtea6Application · Redhat

CVE-2012-1723

CRITICAL · 9.8 CVSS v3.1 Published 2012-06-16

Fix available

A fix is available. Upgrade to 1.10.8 / 1.11.3 or later.

See remediation →

100/100

Remediation priority · Urgent

In the wild Ransomware High EPSS Remotely reachable No privileges Zero-click

Official description

NVD · unedited

Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 update 4 and earlier, 6 update 32 and earlier, 5 update 35 and earlier, and 1.4.2_37 and earlier allows remote attackers to affect confidentiality, integrity, and availability via unknown vectors related to Hotspot.

Technical summary

dbcve analysis · high confidence

Critical vulnerability in the Java Runtime Environment Hotspot component affecting Java SE 7u4 and earlier, 6u32 and earlier, 5u35 and earlier, and 1.4.2_37 and earlier. Allows remote attackers to execute arbitrary code by bypassing Java sandbox restrictions, impacting confidentiality, integrity, and availability.

MitigationApply Oracle's Java security updates (Java 7 Update 7, Java 6 Update 35, or later). If immediate patching is not feasible, disable the Java browser plugin and restrict Java applets until updates can be deployed.

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

Icedtea6Application

Affected:< 1.10.8>= 1.11.0, < 1.11.3

Enterprise Linux DesktopOperating system

Affected:= 5.0= 6.0

Enterprise Linux EusOperating system

Affected:= 6.2

Enterprise Linux ServerOperating system

Affected:= 5.0= 6.0

Enterprise Linux Server AusOperating system

Affected:= 6.2

Enterprise Linux WorkstationOperating system

Affected:= 5.0= 6.0

JdkApplication

Affected:<= 1.4.2_37= 1.5.0= 1.6.0= 1.7.0

JreApplication

Affected:<= 1.4.2_37= 1.5.0= 1.6.0= 1.7.0

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: None
User interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected?

dbcve checks

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

Identify installed Java version

Run 'java -version' or 'java -fullversion' from command line to see the installed JRE/JDK version

Affected if Version shows 1.4.2_37 or earlier, 1.5.0, 1.6.0, 1.7.0, or any 7u4 and earlier (1.7.0_u4 or earlier)
Check Oracle JDK package version

On Red Hat systems, run 'rpm -qa | grep -i jdk' to list installed JDK packages

Affected if Package version corresponds to affected Oracle JDK versions listed (1.4.2_37 or earlier, 1.5.0, 1.6.0, 1.7.0)
Check Oracle JRE package version

On Red Hat systems, run 'rpm -qa | grep -i jre' to list installed JRE packages

Affected if Package version corresponds to affected Oracle JRE versions listed (1.4.2_37 or earlier, 1.5.0, 1.6.0, 1.7.0)
Check Icedtea6 package version

On Red Hat systems using OpenJDK/Icedtea, run 'rpm -qa | grep icedtea' to identify version

Affected if Version is earlier than 1.10.8, or between 1.11.0 and 1.11.2 inclusive
Verify Hotspot JIT compiler presence

Run 'java -version -verbose' or check for 'hotspot' in Java runtime details to confirm Hotspot is in use

Affected if Hotspot JVM is present and running an affected Java version

Your environment is affected if any installed Java version (JDK, JRE, or Icedtea6) falls within the affected version ranges: 1.4.2 through 1.4.2_37, 1.5.0, 1.6.0, 1.7.0 (7u4 and earlier), or Icedtea6 <1.10.8 or 1.11.0-1.11.2

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

Remediation

dbcve · scoped

Upgrade available Upgrade to 1.10.8 / 1.11.3 or later

Fixed in 1.10.81.11.3

Interim mitigation

Apply Oracle's Java security updates (Java 7 Update 7, Java 6 Update 35, or later). If immediate patching is not feasible, disable the Java browser plugin and restrict Java applets until updates can be deployed.

Recommended fix High confidence

JDK/JRE 7u5+, 6u33+, 5u36+, or 1.4.2_38+ | IcedTea6 1.10.8+ or 1.11.3+

Identify the currently installed Java/JRE version by running 'java -version' or checking the system package manager
For Oracle Java SE: Upgrade to JDK/JRE 7 Update 5 or later (if using Java 7), or JDK/JRE 6 Update 33 or later (if using Java 6), or JDK/JRE 5 Update 36 or later (if using Java 5)
For OpenJDK: Upgrade to a version beyond the affected releases listed (1.7.0_05+, 1.6.0_33+, 1.5.0_36+)
For IcedTea6: Upgrade to version 1.10.8 or later, or 1.11.3 or later
For Red Hat Enterprise Linux systems: Run 'yum update java-*' or 'rhn-update' to apply available security patches
Verify the upgrade was successful by running 'java -version' and confirming the new version number
Restart any running Java applications to ensure they use the updated JRE

Caveat Minor - same-major-version updates are generally backward compatible; however, test critical applications after upgrading Java

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Icedtea6 Exploited in the wild — priority engagement

Consultation2.0 h
Implementation4.0 h
Testing2.0 h
Review / QA1.0 h

9.0 hours of engineering $1,600

Get it fixed fast

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

www.oracle.comVendor Advisory
rhn.redhat.comThird Party Advisory
security.gentoo.orgThird Party Advisory
www.securityfocus.comBroken LinkThird Party AdvisoryVDB Entry
mail.openjdk.java.netMailing List
marc.infoMailing List
secunia.comBroken Link
www.ibm.comBroken Link
www.mandriva.comBroken Link
oval.cisecurity.orgBroken Link
www.cisa.govUS Government Resource
nvd.nist.govNVD record

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2012-1723?

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

Exploited in the wildOn CISA’s known-exploited list · agencies must fix by 2022-03-24

A fix existsUpgrade to 1.10.8 / 1.11.3 or later

Severity 9.8 Critical

Exploit likelihood EPSS, next 30 days 93.7%

Affects: Icedtea6

Remediation

Being exploited — close it fast

Fix this in Icedtea6 9 hrs · Low

Typical engagement from $1,600

Get it fixed fast See the full breakdown ↓

This CVE is on CISA’s actively-exploited list, so the clock is real — a vetted specialist can deliver a reviewed fix for your staging environment quickly.

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