Notepad++: Authenticode verification bypass allows modified updater execution
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| notepad-plus-plus | notepad-plus-plus | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Notepad-plus-plus | Notepad++ |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.124% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Notepad-plus-plus
Notepad-plus-plus notepad++ |
|
| Vendors & Products |
Notepad-plus-plus
Notepad-plus-plus notepad++ |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Notepad++ is a free and open-source source code editor. From 8.9.7 until 8.9.8, the Notepad++ updater and signature verification path can accept a modified GUP.exe file whose embedded certificate metadata remains present even though its Authenticode digest is invalid. An attacker who can replace or plant the updater-related file can cause Notepad++ to launch attacker-modified code when a user triggers the updater path, but the issue does not provide remote code execution by itself. This issue is fixed in version 8.9.8. | |
| Title | Notepad++: Authenticode verification bypass allows modified updater execution | |
| Weaknesses | CWE-347 | |
| References |
|
|
| Metrics |
cvssV3_1
|