CVE-2013-0786: Infoleak

Q: 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.

Q: 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.

Q: 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.

Q: 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.

Q: 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.

Published Feb 24, 2013

Updated

The Bugzilla::Search::buildsubselect 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.

Affected Software

113 affected components

Bugzilla<=3.6.12

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.6.10

Bugzilla=3.6.11

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.0.7

Bugzilla=4.0.8

Bugzilla=4.0.9

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

Event History

Feb 24, 2013

CVE Published

via MITRE·11:00 AM

Data Sourced

via MITRE·11:00 AM

Description

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?