Vulnerability in github.com/square/go-jose (CVE-2016-9123)
Summary
Vulnerability in github.com/square/go-jose (CVE-2016-9123). Data can be tampered with by attackers. Mitigation: upgrade to 0.0.0-20160903044734-789a4c4bd4c1 or later.
Original description
The description as published by the source.
go-jose before 1.0.5 suffers from a CBC-HMAC integer overflow on 32-bit architectures. An integer overflow could lead to authentication bypass for CBC-HMAC encrypted ciphertexts on 32-bit architectures.
Source: NIST National Vulnerability Database NVD GitHub Advisory
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-2016-9123 has been found in github.com/square/go-jose.
Data can be tampered with by attackers. CVSS score: 7.5/10.
What to do: upgrade github.com/square/go-jose to 0.0.0-20160903044734-789a4c4bd4c1 or later.
If unsure, ask your IT team or search "github.com/square/go-jose CVE-2016-9123" on the vendor's site.
CVE-2016-9123 (github.com/square/go-jose) — CWE-190 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 0.0.0-20160903044734-789a4c4bd4c1 — 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.
A vulnerability (CWE-190) exists in github.com/square/go-jose.
Check the vendor advisory for the affected versions of github.com/square/go-jose.
Severity: High (CVSS 7.5/10). Data can be tampered with by attackers.
Update to 0.0.0-20160903044734-789a4c4bd4c1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/square/go-jose' . 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/square/go-jose' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/square/go-joseを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/square/go-jose to 0.0.0-20160903044734-789a4c4bd4c1ステージング環境で 0.0.0-20160903044734-789a4c4bd4c1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2016-9123 golang-gopkg-square-go-jose.v1 Fixed in: 1.0.5-1
References
- advisory nvd.nist.gov
- patch openwall.com
- patch github.com
- report hackerone.com
- web openwall.com
- web pkg.go.dev
- web github.com