CVE Vulnerabilities

CVE-2009-4079

Cross-Site Request Forgery (CSRF)

Published: Nov 25, 2009 | Modified: Apr 09, 2025
CVSS 3.x
N/A
Source:
NVD
CVSS 2.x
6.8 MEDIUM
AV:N/AC:M/Au:N/C:P/I:P/A:P
RedHat/V2
RedHat/V3
Ubuntu
MEDIUM
root.io logo minimus.io logo echo.ai logo

Cross-site request forgery (CSRF) vulnerability in Redmine 0.8.5 and earlier allows remote attackers to hijack the authentication of users for requests that delete a ticket via unspecified vectors.

Weakness

The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.

Affected Software

NameVendorStart VersionEnd Version
RedmineRedmine*0.8.5 (including)
RedmineRedmine0.1.0 (including)0.1.0 (including)
RedmineRedmine0.2.1 (including)0.2.1 (including)
RedmineRedmine0.2.2 (including)0.2.2 (including)
RedmineRedmine0.3.0 (including)0.3.0 (including)
RedmineRedmine0.4.0 (including)0.4.0 (including)
RedmineRedmine0.4.1 (including)0.4.1 (including)
RedmineRedmine0.4.2 (including)0.4.2 (including)
RedmineRedmine0.5.0 (including)0.5.0 (including)
RedmineRedmine0.5.1 (including)0.5.1 (including)
RedmineRedmine0.6.0 (including)0.6.0 (including)
RedmineRedmine0.6.1 (including)0.6.1 (including)
RedmineRedmine0.6.2 (including)0.6.2 (including)
RedmineRedmine0.6.3 (including)0.6.3 (including)
RedmineRedmine0.6.4 (including)0.6.4 (including)
RedmineRedmine0.7.0 (including)0.7.0 (including)
RedmineRedmine0.7.0-rc1 (including)0.7.0-rc1 (including)
RedmineRedmine0.7.1 (including)0.7.1 (including)
RedmineRedmine0.7.2 (including)0.7.2 (including)
RedmineRedmine0.7.3 (including)0.7.3 (including)
RedmineRedmine0.7.4 (including)0.7.4 (including)
RedmineRedmine0.8.0 (including)0.8.0 (including)
RedmineRedmine0.8.0-rc1 (including)0.8.0-rc1 (including)
RedmineRedmine0.8.1 (including)0.8.1 (including)
RedmineRedmine0.8.2 (including)0.8.2 (including)
RedmineRedmine0.8.3 (including)0.8.3 (including)
RedmineRedmine0.8.4 (including)0.8.4 (including)
RedmineUbuntulucid*
RedmineUbuntumaverick*
RedmineUbuntunatty*
RedmineUbuntuoneiric*
RedmineUbuntuprecise*
RedmineUbuntuquantal*
RedmineUbunturaring*
RedmineUbuntusaucy*
RedmineUbuntuupstream*
RedmineUbuntuutopic*
RedmineUbuntuvivid*
RedmineUbuntuwily*
RedmineUbuntuyakkety*
RedmineUbuntuzesty*

Potential Mitigations

  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid [REF-1482].
  • For example, use anti-CSRF packages such as the OWASP CSRFGuard. [REF-330]
  • Another example is the ESAPI Session Management control, which includes a component for CSRF. [REF-45]
  • Use the “double-submitted cookie” method as described by Felten and Zeller:
  • When a user visits a site, the site should generate a pseudorandom value and set it as a cookie on the user’s machine. The site should require every form submission to include this value as a form value and also as a cookie value. When a POST request is sent to the site, the request should only be considered valid if the form value and the cookie value are the same.
  • Because of the same-origin policy, an attacker cannot read or modify the value stored in the cookie. To successfully submit a form on behalf of the user, the attacker would have to correctly guess the pseudorandom value. If the pseudorandom value is cryptographically strong, this will be prohibitively difficult.
  • This technique requires Javascript, so it may not work for browsers that have Javascript disabled. [REF-331]

References