CVE-2012-2352
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 · uneditedThe archive management (arc_manage) page in wwsympa/wwsympa.fcgi.in in Sympa before 6.1.11 does not check permissions, which allows remote attackers to list, read, and delete arbitrary list archives via vectors related to the (1) do_arc_manage, (2) do_arc_download, or (3) do_arc_delete functions.
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 confidenceThe archive management page (arc_manage) in Sympa before version 6.1.11 lacks permission checks in the wwsympa.fcgi.in web interface, allowing unauthenticated remote attackers to access do_arc_manage, do_arc_download, and do_arc_delete functions to list, read, and delete arbitrary mailing list archives without authorization.
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<= 6.1.10= 0.001= 0.002= 0.003= 0.004= 0.005= 0.006= 0.007= 0.008= 0.009= 0.010= 0.011CVSS 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
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/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.
-
Identify Sympa installation and versionRun the command to check the installed Sympa version (for example, using 'sympa_version' command, checking package manager, or looking at version files in the Sympa installation directory)Affected if The installed Sympa version is 6.1.10 or earlier, or matches any of the versions 0.001 through 0.011 listed in the affected versions
-
Confirm the wwsympa web interface is in useCheck if the wwsympa.fcgi web interface (typically found in the cgi-bin or similar web directory) is installed and accessibleAffected if The wwsympa web interface is present and running, as the vulnerability exists in this component
-
Verify the arc_manage page is accessible without authenticationAttempt to access the arc_manage page (such as /wwsympa/arc_manage or similar URL path) without providing credentials or a valid sessionAffected if The arc_manage page returns content or functions (do_arc_manage, do_arc_download, do_arc_delete) without requiring authentication or authorization
-
Check web server access logs for vulnerable function callsReview web server access logs for requests to the arc_manage functionality, particularly do_arc_manage, do_arc_download, or do_arc_delete actionsAffected if These functions are being accessed, indicating potential exploitation or vulnerability probe attempts
A user is affected if they are running Sympa version 6.1.10 or earlier with the wwsympa web interface exposed and the arc_manage page accessible without authentication.
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 Sympa to version 6.1.11 or later which implements proper permission validation on archive management functions. Until patched, restrict network access to the wwsympa web interface.
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-2352 — 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-2352 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