CVE-2012-2352: High severity sympa vulnerability

Published May 31, 2012
·
Updated

The archive management (arcmanage) 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) doarcmanage, (2) doarcdownload, or (3) doarcdelete functions.

Affected Software

159 affected components
sympa sympa<=6.1.10
sympa sympa=0.001
sympa sympa=0.002
sympa sympa=0.003
sympa sympa=0.004
sympa sympa=0.005
sympa sympa=0.006
sympa sympa=0.007
sympa sympa=0.008
sympa sympa=0.009
sympa sympa=0.010
sympa sympa=0.011
sympa sympa=1.2.0
sympa sympa=1.2.1
sympa sympa=1.2.2
sympa sympa=1.3.0
sympa sympa=1.3.1
sympa sympa=1.3.1-2
sympa sympa=1.3.2
sympa sympa=1.3.3
sympa sympa=1.3.4
sympa sympa=1.3.4-1
sympa sympa=1.4.0
sympa sympa=1.4.1
sympa sympa=1.4.2
sympa sympa=1.4.2-1
sympa sympa=1.5
sympa sympa=2.2.1b
sympa sympa=2.2.2b
sympa sympa=2.2.3b
sympa sympa=2.2.4
sympa sympa=2.2.5
sympa sympa=2.2.6
sympa sympa=2.2.7
sympa sympa=2.2b
sympa sympa=2.3-beta
sympa sympa=2.3.0
sympa sympa=2.3.1
sympa sympa=2.3.2
sympa sympa=2.3.3
sympa sympa=2.3.4
sympa sympa=2.4
sympa sympa=2.5
sympa sympa=2.5.1
sympa sympa=2.5.2
sympa sympa=2.5.3b
sympa sympa=2.5.4b
sympa sympa=2.6
sympa sympa=2.6.1
sympa sympa=2.7
sympa sympa=2.7.1
sympa sympa=2.7.2
sympa sympa=2.7.3
sympa sympa=2.7a
sympa sympa=2.7b.1
sympa sympa=2.7b.2
sympa sympa=2.7b.3
sympa sympa=3.0
sympa sympa=3.0a
sympa sympa=3.0a.1
sympa sympa=3.0b.4
sympa sympa=3.0b.8
sympa sympa=3.0b.9
sympa sympa=3.1
sympa sympa=3.1.1
sympa sympa=3.1b.7
sympa sympa=3.1b.8
sympa sympa=3.1b.9
sympa sympa=3.1b.10
sympa sympa=3.1b.12
sympa sympa=3.1b.13
sympa sympa=3.2
sympa sympa=3.2.1
sympa sympa=3.2.2a
sympa sympa=3.3
sympa sympa=3.3.1
sympa sympa=3.3.3
sympa sympa=3.3.4b.3
sympa sympa=3.3.4b.4
sympa sympa=3.3.4b.5
sympa sympa=3.3.4b.6
sympa sympa=3.3.4b.7
sympa sympa=3.3.4b.8
sympa sympa=3.3.4b.9
sympa sympa=3.3.5
sympa sympa=3.3.6b.1
sympa sympa=3.3.6b.2
sympa sympa=3.3.6b.3
sympa sympa=3.3.6b.4
sympa sympa=3.3.6b.5
sympa sympa=3.3.6b.6
sympa sympa=3.3b.3
sympa sympa=3.3b.4
sympa sympa=3.4
sympa sympa=4.0.a1
sympa sympa=4.0.a3
sympa sympa=4.0.a4
sympa sympa=4.0.a5
sympa sympa=4.0.a6
sympa sympa=4.0.a7
sympa sympa=4.0.a8
sympa sympa=4.0.a9
sympa sympa=4.0.b1
sympa sympa=4.0.b2
sympa sympa=4.0.b3
sympa sympa=4.1
sympa sympa=4.2b.1
sympa sympa=4.2b.3
sympa sympa=5.0
sympa sympa=5.0a
sympa sympa=5.0a.1
sympa sympa=5.0b
sympa sympa=5.0b.1
sympa sympa=5.1
sympa sympa=5.1.2
sympa sympa=5.2
sympa sympa=5.2b
sympa sympa=5.2b2
sympa sympa=5.3
sympa sympa=5.3.2
sympa sympa=5.3a.8
sympa sympa=5.3a.9
sympa sympa=5.3a.10
sympa sympa=5.3b.1
sympa sympa=5.3b.3
sympa sympa=5.3b.4
sympa sympa=5.3b.5
sympa sympa=5.4
sympa sympa=5.4.1
sympa sympa=5.4.2
sympa sympa=5.4.3
sympa sympa=5.4a.2
sympa sympa=5.4a.4
sympa sympa=5.4b.1
sympa sympa=6.0
sympa sympa=6.0.1
sympa sympa=6.0.2
sympa sympa=6.0.3
sympa sympa=6.0.4
sympa sympa=6.0.5
sympa sympa=6.0.6
sympa sympa=6.0b.1
sympa sympa=6.0b.2
sympa sympa=6.0b.3
sympa sympa=6.0b.4
sympa sympa=6.1.1
sympa sympa=6.1.2
sympa sympa=6.1.3
sympa sympa=6.1.4
sympa sympa=6.1.5
sympa sympa=6.1.6
sympa sympa=6.1.7
sympa sympa=6.1.8
sympa sympa=6.1.9
sympa sympa=6.1b.1
sympa sympa=6.1b.2
sympa sympa=6.1b.3
sympa sympa=6.1b.4
sympa sympa=6.1b.6

Event History

May 31, 2012
CVE Published
via MITRE·05:00 PM
Data Sourced
via MITRE·05:00 PM
Description

Frequently Asked Questions

1

What is the severity of CVE-2012-2352?

CVE-2012-2352 is classified as a high-severity vulnerability due to its potential for unauthorized access and data manipulation.

2

How do I fix CVE-2012-2352?

To fix CVE-2012-2352, upgrade to Sympa version 6.1.11 or later, which includes a patch that checks permissions.

3

What types of actions can attackers perform due to CVE-2012-2352?

Attackers can list, read, and delete arbitrary list archives using the vulnerable functions affected by CVE-2012-2352.

4

Which versions of Sympa are affected by CVE-2012-2352?

CVE-2012-2352 affects all versions of Sympa before 6.1.11.

5

Is there any workaround for CVE-2012-2352 if I cannot immediately upgrade?

A temporary workaround for CVE-2012-2352 may involve restricting access to the archive management page, but upgrading is strongly recommended.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203