Buffer overflow in Adobe Illustrator CS3 13.0.3 and earlier and Illustrator CS4 14.0.0 allows attackers to execute arbitrary code via unspec
Buffer overflow in Adobe Illustrator CS3 13.0.3 and earlier and Illustrator CS4 14.0.0 allows attackers to execute arbitrary code via unspecified vectors.
- Published
- Jan 8, 2010
- Updated
- Jun 16, 2026
- EPSS
- 8.0% · 95th percentile
- CWE
- CWE-119
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
42
Plan
Add it to your regular patch cycle.
- CVSS
- 40 / 40 · 10.0 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 2 / 30 · 8.0%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| adobe | illustrator | cpe:2.3:a:adobe:illustrator |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- adobe illustratorup to 13.0.3 inclusive
- adobe illustrator13.0
- adobe illustrator13.0.1
- adobe illustrator13.0.2
- adobe illustrator14.0.0
Same product
adobe: all recordsOther highest-scoring records for the same primary product.
- CVE-2009-4195Buffer overflow in Adobe Illustrator CS4 14.0.0, CS3 13.0.3 and earlier, and CS3 13.0.0 allows remote attackers to execute arbitrary code vi58Plan
- CVE-2012-0780Adobe Illustrator before CS6 allows attackers to execute arbitrary code or cause a denial of service (memory corruption) via unspecified vec45Plan
- CVE-2014-0513Stack-based buffer overflow in Adobe Illustrator CS6 before 16.0.5 and 16.2.x before 16.2.2 allows remote attackers to execute arbitrary cod42Plan
- CVE-2012-2026Adobe Illustrator before CS6 allows attackers to execute arbitrary code or cause a denial of service (memory corruption) via unspecified vec42Plan
- CVE-2012-2025Adobe Illustrator before CS6 allows attackers to execute arbitrary code or cause a denial of service (memory corruption) via unspecified vec42Plan
- CVE-2012-2024Adobe Illustrator before CS6 allows attackers to execute arbitrary code or cause a denial of service (memory corruption) via unspecified vec42Plan
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Technical details
Attack conditions
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- C · data can be read
- Integrity
- C · data or configuration can be modified
- Availability
- C · the service can be disrupted
- Attack complexity
- Low
- Confidentiality impact
- C
- Integrity impact
- C
- Availability impact
- C
Weakness class (CWE)
CWE-119 · Improper Restriction of Operations within the Bounds of a Memory BufferCVSS vector
AV:N/AC:L/Au:N/C:C/I:C/A:C
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Overflow BuffersCAPEC-100likelihood: High · Very High
- Buffer ManipulationCAPEC-123likelihood: High · Very High
- Client-side Injection-induced Buffer OverflowCAPEC-14likelihood: Medium · High
- Filter Failure through Buffer OverflowCAPEC-24likelihood: High · High
- MIME ConversionCAPEC-42likelihood: High · High
- Overflow Binary Resource FileCAPEC-44likelihood: High · Very High
- Buffer Overflow via Symbolic LinksCAPEC-45likelihood: High · High
ATT&CK techniques
—
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.