CVE-2018-9233 json
Sophos Endpoint Protection 10.7 uses an unsalted SHA-1 hash for password storage in %PROGRAMDATA%\Sophos\Sophos Anti-Virus\Config\machine.x…
published 2018-04-05 8 y ago modified 2026-06-17 4 mo ago also EUVD-2018-20827
- cvss
- 7.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.7%
- EPSS 1.7% chance of exploitation in 30 days, percentile 76%
- public exploits
- 1
- Exploit-DB
Summary
Sophos Endpoint Protection 10.7 uses an unsalted SHA-1 hash for password storage in %PROGRAMDATA%\Sophos\Sophos Anti-Virus\Config\machine.xml, which makes it easier for attackers to determine a cleartext password, and subsequently choose unsafe malware settings, via rainbow tables or other approaches.
Timeline
- Published
- First public exploit (EDB-44411)
Exploit prediction
1.65% chance of exploitation in the next 30 days, higher than 76% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-44411 Sophos Endpoint Protection Control Panel 10.7 - Weak Password Encryption local, 2018-04-06
- seclists.org http://seclists.org/fulldisclosure/2018/Apr/7 referenced PoC, tagged "exploit" by a source, unverified
- hyp3rlinx.altervista.org http://hyp3rlinx.altervista.org/advisories/SOPHOS-ENDPOINT-PROTECTION-CONTROL-PANEL-v10.7-INSECURE-CRYPTO-CVE-2018-9233.txt referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 7.8 | CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 2.1 | AV:L/AC:L/Au:N/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-916 Use of Password Hash With Insufficient Computational Effort
References
-
exploit-db.com
/exploits/44411/
exploit, third-party-advisory, vdb-entry
-
seclists.org
/fulldisclosure/2018/Apr/7
mailing-list, exploit, third-party-advisory
-
hyp3rlinx.altervista.org
/advisories/SOPHOS-ENDPOINT-PROTECTION-CONTROL-PANEL-v10.7-INSECURE-CRYPTO-CVE-2018-9233.txt
exploit, third-party-advisory
Sources
- CVE List CVE-2018-9233
- NVD CVE-2018-9233
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.