medium
5
CWE
200
Advisory Published
Updated

CVE-2013-0786: Infoleak

First published: Sun Feb 24 2013(Updated: )

The Bugzilla::Search::build_subselect function in Bugzilla 2.x and 3.x before 3.6.13 and 3.7.x and 4.0.x before 4.0.10 generates different error messages for invalid product queries depending on whether a product exists, which allows remote attackers to discover private product names by using debug mode for a query.

Credit: security@mozilla.org

Affected SoftwareAffected VersionHow to fix
Mozilla Bugzilla<=3.6.12
Mozilla Bugzilla=3.6
Mozilla Bugzilla=3.6-rc1
Mozilla Bugzilla=3.6.0
Mozilla Bugzilla=3.6.1
Mozilla Bugzilla=3.6.2
Mozilla Bugzilla=3.6.3
Mozilla Bugzilla=3.6.4
Mozilla Bugzilla=3.6.5
Mozilla Bugzilla=3.6.6
Mozilla Bugzilla=3.6.7
Mozilla Bugzilla=3.6.8
Mozilla Bugzilla=3.6.9
Mozilla Bugzilla=3.6.10
Mozilla Bugzilla=3.6.11
Mozilla Bugzilla=3.7
Mozilla Bugzilla=3.7.1
Mozilla Bugzilla=3.7.2
Mozilla Bugzilla=3.7.3
Mozilla Bugzilla=4.0
Mozilla Bugzilla=4.0-rc1
Mozilla Bugzilla=4.0-rc2
Mozilla Bugzilla=4.0.1
Mozilla Bugzilla=4.0.2
Mozilla Bugzilla=4.0.3
Mozilla Bugzilla=4.0.4
Mozilla Bugzilla=4.0.5
Mozilla Bugzilla=4.0.6
Mozilla Bugzilla=4.0.7
Mozilla Bugzilla=4.0.8
Mozilla Bugzilla=4.0.9
Mozilla Bugzilla=2.0
Mozilla Bugzilla=2.2
Mozilla Bugzilla=2.4
Mozilla Bugzilla=2.6
Mozilla Bugzilla=2.8
Mozilla Bugzilla=2.9
Mozilla Bugzilla=2.10
Mozilla Bugzilla=2.12
Mozilla Bugzilla=2.14
Mozilla Bugzilla=2.14.1
Mozilla Bugzilla=2.14.2
Mozilla Bugzilla=2.14.3
Mozilla Bugzilla=2.14.4
Mozilla Bugzilla=2.14.5
Mozilla Bugzilla=2.16
Mozilla Bugzilla=2.16-rc1
Mozilla Bugzilla=2.16-rc2
Mozilla Bugzilla=2.16.1
Mozilla Bugzilla=2.16.2
Mozilla Bugzilla=2.16.3
Mozilla Bugzilla=2.16.4
Mozilla Bugzilla=2.16.5
Mozilla Bugzilla=2.16.6
Mozilla Bugzilla=2.16.7
Mozilla Bugzilla=2.16.8
Mozilla Bugzilla=2.16.9
Mozilla Bugzilla=2.16.10
Mozilla Bugzilla=2.16.11
Mozilla Bugzilla=2.17
Mozilla Bugzilla=2.17.1
Mozilla Bugzilla=2.17.2
Mozilla Bugzilla=2.17.3
Mozilla Bugzilla=2.17.4
Mozilla Bugzilla=2.17.5
Mozilla Bugzilla=2.17.6
Mozilla Bugzilla=2.17.7
Mozilla Bugzilla=2.18
Mozilla Bugzilla=2.18-rc1
Mozilla Bugzilla=2.18-rc2
Mozilla Bugzilla=2.18-rc3
Mozilla Bugzilla=2.18.1
Mozilla Bugzilla=2.18.2
Mozilla Bugzilla=2.18.3
Mozilla Bugzilla=2.18.4
Mozilla Bugzilla=2.18.5
Mozilla Bugzilla=2.18.6
Mozilla Bugzilla=2.18.6\+
Mozilla Bugzilla=2.18.7
Mozilla Bugzilla=2.18.8
Mozilla Bugzilla=2.18.9
Mozilla Bugzilla=2.19
Mozilla Bugzilla=2.19.1
Mozilla Bugzilla=2.19.2
Mozilla Bugzilla=2.19.3
Mozilla Bugzilla=2.20
Mozilla Bugzilla=2.20-rc1
Mozilla Bugzilla=2.20-rc2
Mozilla Bugzilla=2.20.1
Mozilla Bugzilla=2.20.2
Mozilla Bugzilla=2.20.3
Mozilla Bugzilla=2.20.4
Mozilla Bugzilla=2.20.5
Mozilla Bugzilla=2.20.6
Mozilla Bugzilla=2.20.7
Mozilla Bugzilla=2.21
Mozilla Bugzilla=2.21.1
Mozilla Bugzilla=2.21.2
Mozilla Bugzilla=2.21.2-rc1
Mozilla Bugzilla=2.22
Mozilla Bugzilla=2.22-rc1
Mozilla Bugzilla=2.22.1
Mozilla Bugzilla=2.22.2
Mozilla Bugzilla=2.22.3
Mozilla Bugzilla=2.22.4
Mozilla Bugzilla=2.22.5
Mozilla Bugzilla=2.22.6
Mozilla Bugzilla=2.22.7
Mozilla Bugzilla=2.23
Mozilla Bugzilla=2.23.1
Mozilla Bugzilla=2.23.2
Mozilla Bugzilla=2.23.3
Mozilla Bugzilla=2.23.4

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.

Read MoreStart Free Trial

Reference Links

Frequently Asked Questions

  • What is the severity of CVE-2013-0786?

    CVE-2013-0786 has a medium severity rating as it allows remote attackers to discover private product names.

  • How do I fix CVE-2013-0786?

    To fix CVE-2013-0786, upgrade Bugzilla to version 3.6.13, 3.7.x, or 4.0.10 or later.

  • What versions of Bugzilla are affected by CVE-2013-0786?

    CVE-2013-0786 affects Bugzilla versions 2.x and 3.x before 3.6.13, as well as 3.7.x and 4.0.x before 4.0.10.

  • What types of attacks can exploit CVE-2013-0786?

    An attacker can exploit CVE-2013-0786 by sending invalid product queries to obtain error messages that disclose private product names.

  • Is there a workaround for CVE-2013-0786?

    There is no known workaround for CVE-2013-0786; upgrading to a fixed version is the recommended mitigation.

Company

Resources

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.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203