Vulnerability in github.com/grpc/grpc-swift (CVE-2021-36155)
Summary
Vulnerability in github.com/grpc/grpc-swift (CVE-2021-36155). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.2.0 or later.
Original description
The description as published by the source.
Impact
Affected gRPC Swift clients and servers are vulnerable to uncontrolled resource consumption attacks. Excessive memory may be allocated when parsing messages. This can lead to a denial of service.
Patches
The problem has been fixed in 1.2.0.
Workarounds
No workaround is available. Users must upgrade.
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-36155 has been found in github.com/grpc/grpc-swift.
Risk of unauthorized operations or information disclosure.
What to do: upgrade github.com/grpc/grpc-swift to 1.2.0 or later.
If unsure, ask your IT team or search "github.com/grpc/grpc-swift CVE-2021-36155" on the vendor's site.
CVE-2021-36155 (github.com/grpc/grpc-swift) — CWE-120
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 1.2.0 — apply immediately
Workaround: No workaround is available.
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.
A vulnerability (CWE-120) exists in github.com/grpc/grpc-swift.
Check the vendor advisory for the affected versions of github.com/grpc/grpc-swift.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1.2.0.
Workaround: No workaround is available.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/grpc/grpc-swift' . 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
-
1Identify exposure identify
grep -r 'github.com/grpc/grpc-swift' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/grpc/grpc-swiftを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
No workaround is available.パッチが適用されるまでの応急処置として、No workaround is available. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade github.com/grpc/grpc-swift to 1.2.0ステージング環境で 1.2.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web bugs.chromium.org
- web github.com