Buffer Overflow in tlslite (CVE-2015-3220)
Summary
Vulnerability in tlslite (CVE-2015-3220). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to aca8d4f898b436ff6754e1a9ab96cae976c8a853, 0.4.9 or later.
Original description
The description as published by the source.
The tlslite library before 0.4.9 for Python allows remote attackers to trigger a denial of service (runtime exception and process crash).
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-3220 has been found in tlslite.
Risk of unauthorized operations or information disclosure. CVSS score: 7.5/10.
What to do: upgrade tlslite to aca8d4f898b436ff6754e1a9ab96cae976c8a853, 0.4.9 or later.
If unsure, ask your IT team or search "tlslite CVE-2015-3220" on the vendor's site.
CVE-2015-3220 (tlslite) — CWE-119 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: aca8d4f898b436ff6754e1a9ab96cae976c8a853, 0.4.9 — 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-119) exists in tlslite.
Check the vendor advisory for the affected versions of tlslite.
Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure.
Update to aca8d4f898b436ff6754e1a9ab96cae976c8a853, 0.4.9.
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 'tlslite' . 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 'tlslite' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
tlsliteを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade tlslite to aca8d4f898b436ff6754e1a9ab96cae976c8a853, 0.4.9ステージング環境で aca8d4f898b436ff6754e1a9ab96cae976c8a853, 0.4.9 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- patch github.com
- report bugzilla.redhat.com
- web groups.google.com
- web groups.google.com