Vulnerability in snipe/snipe-it (CVE-2022-23064)
Summary
Vulnerability in snipe/snipe-it (CVE-2022-23064). Risk of unauthorized operations or information disclosure. Exploitable via Host header. Mitigation: upgrade to 5.3.8 or later.
Original description
The description as published by the source.
Snipe-IT is a free, open-source IT asset/license management systemIn Snipe-IT, versions v3.0-alpha to v5.3.7 are vulnerable to Host Header Injection. By sending a specially crafted host header in the reset password request, it is possible to send password reset links to users which once clicked lead to an attacker controlled server and thus leading to password reset token leak. This can lead to account take over.
Source: GitHub Security Advisories (Global) 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-2022-23064 has been found in snipe/snipe-it.
Attackers can target a specific entry point like Host header over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade snipe/snipe-it to 5.3.8 or later.
If unsure, ask your IT team or search "snipe/snipe-it CVE-2022-23064" on the vendor's site.
CVE-2022-23064 (snipe/snipe-it) — CWE-74
Attack surface: Host header
Patched: 5.3.8 — 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-74) exists in snipe/snipe-it. Attackers reach the vulnerable code path via Host header.
Check the vendor advisory for the affected versions of snipe/snipe-it. Attack surface: Host header.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 5.3.8.
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 'snipe/snipe-it' . 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 'snipe/snipe-it' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
snipe/snipe-itを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade snipe/snipe-it to 5.3.8ステージング環境で 5.3.8 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- web nvd.nist.gov
- web github.com
- web whitesourcesoftware.com
- web github.com