Vulnerability in tokio-boring (CVE-2023-6180)
Summary
Vulnerability in tokio-boring (CVE-2023-6180). Risk of unauthorized operations or information disclosure. Exploitable via set_ex_data. Mitigation: upgrade to 4.1.0 or later.
Original description
The description as published by the source.
Impact
The tokio-boring library in version 4.0.0 is affected by a memory leak issue that can lead to excessive resource consumption and potential DoS by resource exhaustion. The set_ex_data function used by the library did not deallocate memory used by pre-existing data in memory each time after completing a TLS connection causing the program to consume more resources with each new connection.
Patches
The issue is fixed in version 4.1.0 of tokio-boring.
References
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
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-2023-6180 has been found in tokio-boring.
Attackers can target a specific entry point like set_ex_data over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade tokio-boring to 4.1.0 or later.
If unsure, ask your IT team or search "tokio-boring CVE-2023-6180" on the vendor's site.
CVE-2023-6180 (tokio-boring) — CWE-400
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: set_ex_data
Patched: 4.1.0 — 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-400) exists in tokio-boring. Attackers reach the vulnerable code path via set_ex_data without authentication.
Check the vendor advisory for the affected versions of tokio-boring. Attack surface: set_ex_data.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 4.1.0.
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 'tokio-boring' . 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 'tokio-boring' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
tokio-boringを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade tokio-boring to 4.1.0ステージング環境で 4.1.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com