CVE-2012-3343
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCross-site request forgery (CSRF) vulnerability in Microdasys before 3.5.1-B708, as used in Bloxx Web Filtering before 5.0.14 and other products, allows remote attackers to hijack the authentication of arbitrary users for requests that trigger error pages containing XSS sequences, a different vulnerability than CVE-2012-2564.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceCross-site request forgery (CSRF) vulnerability in Microdasys components before version 3.5.1-B708 (used in Bloxx Web Filtering before 5.0.14) allows remote attackers to hijack authentication of arbitrary users. The CSRF triggers error pages that contain cross-site scripting (XSS) sequences, enabling both session hijacking and XSS attacks.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 5.0.13CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:P/I:P/A:P
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Bloxx Web Filtering installationIdentify if Bloxx Web Filtering is deployed in your environment by checking for the product in your asset inventory, installed software list, or network devicesAffected if Bloxx Web Filtering is present and the version cannot be determined or is <= 5.0.13
-
Determine installed Bloxx versionAccess the Bloxx admin interface or check the system management console to retrieve the exact version number of Bloxx Web FilteringAffected if The installed version is 5.0.13 or earlier, or the version cannot be verified
-
Identify Microdasys component versionCheck the Bloxx system documentation, admin panel, or component registry for the Microdasys component version numberAffected if The Microdasys component version is earlier than 3.5.1-B708 or cannot be determined
-
Assess network exposure of admin interfaceDetermine if the Bloxx management interface is network-accessible from untrusted networks, as this CSRF/XSS vulnerability requires user interaction with the web interfaceAffected if The admin interface is exposed to untrusted networks without additional access controls
You are affected if Bloxx Web Filtering version 5.0.13 or earlier is installed, or if the Microdasys component version is earlier than 3.5.1-B708.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade Microdasys to version 3.5.1-B708 or later, and Bloxx Web Filtering to version 5.0.14 or later. Implement anti-CSRF tokens in application forms and validate error page output to prevent XSS injection.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-3343 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2012-3343 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data