CVE-2008-3436
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 · uneditedThe GUP generic update process in Notepad++ before 4.8.1 does not properly verify the authenticity of updates, which allows man-in-the-middle attackers to execute arbitrary code via a Trojan horse update, as demonstrated by evilgrade and DNS cache poisoning.
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 confidenceThe GUP (generic update process) in Notepad++ versions prior to 4.8.1 lacks proper cryptographic verification of update authenticity, allowing man-in-the-middle attackers to inject malicious updates that execute arbitrary code on the target system.
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<= 1.0<= 1.1<= 1.2<= 1.3<= 1.4<= 1.5<= 1.6<= 1.7<= 1.8<= 1.9<= 2.1<= 2.2CVSS 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
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/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.
-
Verify Notepad++ is installedCheck for the presence of Notepad++ installation directory (commonly C:\Program Files\Notepad++\ or C:\Program Files (x86)\Notepad++\) or look for notepad++.exe on the systemAffected if Notepad++ is found on the system
-
Determine installed Notepad++ versionRight-click notepad++.exe, select Properties, then view the Details tab for Product Version, or run: notepad++.exe -versionAffected if Version is 4.8.0 or earlier, or any version prior to 4.8.1
-
Identify if GUP update mechanism is configuredCheck Notepad++ configuration files (config.xml in the Notepad++ program directory) for <GUP> or <Update> related settings, or inspect the plugins\GUP folder if presentAffected if GUP/Update component exists and is configured for automatic or on-demand checking
-
Confirm vulnerability conditionCross-reference installed version against affected ranges: versions 1.0 through 2.2 are explicitly listed as affected, along with any version prior to 4.8.1Affected if Installed version is 4.8.0 or earlier, or falls within 1.0 through 2.2 range, AND GUP update feature is present
User is affected if Notepad++ version 4.8.0 or earlier is installed with the GUP update component enabled, allowing potential injection of malicious updates via network interception.
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 to Notepad++ 4.8.1 or later which implements proper update verification. Until patched, avoid using the built-in update mechanism on untrusted networks and consider network-level defenses against DNS cache poisoning.
- Consultation1.0 h
- Implementation1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2008-3436 — 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-2008-3436 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