First published: Wed Mar 26 2003(Updated: )
The digital signature mechanism for the Adobe Acrobat PDF viewer only verifies the PE header of executable code for a plug-in, which can allow attackers to execute arbitrary code in certified mode by making the plug-in appear to be signed by Adobe.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Adobe Acrobat Reader | =5.0 | |
Adobe Acrobat Reader | =4.0 | |
Adobe Acrobat Reader | =4.0.5 | |
Adobe Acrobat Reader | =4.0 | |
Adobe Acrobat Reader | =4.0.5a | |
Adobe Acrobat Reader | =5.0.5 | |
Adobe Acrobat Reader | =4.0.5c | |
Adobe Acrobat Reader | =4.0.5a | |
Adobe Acrobat Reader | =5.0 | |
Adobe Acrobat Reader | =5.0.5 | |
Adobe Acrobat Reader | =4.0.5 | |
Adobe Acrobat Reader | =4.0.5c |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2002-0030 is considered to be a medium severity vulnerability.
To fix CVE-2002-0030, update Adobe Acrobat Reader to the latest version available.
CVE-2002-0030 affects various versions of Adobe Acrobat Reader including versions 4.0, 4.0.5, and 5.0.
Attackers can execute arbitrary code in certified mode by making a plug-in appear to be signed by Adobe.
Yes, CVE-2002-0030 specifically affects Adobe Acrobat Reader versions 4.0, 4.0.5, and 5.0.