First published: Wed May 16 2007(Updated: )
Multiple IBM ISS Proventia Series products, including the A, G, and M series, do not properly handle certain full-width and half-width Unicode character encodings, which might allow remote attackers to evade detection of HTTP traffic.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
IBM Proventia M Series Xpu | =1.5 | |
IBM Proventia A Series XPU | =22.2 | |
IBM Proventia M Series Xpu | <=1.9 | |
IBM Proventia G Series XPU | =22.5 | |
IBM Proventia M Series Xpu | =1.1 | |
IBM Proventia M Series Xpu | =1.8 | |
IBM Proventia M Series Xpu | =1.6 | |
IBM Proventia A Series XPU | =22.3 | |
IBM Proventia A Series XPU | <=22.10 | |
IBM Proventia G Series XPU | =22.4 | |
IBM Proventia G Series XPU | =22.7 | |
IBM Proventia G Series XPU | =22.2 | |
IBM Proventia A Series XPU | =22.1 | |
IBM Proventia A Series XPU | =22.6 | |
IBM Proventia G Series XPU | <=22.11 | |
IBM Proventia G Series XPU | =22.8 | |
IBM Proventia A Series XPU | =22.4 | |
IBM Proventia G Series XPU | =22.3 | |
IBM Proventia M Series Xpu | =1.3 | |
IBM Proventia A Series XPU | =20.11 | |
IBM Proventia G Series XPU | =22.6 | |
IBM Proventia A Series XPU | =22.5 | |
IBM Proventia G Series XPU | =22.1 | |
IBM Proventia M Series Xpu | =1.7 | |
IBM Proventia M Series Xpu | =1.2 | |
IBM Proventia G Series XPU | =22.9 | |
IBM Proventia G Series XPU | =22.10 | |
IBM Proventia M Series Xpu | =1.4 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of CVE-2007-2690 is classified as medium, primarily due to the potential for remote attackers to evade detection of HTTP traffic.
To mitigate the risks associated with CVE-2007-2690, it is recommended to update to the latest patched versions of the IBM ISS Proventia Series products.
CVE-2007-2690 affects various models of the IBM ISS Proventia A, G, and M Series products, specifically versions 1.1 through 1.9 and 20.11 through 22.10.
CVE-2007-2690 could allow attackers to bypass security mechanisms designed to detect harmful HTTP traffic, potentially leading to data breaches.
There is no official workaround for CVE-2007-2690, so updating the software to the latest version is the most effective temporary measure.