CVE-2005-4708 json
Adobe Macromedia MX 2004 products, Captivate, Contribute 2, Contribute 3, and eLicensing client install the Macromedia Licensing Service wi…
published 2005-12-31 20 y ago modified 2026-06-16 4 mo ago also EUVD-2005-4701
- cvss
- 7.2
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.2%
- EPSS 1.2% chance of exploitation in 30 days, percentile 68%
- public exploits
- 0
- none known
Summary
Adobe Macromedia MX 2004 products, Captivate, Contribute 2, Contribute 3, and eLicensing client install the Macromedia Licensing Service with the Users group permitted to configure the service, including the path to executable, which allows local users to execute arbitrary code as Local System.
Patch / fix
Exploit prediction
1.22% chance of exploitation in the next 30 days, higher than 68% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 7.2 | AV:L/AC:L/Au:N/C:C/I:C/A:C |
References
-
macromedia.com
/devnet/security/security_zone/mpsb05-04.html
patch, vendor-advisory
-
securitytracker.com
/id?1014162
vdb-entry
-
securitytracker.com
/id?1014161
vdb-entry
-
securitytracker.com
/id?1014165
vdb-entry
-
securityfocus.com
/archive/1/423587/100/0/threaded
mailing-list
-
kb.cert.org
/vuls/id/953860
third-party-advisory, us-government-resource
-
securitytracker.com
/id?1014166
vdb-entry
- cs.princeton.edu /~sudhakar/papers/winval.pdf
-
securitytracker.com
/id?1014159
vdb-entry
-
osvdb.org
/17248
vdb-entry
-
securitytracker.com
/id?1014163
vdb-entry
-
securitytracker.com
/id?1014164
vdb-entry
-
vupen.com
/english/advisories/2005/0723
vdb-entry
-
secunia.com
/advisories/15654
third-party-advisory
-
securitytracker.com
/id?1014158
vdb-entry
-
securitytracker.com
/id?1014160
vdb-entry
-
securityfocus.com
/bid/13925
vdb-entry
Sources
- CVE List CVE-2005-4708
- NVD CVE-2005-4708
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.