Cross-Site Scripting (XSS) in kallithea (CVE-2015-1864)
Summary
Cross-site scripting in kallithea (CVE-2015-1864). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 0.2.1 or later.
Original description
The description as published by the source.
Multiple cross-site scripting (XSS) vulnerabilities in the administration pages in Kallithea before 0.2.1 allow remote attackers to inject arbitrary web script or HTML via the (1) first name or (2) last name user details, or the (3) repository, (4) repository group, or (5) user group description.
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-2015-1864 has been found in kallithea.
Risk of unauthorized operations or information disclosure. CVSS score: 5.4/10.
What to do: upgrade kallithea to 0.2.1 or later.
If unsure, ask your IT team or search "kallithea CVE-2015-1864" on the vendor's site.
CVE-2015-1864 (kallithea) — CWE-79 / CVSS v3 5.4
Attack vector: remote (network-reachable)
Patched: 0.2.1 — 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.
Cross-site scripting (XSS) (CWE-79) exists in kallithea.
Check the vendor advisory for the affected versions of kallithea.
Severity: Medium (CVSS 5.4/10). Risk of unauthorized operations or information disclosure.
Update to 0.2.1.
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 'kallithea' . 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 'kallithea' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
kallitheaを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade kallithea to 0.2.1ステージング環境で 0.2.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- web openwall.com
- web securityfocus.com
- web kallithea-scm.org
- web kallithea-scm.org