CVE-2001-1548
First published: Mon Dec 31 2001(Updated: )
ZoneAlarm 2.1 through 2.6 and ZoneAlarm Pro 2.4 and 2.6 allows local users to bypass filtering via non-standard TCP packets created with non-Windows protocol adapters.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Alarm | =2.1 | |
| Alarm | =2.2 | |
| Alarm | =2.3 | |
| Alarm | =2.4 | |
| Alarm | =2.4 | |
| Alarm | =2.5 | |
| Alarm | =2.6 | |
| Alarm | =2.6 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2001-1548?
CVE-2001-1548 is categorized as a high severity vulnerability due to its potential to allow local users to bypass security filtering.
How do I fix CVE-2001-1548?
To fix CVE-2001-1548, upgrade to a version of ZoneAlarm that is not affected, such as versions later than 2.6.
What versions of ZoneAlarm are affected by CVE-2001-1548?
CVE-2001-1548 affects ZoneAlarm versions 2.1 through 2.6 and ZoneAlarm Pro versions 2.4 and 2.6.
Who is affected by CVE-2001-1548?
Local users of the affected versions of ZoneAlarm are at risk of exploiting this vulnerability.
What kind of attacks can be performed using CVE-2001-1548?
Exploitation of CVE-2001-1548 can allow attackers to send non-standard TCP packets that bypass the software's filtering capabilities.
- agent/references
- agent/type
- agent/first-publish-date
- agent/author
- agent/weakness
- agent/severity
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/event
- agent/source
- agent/softwarecombine
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- collector/nvd-historical
- vendor/zonelabs
- canonical/alarm
- version/alarm/2.1
- version/alarm/2.2
- version/alarm/2.3
- version/alarm/2.4
- version/alarm/2.5
- version/alarm/2.6