CVE-2007-3853 json
Multiple unspecified vulnerabilities in Oracle Database 10.1.0.5 and 10.2.0.3 allow remote authenticated users to have unknown impact via (…
published 2007-07-18 19 y ago modified 2026-06-16 4 mo ago also EUVD-2007-3837
- cvss
- 6.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.8%
- EPSS 2.8% chance of exploitation in 30 days, percentile 86%
- public exploits
- 0
- none known
Summary
Multiple unspecified vulnerabilities in Oracle Database 10.1.0.5 and 10.2.0.3 allow remote authenticated users to have unknown impact via (1) DBMS_JAVA_TEST in the JavaVM component (DB01), (2) Oracle Text component (DB09), and (3) MDSYS.SDO_GEOR_INT in the Spatial component (DB15). NOTE: a reliable researcher claims that DB01 is SQL injection in DBMS_PRVTAQIS.
Exploit prediction
2.84% chance of exploitation in the next 30 days, higher than 86% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 6.5 | AV:N/AC:L/Au:S/C:P/I:P/A:P |
Classification
- Technology feeds
References
-
h20000.www2.hp.com
/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&objectID=c00727143
vendor-advisory
-
red-database-security.com
/advisory/oracle_sql_injection_dbms_prvtaqis.html
vendor-advisory
-
secunia.com
/advisories/26114
third-party-advisory
-
secunia.com
/advisories/26166
third-party-advisory
- oracle.com /technetwork/topics/security/cpujul2007-087014.html
-
us-cert.gov
/cas/techalerts/TA07-200A.html
third-party-advisory, us-government-resource
-
vupen.com
/english/advisories/2007/2562
vdb-entry
-
vupen.com
/english/advisories/2007/2635
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/35490
vdb-entry
- integrigy.com /security-resources/analysis/Integrigy_Oracle_CPU_July_2007_Analysis.pdf
-
securitytracker.com
/id?1018415
vdb-entry
-
securityfocus.com
/archive/1/474000
mailing-list
- red-database-security.com /advisory/oracle_cpu_jul_2007.html
Sources
- CVE List CVE-2007-3853
- NVD CVE-2007-3853
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.