CyberSecBulletin
CVE-2024-7954NVD status: Deferred

SPIP: Improper Neutralization of Directives in Dynamically Evaluated Code

Published Updated By the CyberSecBulletin desk

CVE-2024-7954 is a critical-severity improper neutralization of directives in dynamically evaluated code vulnerability in SPIP, with a CVSS 3.1 base score of 9.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists versions 4.3.0-alpha2, 4.2.13, 4.1.16 as the first without the flaw, so updating SPIP to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 90.1% chance of exploitation within 30 days, which is in the top 0.2% of all scored CVEs.

Patch now

Exploitation in the next 30 days is more likely than not, according to EPSS.

What to do

  1. Update SPIP to 4.3.0-alpha2 or 4.2.13 or 4.1.16, whichever matches your release line, or a later version.
  2. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
SPIPSPIP4.3.0-alpha up to, but not including, 4.3.0-alpha2; 4.2.0 up to, but not including, 4.2.13; 4.1.0 up to, but not including, 4.1.164.3.0-alpha2, 4.2.13, 4.1.16

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
NoneNo action by a victim is required.
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
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by CNA (vulncheck.com).

Official description

The porte_plume plugin used by SPIP before 4.30-alpha2, 4.2.13, and 4.1.16 is vulnerable to an arbitrary code execution vulnerability. A remote and unauthenticated attacker can execute arbitrary PHP as the SPIP user by sending a crafted HTTP request.

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

The underlying weakness: Improper Neutralization of Directives in Dynamically Evaluated Code

The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes code syntax before using the input in a dynamic evaluation call (e.g. eval).

How developers prevent this class of flaw

  • If possible, refactor your code so that it does not need to use eval() at all.
  • For Python programs, it is frequently encouraged to use the ast.literal_eval() function instead of eval, since it is intentionally designed to avoid executing code. However, an adversary could still cause excessive memory or stack consumption via deeply nested structures, so the python documentation discourages use of ast.literal_eval() on untrusted data.

More Improper Neutralization of Directives in Dynamically Evaluated Code vulnerabilities (CWE-95)

Timeline

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

References

Other vulnerabilities in SPIP

All SPIP vulnerabilities

Recent Improper Neutralization of Directives in Dynamically Evaluated Code vulnerabilities

Spotted an error? Tell us.