CVE-2012-0079 json
Unspecified vulnerability in Oracle OpenSSO 7.1 and 8.0 allows remote attackers to affect integrity via unknown vectors related to Administ…
published 2012-01-18 14 y ago modified 2026-06-16 4 mo ago also EUVD-2012-0117
- cvss
- 4.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.4%
- EPSS 1.4% chance of exploitation in 30 days, percentile 72%
- public exploits
- 0
- none known
Summary
Unspecified vulnerability in Oracle OpenSSO 7.1 and 8.0 allows remote attackers to affect integrity via unknown vectors related to Administration.
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2012-0079 updated cvss 2.6
OpenSSO: Unspecified vulnerability allows remote attackers to affect integrity via unknown vectors
-
Red Hat JBoss BRMS 5 securityunder investigation
-
Red Hat JBoss SOA Platform 5.3fixed: vendor fix RHSA-2012:1125
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
1.39% chance of exploitation in the next 30 days, higher than 72% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:P/A:N |
References
-
rhn.redhat.com
/errata/RHSA-2012-1232.html
vendor-advisory
-
secunia.com
/advisories/46646
third-party-advisory, vendor-advisory
-
oracle.com
/technetwork/topics/security/cpujan2012-366304.html
vendor-advisory
-
securitytracker.com
/id?1026536
vdb-entry
-
secunia.com
/advisories/50084
third-party-advisory
-
securityfocus.com
/bid/51492
vdb-entry
-
osvdb.org
/78412
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/72501
vdb-entry
Sources
- CVE List CVE-2012-0079
- NVD CVE-2012-0079
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.