CVE-2018-25266 Details
Description
Angry IP Scanner 3.5.3 contains a buffer overflow vulnerability in the preferences dialog that allows local attackers to crash the application by supplying an excessively large string. Attackers can generate a file containing a massive buffer of repeated characters and paste it into the unavailable value field in the display preferences to trigger a denial of service.
A buffer overflow vulnerability has been identified in Angry IP Scanner version 3.5.3, specifically within the preferences dialog. This vulnerability allows local attackers to cause a denial-of-service by crashing the application. Exploitation involves supplying an excessively large string into a field that is not properly validated. Attackers can create a file containing a massive buffer of repeated characters, which can then be pasted into the unavailable value field in the display preferences to trigger the crash.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Apr 22, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://angryip.org | [email protected] | Product |
| https://www.exploit-db.com/exploits/45993 | [email protected] | ExploitVDB Entry |
| https://www.vulncheck.com/advisories/angry-ip-scanner-denial-of-service-via-preferences-buffer-overflow | [email protected] | Third Party Advisory |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-787 | Out-of-bounds Write | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| angryip angry ip scanner | 3.5.3 |
CPE
Remediation
| |
Change History
4 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | [email protected] |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Apr 27, 2026 | Initial Analysis | [email protected] |
| Apr 22, 2026 | New CVE Received | [email protected] |