CVE-2012-2566
First published: Sat Jun 09 2012(Updated: )
Bloxx Web Filtering before 5.0.14 does not properly interpret X-Forwarded-For headers during access-control and logging operations for HTTPS connection attempts, which allows remote attackers to bypass intended IP address and domain restrictions, and trigger misleading log entries, via a crafted header.
Credit: cret@cert.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Bloxx Web Filtering | <=5.0.13 |
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-2012-2566?
CVE-2012-2566 is considered to have a high severity due to its potential to allow unauthorized access and manipulation of logs.
How do I fix CVE-2012-2566?
To fix CVE-2012-2566, you should upgrade to Bloxx Web Filtering version 5.0.14 or later, which addresses this vulnerability.
What vulnerability does CVE-2012-2566 address?
CVE-2012-2566 addresses the improper handling of X-Forwarded-For headers in Bloxx Web Filtering that can lead to access-control bypass.
What systems are affected by CVE-2012-2566?
CVE-2012-2566 affects versions of Bloxx Web Filtering prior to 5.0.14.
Can CVE-2012-2566 be exploited remotely?
Yes, CVE-2012-2566 can be exploited remotely, allowing attackers to bypass intended IP address and domain restrictions.
- collector/nvd-index
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/weakness
- agent/last-modified-date
- agent/references
- agent/severity
- agent/author
- agent/tags
- agent/description
- agent/event
- agent/first-publish-date
- agent/source
- vendor/bloxx
- canonical/bloxx web filtering
- version/bloxx web filtering/5.0.13