CVE-2006-0230 in the critical feed json
Symantec Scan Engine 5.0.0.24, and possibly other versions before 5.1.0.7, uses a client-side check to verify a password, which allows remo…
published 2006-04-25 20 y ago modified 2026-06-16 4 mo ago also EUVD-2006-0238
- cvss
- 10.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 16.5%
- EPSS 16.5% chance of exploitation in 30 days, percentile 97%
- public exploits
- 1
- Exploit-DB
Summary
Symantec Scan Engine 5.0.0.24, and possibly other versions before 5.1.0.7, uses a client-side check to verify a password, which allows remote attackers to gain administrator privileges via a modified client that sends certain XML requests.
Patch / fix
Timeline
- First public exploit (EDB-1703)
- Published
Exploit prediction
16.47% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-1703 Symantec Scan Engine 5.0.x - Change Admin Password remote, 2006-04-21
- archives.neohapsis.com http://archives.neohapsis.com/archives/vulnwatch/2006-q2/0010.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 10.0 | AV:N/AC:L/Au:N/C:C/I:C/A:C |
References
-
archives.neohapsis.com
/archives/vulnwatch/2006-q2/0010.html
mailing-list, exploit, patch, vendor-advisory
-
securityfocus.com
/bid/17637
vdb-entry
-
secunia.com
/advisories/19734
third-party-advisory
-
securityfocus.com
/archive/1/431724/100/0/threaded
mailing-list
-
securityfocus.com
/archive/1/431734/100/0/threaded
mailing-list
-
kb.cert.org
/vuls/id/118388
third-party-advisory, us-government-resource
- symantec.com /avcenter/security/Content/2006.04.21.html
-
exchange.xforce.ibmcloud.com
/vulnerabilities/25972
vdb-entry
-
vupen.com
/english/advisories/2006/1464
vdb-entry
Sources
- CVE List CVE-2006-0230
- NVD CVE-2006-0230
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.