CVE-2015-2078 json
The SDK for Komodia Redirector with SSL Digestor, as used in Lavasoft Ad-Aware Web Companion 1.1.885.1766 and Ad-Aware AdBlocker (alpha) 1.…
published 11y ago modified 4mo ago also EUVD-2015-2189
- cvss
- 5.0
- version 2.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
- 0
- none known
Summary
The SDK for Komodia Redirector with SSL Digestor, as used in Lavasoft Ad-Aware Web Companion 1.1.885.1766 and Ad-Aware AdBlocker (alpha) 1.3.69.1, Qustodio for Windows, Atom Security, Inc. StaffCop 5.8, and other products, does not properly verify X.509 certificates from SSL servers, which allows man-in-the-middle attackers to spoof servers, a different vulnerability than CVE-2015-2077.
Is CVE-2015-2078 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
1.67% chance of exploitation in the next 30 days, higher than 76% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- blog.filippo.io https://blog.filippo.io/komodia-superfish-ssl-validation-is-broken/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:P/A:N |
Classification
- Weakness
-
- CWE-310 Cryptographic Issues
References
-
blog.filippo.io
/komodia-superfish-ssl-validation-is-broken/
exploit
-
us-cert.gov
/cas/techalerts/TA15-051A.html
third-party-advisory, us-government-resource
- blog.erratasec.com /2015/02/some-notes-on-superfish.html#.VOq6Yvn8Fp4
- blog.erratasec.com /2015/02/extracting-superfish-certificate.html#.VOq6Yfn8Fp4
-
securitytracker.com
/id/1031779
vdb-entry
-
kb.cert.org
/vuls/id/529496
third-party-advisory, us-government-resource
- facebook.com /notes/protect-the-graph/windows-ssl-interception-gone-wild/1570074729899339
Sources
- CVE List CVE-2015-2078
- NVD CVE-2015-2078
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.