CyberSecBulletin
CVE-2024-24820NVD status: Modified

icingaweb2-module-director: Cross-Site Request Forgery

Published Updated By the CyberSecBulletin desk

CVE-2024-24820 is a high-severity cross-site request forgery vulnerability in icingaweb2-module-director from Icinga, with a CVSS 3.1 base score of 8.3 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, but only if a user takes part, for example by opening a link or file. Affected icingaweb2-module-director versions: >=1.0.0, < 1.8.2; >= 1.9.0, < 1.9.2; >= 1.10.0, < 1.10.3, and others listed below. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.4% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Icinga to 1.8.2 or 1.9.2 or 1.10.3 or 1.11.3, whichever matches your release line, or a later version.
  2. Read the advisory on github.com for workarounds and exact fixed builds.
  3. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
  4. Because the attack needs a user to take part, warn users about unexpected links and files related to this product until it is patched.

Affected products and versions

VendorProductAffected versionsFixed in
Icingaicingaweb2-module-director>=1.0.0, < 1.8.2; >= 1.9.0, < 1.9.2; >= 1.10.0, < 1.10.3; >= 1.11.0, < 1.11.1Not stated
IcingaIcinga1.0.0 up to, but not including, 1.8.2; 1.9.0 up to, but not including, 1.9.2; 1.10.0 up to, but not including, 1.10.3; 1.11.0 up to, but not including, 1.11.31.8.2, 1.9.2, 1.10.3, 1.11.3

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
RequiredA user must take an action such as opening a file or link.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
LowPerformance or availability is reduced.

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:L. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 3.18.3HighCNA (github.com)
CVSS 3.18.3HighNVD

Official description

Icinga Director is a tool designed to make Icinga 2 configuration handling easy. Not any of Icinga Director's configuration forms used to manipulate the monitoring environment are protected against cross site request forgery (CSRF). It enables attackers to perform changes in the monitoring environment managed by Icinga Director without the awareness of the victim. Users of the map module in version 1.x, should immediately upgrade to v2.0. The mentioned XSS vulnerabilities in Icinga Web are already fixed as well and upgrades to the most recent release of the 2.9, 2.10 or 2.11 branch must be performed if not done yet. Any later major release is also suitable. Icinga Director will receive minor updates to the 1.8, 1.9, 1.10 and 1.11 branches to remedy this issue. Upgrade immediately to a patched release. If that is not feasible, disable the director module for the time being.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Cross-Site Request Forgery

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.

How developers prevent this class of flaw

  • 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. Another example is the ESAPI Session Management control, which includes a component for CSRF.
  • Ensure that the application is free of cross-site scripting issues (CWE-79), because most CSRF defenses can be bypassed using attacker-controlled script.
  • Generate a unique nonce for each form, place the nonce into the form, and verify the nonce upon receipt of the form. Be sure that the nonce is not predictable (CWE-330).

More Cross-Site Request Forgery vulnerabilities (CWE-352)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: poc, automatable: no, technical impact: partial).
  3. Record last changed materially (score, affected products, status or references).

References

Third-party and government advisories

Recent Cross-Site Request Forgery vulnerabilities

Spotted an error? Tell us.