CVE-2009-4452 json
Kaspersky Anti-Virus 5.0 (5.0.712); Antivirus Personal 5.0.x; Anti-Virus 6.0 (6.0.3.837), 7 (7.0.1.325), 2009 (8.0.0.x), and 2010 (9.0.0.46…
published 16y ago modified 4mo ago also EUVD-2009-4419
- cvss
- 6.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.8%
- EPSS 0.8% chance of exploitation in 30 days, percentile 57%
- public exploits
- 1
- Exploit-DB
Summary
Kaspersky Anti-Virus 5.0 (5.0.712); Antivirus Personal 5.0.x; Anti-Virus 6.0 (6.0.3.837), 7 (7.0.1.325), 2009 (8.0.0.x), and 2010 (9.0.0.463); and Internet Security 7 (7.0.1.325), 2009 (8.0.0.x), and 2010 (9.0.0.463); use weak permissions (Everyone:Full Control) for the BASES directory, which allows local users to gain SYSTEM privileges by replacing an executable or DLL with a Trojan horse.
Is CVE-2009-4452 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 FencerTimeline
- First public exploit (EDB-10484)
- Published
Exploit prediction
0.82% chance of exploitation in the next 30 days, higher than 57% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-10484 Kaspersky Lab (Multiple Products) - Local Privilege Escalation local, 2009-12-16
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 6.8 | AV:L/AC:L/Au:S/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-264 Permissions, Privileges, and Access Controls
References
-
exploit-db.com
/exploits/10484
exploit
-
vupen.com
/english/advisories/2009/3573
vdb-entry, vendor-advisory
-
secunia.com
/advisories/37730
third-party-advisory, vendor-advisory
-
secunia.com
/advisories/37398
third-party-advisory, vendor-advisory
-
securitytracker.com
/id?1023366
vdb-entry
-
securityfocus.com
/archive/1/508508/100/0/threaded
mailing-list
-
securitytracker.com
/id?1023367
vdb-entry
Sources
- CVE List CVE-2009-4452
- NVD CVE-2009-4452
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.