Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2021-32697

Vulnerability in neos/form (CVE-2021-32697)

Summary

Vulnerability in neos/form (CVE-2021-32697). Risk of unauthorized operations or information disclosure. Exploitable via GET. Mitigation: upgrade to 5.1.3 or later.

Original description

The description as published by the source.

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

https://github.com/neos/form/commit/69de4219b1f58157e2be6b05811463875d75c246

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 https://github.com/neos/form/commit/049d415295be8d4a0478ccba97dba1bb81649567
Original report: https://tickets.neos.io/#ticket/zoom/411 (internal)

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2021-32697 has been found in neos/form.
Attackers can target a specific entry point like GET over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade neos/form to 5.1.3 or later.
If unsure, ask your IT team or search "neos/form CVE-2021-32697" on the vendor's site.

CVE-2021-32697 (neos/form) — CWE-20
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: GET
Patched: 5.1.3 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-20) exists in neos/form. Attackers reach the vulnerable code path via GET without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of neos/form. Attack surface: GET.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 5.1.3.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'neos/form' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'neos/form' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で neos/form を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade neos/form to 5.1.3

    ステージング環境で 5.1.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Packagist neos/form
[{"type":"ECOSYSTEM","events":[{"introduced":"5.1.0"},{"fixed":"5.1.3"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details