← Back
CVE-2016-9123
high
CVSS 7.5
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.
AI summary snake-internal / snake-material-v2
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.
❓ What is the problem
**A vulnerability** (CWE-190) exists in github.com/square/go-jose.
📍 Affected scope
github.com/square/go-jose — .
🔥 Severity
Severity: High (CVSS 7.5/10). Data can be tampered with by attackers
🔧 How to fix
Update to **0.0.0-20160903044734-789a4c4bd4c1**.
🛡️ 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/square/go-jose' .` 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/square/go-jose' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `github.com/square/go-jose` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade github.com/square/go-jose to 0.0.0-20160903044734-789a4c4bd4c1ステージング環境で 0.0.0-20160903044734-789a4c4bd4c1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
go
github.com/square/go-jose
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.0.0-20160903044734-789a4c4bd4c1"}]}]
References
- patch af854a3a-2127-422b-91ae-364da2661108
- web https://github.com/square/go-jose/commit/789a4c4bd4c118f7564954f441b29c153ccd6a96
- web https://hackerone.com/reports/165170
- web https://nvd.nist.gov/vuln/detail/CVE-2016-9123
- web https://www.openwall.com/lists/oss-security/2016/11/03/1
- web https://pkg.go.dev/vuln/GO-2020-0009
- web https://github.com/advisories/GHSA-3fx4-7f69-5mmg