What is the CVSS score of CVE-2012-0453?

CVE-2012-0453 has a CVSS 2.0 base score of 5.1 (Medium). CVSS vector: AV:N/AC:H/Au:N/C:P/I:P/A:P. EPSS exploitation probability: 0.2%.

Is there a patch available for CVE-2012-0453?

Yes, a patch is available for CVE-2012-0453. Update the affected software to the latest version immediately.

Bugzilla CVE-2012-0453

MEDIUM

Cross-Site Request Forgery (CSRF) (CWE-352)

2012-02-25 cve@mitre.org

CSRF Bugzilla

5.1

CVSS 2.0 · NVD

Severity by source

NVD PRIMARY

5.1 MEDIUM

AV:N/AC:H/Au:N/C:P/I:P/A:P

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

AV:N/AC:H/Au:N/C:P/I:P/A:P

Attack Vector

Network

Attack Complexity

High

Confidentiality

Integrity

Availability

Lifecycle Timeline

CVE Published

Feb 25, 2012 - 04:21 cve.org

MEDIUM 5.1

DescriptionCVE.org

Cross-site request forgery (CSRF) vulnerability in xmlrpc.cgi in Bugzilla 4.0.2 through 4.0.4 and 4.1.1 through 4.2rc2, when mod_perl is used, allows remote attackers to hijack the authentication of arbitrary users for requests that modify the product's installation via the XML-RPC API.

AnalysisAI

Cross-site request forgery (CSRF) vulnerability in xmlrpc.cgi in Bugzilla 4.0.2 through 4.0.4 and 4.1.1 through 4.2rc2, when mod_perl is used, allows remote attackers to hijack the authentication of. Rated medium severity (CVSS 5.1), this vulnerability is remotely exploitable.

Technical ContextAI

This vulnerability is classified as Cross-Site Request Forgery (CSRF) (CWE-352), which allows attackers to trick authenticated users into performing unintended actions. Cross-site request forgery (CSRF) vulnerability in xmlrpc.cgi in Bugzilla 4.0.2 through 4.0.4 and 4.1.1 through 4.2rc2, when mod_perl is used, allows remote attackers to hijack the authentication of arbitrary users for requests that modify the product's installation via the XML-RPC API. Affected products include: Mozilla Bugzilla. Version information: through 4.0.4.

RemediationAI

A vendor patch is available. Apply the latest security update as soon as possible. Implement anti-CSRF tokens, validate Origin/Referer headers, use SameSite cookie attribute.