CVE-2008-7236 json
Unspecified vulnerability in the Oracle JDeveloper component in Oracle Application Server 10.1.2.2 and 10.1.3.1 allows remote attackers to…
published 2009-09-14 17 y ago modified 2026-06-16 4 mo ago also EUVD-2008-7194
- cvss
- 4.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 4.2%
- EPSS 4.2% chance of exploitation in 30 days, percentile 90%
- public exploits
- 0
- none known
Summary
Unspecified vulnerability in the Oracle JDeveloper component in Oracle Application Server 10.1.2.2 and 10.1.3.1 allows remote attackers to affect integrity via unknown vectors, aka AS05.
Patch / fix
- securitytracker.com/id?1019218 advisory
- us-cert.gov/cas/techalerts/TA08-017A.html advisory
- vupen.com/english/advisories/2008/0150 advisory
- vupen.com/english/advisories/2008/0180 advisory
Exploit prediction
4.17% chance of exploitation in the next 30 days, higher than 90% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- securityfocus.com http://www.securityfocus.com/bid/27229 referenced PoC, tagged "exploit" by a source, unverified
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
-
securitytracker.com
/id?1019218
vdb-entry, patch, third-party-advisory
-
us-cert.gov
/cas/techalerts/TA08-017A.html
third-party-advisory, patch, us-government-resource
-
vupen.com
/english/advisories/2008/0150
vdb-entry, patch, third-party-advisory
-
vupen.com
/english/advisories/2008/0180
vdb-entry, patch, third-party-advisory
-
securityfocus.com
/bid/27229
vdb-entry, exploit, third-party-advisory
-
marc.info
/?l=bugtraq&m=120058413923005&w=2
vendor-advisory, issue-tracking, mailing-list, third-party-advisory
-
oracle.com
/technetwork/topics/security/cpujan2008-086860.html
broken-link
-
secunia.com
/advisories/28556
third-party-advisory
-
osvdb.org
/40297
vdb-entry, broken-link
-
secunia.com
/advisories/28518
third-party-advisory
Sources
- CVE List CVE-2008-7236
- NVD CVE-2008-7236
Fencer Vulns 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.