CyberSecBulletin
CVE-2022-25271NVD status: Modified

Drupal core's form API has a vulnerability where certain contributed or custom modules' forms…

Published Updated By the CyberSecBulletin desk

CVE-2022-25271 is a high-severity improper input validation vulnerability in Core from Drupal, with a CVSS 3.1 base score of 7.5 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 9.3.6, 9.2.13, 7.88 as the first without the flaw, so updating Core to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 1.27% chance of exploitation within 30 days, higher than 70% of scored CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Core to 9.3.6 or 9.2.13 or 7.88, whichever matches your release line, or a later version.
  2. Update Drupal to 7.88 or 9.2.13 or 9.3.6, whichever matches your release line, or a later version.
  3. Read the advisory on drupal.org for workarounds and exact fixed builds.
  4. 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
DrupalCore9.3.x up to, but not including, 9.3.6; 9.2.x up to, but not including, 9.2.13; 7.x up to, but not including, 7.889.3.6, 9.2.13, 7.88
DrupalDrupal7.0.0 up to, but not including, 7.88; 9.2.0 up to, but not including, 9.2.13; 9.3.0 up to, but not including, 9.3.67.88, 9.2.13, 9.3.6
Fedora ProjectFedora35; 36Not stated

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
NoneNo data is disclosed.
Integrity
HighData or code can be modified at will.
Availability
NoneAvailability is not affected.

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

Scoring systemScoreSeverityScored by
CVSS 3.17.5HighNVD
CVSS 2.04.3MediumNVD

Official description

Drupal core's form API has a vulnerability where certain contributed or custom modules' forms may be vulnerable to improper input validation. This could allow an attacker to inject disallowed values or overwrite data. Affected forms are uncommon, but in certain cases an attacker could alter critical or sensitive data.

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

The underlying weakness: Improper Input Validation

The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.

How developers prevent this class of flaw

  • Consider using language-theoretic security (LangSec) techniques that characterize inputs using a formal language and build recognizers for that language. This effectively requires parsing to be a distinct layer that effectively enforces a boundary between raw input and internal data representations, instead of allowing parser code to be scattered throughout the program, where it could be subject to errors or inconsistencies that create weaknesses.
  • Use an input validation framework such as Struts or the OWASP ESAPI Validation API. Note that using a framework does not automatically address all input validation problems; be mindful of weaknesses that could arise from misusing the framework itself (CWE-1173).
  • Understand all the potential areas where untrusted inputs can enter the product, including but not limited to: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide data to the application. Remember that such inputs may be obtained indirectly through API calls.

More Improper Input Validation vulnerabilities (CWE-20)

Timeline

  1. CVE record published.
  2. Record last changed materially (score, affected products, status or references).

References

Other vulnerabilities in Core

All Core vulnerabilities

Recent Improper Input Validation vulnerabilities

Spotted an error? Tell us.