← Back
CVE-2024-23332
Vulnerability in github.com/notaryproject/notation (CVE-2024-23332)
Summary
vulnerability in github.com/notaryproject/notation (CVE-2024-23332). Risk of unauthorized operations or information disclosure. Exploitable via ``permissive``.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2024-23332** has been found in github.com/notaryproject/notation.
Attackers can target a specific entry point like ``permissive`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "github.com/notaryproject/notation CVE-2024-23332" on the vendor's site.
CVE-2024-23332 (github.com/notaryproject/notation) — CWE-672 /
Attack vector: remote (network-reachable)
Attack surface: `permissive` / `strict` / `audit` / `skip`
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-672) exists in github.com/notaryproject/notation. Attackers reach the vulnerable code path via ``permissive`` without authentication.
📍 Affected scope
github.com/notaryproject/notation — . Attack surface: `permissive` / `strict` / `audit` / `skip`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to the patched release per vendor advisory.
🛡️ 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 'github.com/notaryproject/notation' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/notaryproject/notation' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `github.com/notaryproject/notation` を grep し、稼働しているサービス・バージョンを把握する。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Go
github.com/notaryproject/notation
[{"type":"SEMVER","events":[{"introduced":"0"},{"last_affected":"1.0.0"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2024-23332
- package https://github.com/notaryproject/specifications
- web https://github.com/notaryproject/specifications/security/advisories/GHSA-57wx-m636-g3g8
- web https://github.com/notaryproject/specifications/commit/cdabdd1042de2999c685fa5d422a785ded9c983a