CVE-2009-3386 json
Template.pm in Bugzilla 3.3.2 through 3.4.3 and 3.5 through 3.5.1 allows remote attackers to discover the alias of a private bug by reading…
published 2009-11-20 16 y ago modified 2026-06-16 4 mo ago also EUVD-2009-3368
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.7%
- EPSS 1.7% chance of exploitation in 30 days, percentile 77%
- public exploits
- 0
- none known
Summary
Template.pm in Bugzilla 3.3.2 through 3.4.3 and 3.5 through 3.5.1 allows remote attackers to discover the alias of a private bug by reading the (1) Depends On or (2) Blocks field of a related bug.
Patch / fix
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2009-3386 updated
bugzilla hidden bug alias disclosure
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
1.73% chance of exploitation in the next 30 days, higher than 77% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
References
-
securityfocus.com
/bid/37062
vdb-entry, patch
-
vupen.com
/english/advisories/2009/3288
vdb-entry, patch, vendor-advisory
-
bugzilla.org
/security/3.4.3/
patch, vendor-advisory
-
bugzilla.mozilla.org
/show_bug.cgi?id=529416
patch
-
secunia.com
/advisories/37423
third-party-advisory, vendor-advisory
-
osvdb.org
/60271
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/54332
vdb-entry
Sources
- CVE List CVE-2009-3386
- NVD CVE-2009-3386
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.