CVE-2006-0270 in the critical feed json
Unspecified vulnerability in the Transparent Data Encryption (TDE) Wallet component of Oracle Database server 10.2.0.1 has unspecified impa…
published 2006-01-18 20 y ago modified 2026-06-16 4 mo ago also EUVD-2006-0277
- cvss
- 10.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 4.9%
- EPSS 4.9% chance of exploitation in 30 days, percentile 92%
- public exploits
- 0
- none known
Summary
Unspecified vulnerability in the Transparent Data Encryption (TDE) Wallet component of Oracle Database server 10.2.0.1 has unspecified impact and attack vectors, as identified by Oracle Vuln# DB27. NOTE: Oracle has not disputed a reliable researcher report that TDA stores the master key without encryption, which allows local users to obtain the key via the SGA.
Exploit prediction
4.86% chance of exploitation in the next 30 days, higher than 92% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 10.0 | AV:N/AC:L/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-310 Cryptographic Issues
- Technology feeds
References
-
secunia.com
/advisories/18493
third-party-advisory, vendor-advisory
-
vupen.com
/english/advisories/2006/0323
vdb-entry, vendor-advisory
-
vupen.com
/english/advisories/2006/0243
vdb-entry, vendor-advisory
-
secunia.com
/advisories/18608
third-party-advisory, vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/24186
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/24321
vdb-entry
-
securityfocus.com
/bid/16287
vdb-entry
-
kb.cert.org
/vuls/id/545804
third-party-advisory, us-government-resource
-
securitytracker.com
/id?1015499
vdb-entry
- oracle.com /technetwork/topics/security/cpujan2006-082403.html
-
securityfocus.com
/archive/1/422262/30/7400/threaded
mailing-list
- red-database-security.com /advisory/oracle_tde_unencrypted_sga.html
Sources
- CVE List CVE-2006-0270
- NVD CVE-2006-0270
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.