CVE-2007-0047
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCRLF injection vulnerability in Adobe Acrobat Reader Plugin before 8.0.0, when used with the Microsoft.XMLHTTP ActiveX object in Internet Explorer, allows remote attackers to inject arbitrary HTTP headers and conduct HTTP response splitting attacks via CRLF sequences in the javascript: URI in the (1) FDF, (2) XML, or (3) XFDF AJAX request parameters.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceCRLF injection vulnerability in Adobe Acrobat Reader Plugin before 8.0.0 allows remote attackers to inject arbitrary HTTP headers and conduct HTTP response splitting attacks via CRLF sequences in javascript: URIs within FDF, XML, or XFDF AJAX request parameters when used with Microsoft.XMLHTTP ActiveX object in Internet Explorer.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 7.0.8CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:P/I:P/A:P
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if Adobe Acrobat Reader is installedOpen Windows Control Panel and look for Adobe Acrobat Reader in the Programs and Features list, or search for acrord32.exe in the Program Files directoryAffected if Adobe Acrobat Reader is found on the system
-
Determine the installed version of Adobe Acrobat ReaderRight-click on the Adobe Acrobat Reader icon or executable, select Properties, and check the Details tab for the version number. Alternatively, open Adobe Acrobat Reader and go to Help > About Adobe Acrobat Reader.Affected if version cannot be determined or is not visible
-
Compare the installed version against affected rangesIf the version is visible, compare it to the affected range: any version 7.0.8 or lower (including 7.0.x versions, 6.x versions, and earlier) is vulnerableAffected if the installed version is 7.0.8 or any earlier version such as 7.0.7, 7.0.6, 6.0.5, etc.
-
Verify the plugin component versionCheck the Adobe Acrobat Reader plugin directory (typically located in Program Files\Adobe\Acrobat 7.0\Reader\browser\INTBUNDLE or similar path) and verify the plugin version matches the affected Reader versionAffected if plugin version corresponds to an affected Reader version
The system is affected if Adobe Acrobat Reader version 7.0.8 or any earlier version (7.0.x, 6.x, or older) is installed on the machine.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade Adobe Acrobat Reader to version 8.0.0 or later to remediate this vulnerability.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-0047 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2007-0047 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data