Vulnerability in @swiggy-private/aatm-nirbhar-build (GHSA-rc4h-g3gj-3h2g)

Summary

vulnerability in @swiggy-private/aatm-nirbhar-build (GHSA-rc4h-g3gj-3h2g). Risk of unauthorized operations or information disclosure.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **GHSA-rc4h-g3gj-3h2g** has been found in @swiggy-private/aatm-nirbhar-build. 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 "@swiggy-private/aatm-nirbhar-build GHSA-rc4h-g3gj-3h2g" on the vendor's site.

GHSA-rc4h-g3gj-3h2g (@swiggy-private/aatm-nirbhar-build) — 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 @swiggy-private/aatm-nirbhar-build.

📍 Affected scope

@swiggy-private/aatm-nirbhar-build — .

🔥 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 '@swiggy-private/aatm-nirbhar-build' .` 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

1
Identify exposure identify
```
grep -r '@swiggy-private/aatm-nirbhar-build' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `@swiggy-private/aatm-nirbhar-build` を grep し、稼働しているサービス・バージョンを把握する。
7
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

npm @swiggy-private/aatm-nirbhar-build