Vulnerability in API Platform (CVE-2019-1000011)

Summary

Vulnerability in API Platform (CVE-2019-1000011). Data can be tampered with by attackers. Mitigation: upgrade to 2.3.6 or later.

Original description

The description as published by the source.

API Platform version from 2.2.0 to 2.3.5 contains an Incorrect Access Control vulnerability in GraphQL delete mutations that can result in a user authorized to delete a resource can delete any resource. This attack appears to be exploitable via the user must be authorized. This vulnerability appears to have been fixed in 2.3.6.

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-2019-1000011 has been found in API Platform.
Data can be tampered with by attackers.
What to do: upgrade API Platform to 2.3.6 or later.
If unsure, ask your IT team or search "API Platform CVE-2019-1000011" on the vendor's site.

CVE-2019-1000011 (API Platform)
Attack vector: remote (network-reachable) / no user interaction
Patched: 2.3.6 — 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 (unclassified) exists in API Platform.

📍 Affected scope

Check the vendor advisory for the affected versions of API Platform.

🔥 Severity

Severity: ?. Data can be tampered with by attackers.

🔧 How to fix

Update to 2.3.6.

🛡️ 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. Audit SBOM/dependencies to find affected services.

Response actions

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

1
Identify exposure identify
```
Audit SBOM/dependencies for affected components.
```
資産台帳・SBOM・依存マニフェストで API Platform を使っているサービスとバージョンを洗い出す。
2
Apply patch patch
```
Upgrade API Platform to 2.3.6
```
ステージング環境で 2.3.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

References

report github.com
report github.com