Skip to content

Form validation can be skipped

Moderate severity GitHub Reviewed Published Jun 21, 2021 in neos/form • Updated Feb 7, 2024

Package

composer neos/form (Composer)

Affected versions

>= 1.2.0, < 4.3.3
>= 5.0.0, < 5.0.9
>= 5.1.0, < 5.1.3

Patched versions

4.3.3
5.0.9
5.1.3

Description

Impact

By crafting a special GET request containing a valid form state, a form can be submitted without invoking any validators.
We consider the severity low because it is not possible to change any form values since the form state is secured with an HMAC that is still verified.
That means that this issue can only be exploited if Form Finishers cause side effects even if no form values have been sent.

Patches

neos/form@69de421

Workarounds

Form Finishers can be adjusted in a way that they only execute an action if the submitted form contains some expected data.
Alternatively a custom Finisher can be added as first finisher.

References

This regression was introduced with neos/form@049d415
Original report: https://tickets.neos.io/#ticket/zoom/411 (internal)

References

@bwaidelich bwaidelich published to neos/form Jun 21, 2021
Reviewed Jun 21, 2021
Published by the National Vulnerability Database Jun 21, 2021
Published to the GitHub Advisory Database Jun 22, 2021
Last updated Feb 7, 2024

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(46th percentile)

Weaknesses

CVE ID

CVE-2021-32697

GHSA ID

GHSA-m5vx-8chx-qvmm

Source code

No known source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.