GHSA-6cf6-8hvr-r68w
HIGHGHSA-6cf6-8hvr-r68w is a high-severity (CVSS 8.2) CWE-300 vulnerability in dectalk-tts. O3 Security confirms whether GHSA-6cf6-8hvr-r68w is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
dectalk-tts Uses Unencrypted HTTP Request
Blast Radius
Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.
dectalk-ttsnpmDescription
Impact
In [email protected], network requests to the third-party API are sent over HTTP, which is unencrypted. Unencrypted traffic can be easily intercepted and modified by attackers. Anyone who uses the package could be the victim of a man-in-the-middle (MITM) attack.
<ins>Theft</ins>
Because dectalk-tts is a text-to-speech package, user requests are expected to only contain natural language. The package README warns that user input is sent to a third-party API, so users should not send sensitive information regardless.
But if users ignore the warnings and send sensitive information anyway, that information could be stolen by attackers.
<ins>Modification</ins>
Attackers could manipulate requests to the API. However, the worst a modified request could do is return an incorrect audio file or bad request rejection.
Attackers could also manipulate responses from the API, returning malicious output to the user. Output is expected to be a wav-encoded buffer, which users will likely save to a file. This could be a dangerous entrypoint to the user's filesystem.
Patches
The network request was upgraded to HTTPS in version 1.0.1. No other changes were made, so updating is risk-free.
Workarounds
There are no workarounds, but here are some precautions:
-
Do not send any sensitive information.
-
Carefully verify the API response before saving it.
References
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | dectalk-tts | ≥ 1.0.0&&< 1.0.1 | 1.0.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for dectalk-tts. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update dectalk-tts to 1.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6cf6-8hvr-r68w is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-6cf6-8hvr-r68w is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-6cf6-8hvr-r68w. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-6cf6-8hvr-r68w in your dependencies?
O3 detects GHSA-6cf6-8hvr-r68w across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.