Home/CVE/Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 Update 7 and earlier, 6 Up
CVE
CVE-2012-5081
Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 Update 7 and earlier, 6 Up
Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 Update 7 and earlier, 6 Update 35 and earlier, 5.0 Update 36 and earlier, and 1.4.2_38 and earlier allows remote attackers to affect availability, related to JSSE.
MEDIUM · CVSS 5
EPSS 0.757
Act now
- EPSS ≥ 0.50 - high probability of exploitation in the next 30 days
- EPSS percentile: top 1% of all CVEs by exploitation likelihood
- Metasploit module exists (rank: Normal)
- Public exploit or PoC is available
Sigma rules0
YARA rules0
Look this up elsewhere - one-click external pivots
▸
How to read a CVE - triage first, then detect and patch
This page is every public fact about CVE-2012-5081, cross-linked. Its job is to answer one question fast - does this need my attention now? - and then hand you the two things you do about it. Here is how an analyst reads it.
Triage: should I act now? Four signals, and they are not interchangeable:
CVSSseverity - how bad it is IF exploited, 0-10. A high CVSS alone is not urgency; a flaw can be a perfect 10 and never actually be attacked.
EPSSprobability - a model’s estimate of the chance it is exploited in the next 30 days, 0-1. This is the “will it actually happen” signal.
CISA KEVconfirmed - it is being exploited in the wild right now. The strongest signal on the page; KEV beats any score.
Weaponisedavailability - public exploits / PoCs, and especially Metasploit modules rated Excellent / Great. Reliable, packaged exploit code means low-skill attackers can use it today.
How they combine: KEV, or a dependable Metasploit module, means patch now regardless of CVSS. High CVSS + low EPSS + no exploit is real but not an emergency - schedule it. Low CVSS but KEV-listed still gets patched now. The verdict above already weighed these for you; this is how it got there.
Then what - two workflows:
Detectwhen you cannot patch today, follow this CVE to the ATT&CK techniques it enables, then Build a SIEM detection (the green button) - author a rule, test it in Atomic, deploy it. That buys visibility while the patch waits.
PatchAffected products / packages tell you if you are exposed; Fixed versions by distribution and Vendor advisories give the exact version that closes it.
Reading order for the panels below: verdict + badges, then Public exploits / Metasploit (is it weaponised), then ATT&CK techniques + Sigma / IDS rules (can I detect it), then Affected products / packages + Fixed versions (am I exposed, what patches it), then Threat actors / IOCs (who uses it), then Scoring & timeline / references (the evidence).
▤
Affected Products & Versions
7oracle jdk<= 1.7.0
oracle jdkall versions
oracle jre<= 1.7.0
oracle jreall versions
oracle jdk<= 1.6.0
oracle jre<= 1.6.0
sun jdkall versions
⚠
Public Exploits & PoCs
2These PoC and exploit links come from public sources and are not verified to be safe or functional. Review the code before running anything, and treat unverified entries as untrusted.
📦
Fixed versions by distribution
8The package version that resolves this CVE on each Linux distribution, from the vendor’s published security data. fixed in shows a patched version exists; open means the package is listed as affected with no fix yet.
oracle alljava-1.6.0-openjdk open
oracle alljava-1.6.0-openjdk-demo open
oracle alljava-1.6.0-openjdk-devel fixed in 1:1.6.0.0-1.50.1.11.5.el6_3
oracle alljava-1.6.0-openjdk-src open
oracle alljava-1.7.0-openjdk open
oracle alljava-1.7.0-openjdk-demo open
oracle alljava-1.7.0-openjdk-devel fixed in 1:1.7.0.9-2.3.3.0.1.el6_3.1
oracle alljava-1.7.0-openjdk-src fixed in 1:1.7.0.9-2.3.3.0.1.el6_3.1
⚙
Metasploit Modules
1Weaponised exploit modules in the Metasploit Framework. Rank is Metasploit’s reliability rating - Excellent/Great/Good means dependable, real-world exploit code (a strong “act now” signal), not a fragile PoC.
▣
Scoring & Timeline
5
MEDIUM · CVSS v2 (legacy) · [email protected]
This CVE predates CVSS v3; the legacy v2 score is shown so triage still has a severity to work with.
v2 Vector
AV:N/AC:L/Au:N/C:N/I:N/A:P
⚑
Vendor Advisories
17suse-csafopenSUSE-SU-2024:10534-1
suse-csafSUSE-SU-2015:0344-1
suse-csafSUSE-SU-2015:1086-3
suse-csafSUSE-SU-2015:0392-1
suse-csafSUSE-SU-2015:1086-1
🔗
References & Sources
39Source URLs (vendor pages, mailing lists, write-ups). Exploit/PoC links are in their own section above to avoid duplication.