CVE-2012-0440 json
Cross-site request forgery (CSRF) vulnerability in jsonrpc.cgi in Bugzilla 3.5.x and 3.6.x before 3.6.8, 3.7.x and 4.0.x before 4.0.4, and…
published 2012-02-02 14 y ago modified 2026-06-16 4 mo ago also EUVD-2012-0472
- cvss
- 5.1
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 49%
- public exploits
- 0
- none known
Summary
Cross-site request forgery (CSRF) vulnerability in jsonrpc.cgi in Bugzilla 3.5.x and 3.6.x before 3.6.8, 3.7.x and 4.0.x before 4.0.4, and 4.1.x and 4.2.x before 4.2rc2 allows remote attackers to hijack the authentication of arbitrary users for requests that use the JSON-RPC API.
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-2012-0440 updated cvss 4.3
bugzila: two flaws fixed in 4.2rc2, 4.0.4, 3.6.8, and 3.4.14
-
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
0.60% chance of exploitation in the next 30 days, higher than 49% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- bugzilla.mozilla.org https://bugzilla.mozilla.org/show_bug.cgi?id=718319 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.1 | AV:N/AC:H/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-352 Cross-Site Request Forgery
References
-
bugzilla.mozilla.org
/show_bug.cgi?id=718319
exploit, patch
-
bugzilla.org
/security/3.4.13/
vendor-advisory
-
secunia.com
/advisories/47814
third-party-advisory
-
securitytracker.com
/id?1026623
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/72882
vdb-entry
Sources
- CVE List CVE-2012-0440
- NVD CVE-2012-0440
Fencer Intel 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.