CVE-2012-1969: Medium severity bugzilla vulnerability

Published Jul 28, 2012
·
Updated

The getattachmentlink function in Template.pm in Bugzilla 2.x and 3.x before 3.6.10, 3.7.x and 4.0.x before 4.0.7, 4.1.x and 4.2.x before 4.2.2, and 4.3.x before 4.3.2 does not check whether an attachment is private before presenting the attachment description within a public comment, which allows remote attackers to obtain sensitive description information by reading a comment.

Affected Software

173 affected components
Bugzilla=2.0
Bugzilla=2.2
Bugzilla=2.4
Bugzilla=2.6
Bugzilla=2.8
Bugzilla=2.9
Bugzilla=2.10
Bugzilla=2.12
Bugzilla=2.14
Bugzilla=2.14.1
Bugzilla=2.14.2
Bugzilla=2.14.3
Bugzilla=2.14.4
Bugzilla=2.14.5
Bugzilla=2.16
Bugzilla=2.16-rc1
Bugzilla=2.16-rc2
Bugzilla=2.16.1
Bugzilla=2.16.2
Bugzilla=2.16.3
Bugzilla=2.16.4
Bugzilla=2.16.5
Bugzilla=2.16.6
Bugzilla=2.16.7
Bugzilla=2.16.8
Bugzilla=2.16.9
Bugzilla=2.16.10
Bugzilla=2.16.11
Bugzilla=2.17
Bugzilla=2.17.1
Bugzilla=2.17.2
Bugzilla=2.17.3
Bugzilla=2.17.4
Bugzilla=2.17.5
Bugzilla=2.17.6
Bugzilla=2.17.7
Bugzilla=2.18
Bugzilla=2.18-rc1
Bugzilla=2.18-rc2
Bugzilla=2.18-rc3
Bugzilla=2.18.1
Bugzilla=2.18.2
Bugzilla=2.18.3
Bugzilla=2.18.4
Bugzilla=2.18.5
Bugzilla=2.18.6
Bugzilla=2.18.6\+
Bugzilla=2.18.7
Bugzilla=2.18.8
Bugzilla=2.18.9
Bugzilla=2.19
Bugzilla=2.19.1
Bugzilla=2.19.2
Bugzilla=2.19.3
Bugzilla=2.20
Bugzilla=2.20-rc1
Bugzilla=2.20-rc2
Bugzilla=2.20.1
Bugzilla=2.20.2
Bugzilla=2.20.3
Bugzilla=2.20.4
Bugzilla=2.20.5
Bugzilla=2.20.6
Bugzilla=2.20.7
Bugzilla=2.21
Bugzilla=2.21.1
Bugzilla=2.21.2
Bugzilla=2.21.2-rc1
Bugzilla=2.22
Bugzilla=2.22-rc1
Bugzilla=2.22.1
Bugzilla=2.22.2
Bugzilla=2.22.3
Bugzilla=2.22.4
Bugzilla=2.22.5
Bugzilla=2.22.6
Bugzilla=2.22.7
Bugzilla=2.23
Bugzilla=2.23.1
Bugzilla=2.23.2
Bugzilla=2.23.3
Bugzilla=2.23.4
Bugzilla=3.0
Bugzilla=3.0-rc1
Bugzilla=3.0.0
Bugzilla=3.0.1
Bugzilla=3.0.2
Bugzilla=3.0.3
Bugzilla=3.0.4
Bugzilla=3.0.5
Bugzilla=3.0.6
Bugzilla=3.0.7
Bugzilla=3.0.8
Bugzilla=3.0.9
Bugzilla=3.0.10
Bugzilla=3.0.11
Bugzilla=3.1.0
Bugzilla=3.1.1
Bugzilla=3.1.2
Bugzilla=3.1.3
Bugzilla=3.1.4
Bugzilla=3.2
Bugzilla=3.2-rc1
Bugzilla=3.2-rc2
Bugzilla=3.2.1
Bugzilla=3.2.2
Bugzilla=3.2.3
Bugzilla=3.2.4
Bugzilla=3.2.5
Bugzilla=3.2.6
Bugzilla=3.2.7
Bugzilla=3.2.8
Bugzilla=3.2.9
Bugzilla=3.2.10
Bugzilla=3.3
Bugzilla=3.3.1
Bugzilla=3.3.2
Bugzilla=3.3.3
Bugzilla=3.3.4
Bugzilla=3.4
Bugzilla=3.4-rc1
Bugzilla=3.4.1
Bugzilla=3.4.2
Bugzilla=3.4.3
Bugzilla=3.4.4
Bugzilla=3.4.5
Bugzilla=3.4.6
Bugzilla=3.4.7
Bugzilla=3.4.8
Bugzilla=3.4.9
Bugzilla=3.4.10
Bugzilla=3.4.11
Bugzilla=3.4.12
Bugzilla=3.4.13
Bugzilla=3.5
Bugzilla=3.5.1
Bugzilla=3.5.2
Bugzilla=3.5.3
Bugzilla=3.6
Bugzilla=3.6-rc1
Bugzilla=3.6.0
Bugzilla=3.6.1
Bugzilla=3.6.2
Bugzilla=3.6.3
Bugzilla=3.6.4
Bugzilla=3.6.5
Bugzilla=3.6.6
Bugzilla=3.6.7
Bugzilla=3.6.8
Bugzilla=3.6.9
Bugzilla=3.7
Bugzilla=3.7.1
Bugzilla=3.7.2
Bugzilla=3.7.3
Bugzilla=4.0
Bugzilla=4.0-rc1
Bugzilla=4.0-rc2
Bugzilla=4.0.1
Bugzilla=4.0.2
Bugzilla=4.0.3
Bugzilla=4.0.4
Bugzilla=4.0.5
Bugzilla=4.0.6
Bugzilla=4.1
Bugzilla=4.1.1
Bugzilla=4.1.2
Bugzilla=4.1.3
Bugzilla=4.2
Bugzilla=4.2-rc1
Bugzilla=4.2-rc2
Bugzilla=4.2.1
Bugzilla=4.3
Bugzilla=4.3.1

Event History

Jul 28, 2012
CVE Published
via MITRE·06:00 PM
Data Sourced
via MITRE·06:00 PM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2012-1969?

The severity of CVE-2012-1969 is classified as a Medium risk, as it involves the exposure of private attachment descriptions in public comments.

2

How do I fix CVE-2012-1969?

To fix CVE-2012-1969, update your Bugzilla installation to version 3.6.10, 3.7.4, 4.0.7, 4.2.2, or 4.3.2 or later.

3

What versions of Bugzilla are affected by CVE-2012-1969?

CVE-2012-1969 affects Bugzilla versions 2.x and 3.x prior to 3.6.10, 3.7.x prior to 4.0.7, and 4.1.x and 4.2.x prior to 4.2.2.

4

What kind of attack can exploit CVE-2012-1969?

CVE-2012-1969 can be exploited to disclose private information within public comments, potentially exposing sensitive attachment descriptions.

5

Is there a workaround for CVE-2012-1969?

There is no official workaround for CVE-2012-1969 other than upgrading to a patched version of Bugzilla.

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