CVE Vulnerabilities

CVE-2008-5028

Cross-Site Request Forgery (CSRF)

Published: Nov 10, 2008 | Modified: Nov 07, 2023
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

Cross-site request forgery (CSRF) vulnerability in cmd.cgi in (1) Nagios 3.0.5 and (2) op5 Monitor before 4.0.1 allows remote attackers to send commands to the Nagios process, and trigger execution of arbitrary programs by this process, via unspecified HTTP requests.

Weakness

The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request.

Affected Software

Name Vendor Start Version End Version
Nagios Nagios 3.0 3.0
Nagios Nagios 2.0b5 2.0b5
Nagios Nagios 2.7 2.7
Nagios Nagios 2.4 2.4
Nagios Nagios 3.0 3.0
Monitor Op5 * 4.0.0
Nagios Nagios 3.0 3.0
Nagios Nagios 2.0b6 2.0b6
Nagios Nagios 1.0b3 1.0b3
Nagios Nagios 1.1 1.1
Nagios Nagios 3.0 3.0
Nagios Nagios 2.1 2.1
Monitor Op5 3.3.1 3.3.1
Nagios Nagios 1.0b6 1.0b6
Nagios Nagios 3.0.1 3.0.1
Nagios Nagios 1.0 1.0
Nagios Nagios 2.3.1 2.3.1
Nagios Nagios 3.0 3.0
Nagios Nagios 2.2 2.2
Nagios Nagios 3.0 3.0
Monitor Op5 3.2 3.2
Nagios Nagios 2.0b2 2.0b2
Monitor Op5 2.8 2.8
Monitor Op5 3.2.4 3.2.4
Nagios Nagios 1.0b4 1.0b4
Nagios Nagios 3.0.2 3.0.2
Nagios Nagios 2.5 2.5
Nagios Nagios 2.0b4 2.0b4
Nagios Nagios 2.8 2.8
Nagios Nagios * 3.0.4
Nagios Nagios 3.0 3.0
Nagios Nagios 2.10 2.10
Nagios Nagios 1.2 1.2
Nagios Nagios 3.0 3.0
Nagios Nagios 3.0 3.0
Nagios Nagios 1.0b5 1.0b5
Monitor Op5 3.3.3 3.3.3
Nagios Nagios 1.0_b3 1.0_b3
Nagios Nagios 2.0b1 2.0b1
Monitor Op5 2.6 2.6
Nagios Nagios 3.0 3.0
Nagios Nagios 2.0 2.0
Nagios Nagios 1.4 1.4
Nagios Nagios 3.0 3.0
Nagios Nagios 1.4.1 1.4.1
Nagios Nagios 3.0 3.0
Nagios Nagios 2.0b3 2.0b3
Nagios Nagios 1.3 1.3
Nagios Nagios 2.11 2.11
Nagios Nagios 3.0 3.0
Monitor Op5 3.0.0 3.0.0
Nagios Nagios 2.0rc1 2.0rc1
Nagios Nagios 3.0 3.0
Nagios Nagios 1.0_b1 1.0_b1
Nagios Nagios 2.3 2.3
Nagios Nagios 1.0b1 1.0b1
Nagios Nagios 3.0 3.0
Nagios Nagios 3.0.3 3.0.3
Monitor Op5 3.3.2 3.3.2
Nagios Nagios 1.0b2 1.0b2
Nagios Nagios 2.9 2.9
Nagios Nagios 1.0_b2 1.0_b2
Nagios Nagios 2.0rc2 2.0rc2
Monitor Op5 2.4 2.4
Monitor Op5 3.0 3.0

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