← Back
GHSA-429q-fhh4-r6hj
Vulnerability in anchor-lang (GHSA-429q-fhh4-r6hj)
Summary
vulnerability in anchor-lang (GHSA-429q-fhh4-r6hj). Risk of unauthorized operations or information disclosure. Exploitable via ``InterfaceAccount``. Mitigation: upgrade to `1.0.0-rc.2` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **GHSA-429q-fhh4-r6hj** has been found in anchor-lang.
Attackers can target a specific entry point like ``InterfaceAccount`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade anchor-lang to **1.0.0-rc.2** or later.
If unsure, ask your IT team or search "anchor-lang GHSA-429q-fhh4-r6hj" on the vendor's site.
GHSA-429q-fhh4-r6hj (anchor-lang) — CWE-20 /
Attack surface: `InterfaceAccount`
Patched: `1.0.0-rc.2` — 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 anchor-lang. Attackers reach the vulnerable code path via ``InterfaceAccount`` without authentication.
📍 Affected scope
anchor-lang — . Attack surface: `InterfaceAccount`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **1.0.0-rc.2**.
🛡️ 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 'anchor-lang' .` 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 'anchor-lang' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `anchor-lang` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade anchor-lang to 1.0.0-rc.2ステージング環境で 1.0.0-rc.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
rust
anchor-lang
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.0.0-rc.2"}]}]
References
- web https://github.com/solana-foundation/anchor/security/advisories/GHSA-429q-fhh4-r6hj
- web https://github.com/solana-foundation/anchor/pull/3837
- web https://github.com/solana-foundation/anchor/pull/4139
- web https://github.com/solana-foundation/anchor/commit/26ef36968a62e28a1f028e7adae4806af30c747d
- web https://github.com/advisories/GHSA-429q-fhh4-r6hj