Vulnerabilities in pkg:npm/dectalk-tts

PACKAGE
Advisory Identifier: GHSA-6cf6-8hvr-r68w
Advisory Summary

CVE-2024-31206 is a HIGH (CVSS 8.2) dectalk-tts uses unencrypted http request vulnerability (CWE-319: Cleartext Transmission of Sensitive Information) affecting Dectalk tts libraries in the npm ecosystem. The issue involves dectalk-tts uses unencrypted http request. Remediation is available by upgrading affected packages to version 1.0.1.

1 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:npm/dectalk-tts

1 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:npm/dectalk-tts. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-6cf6-8hvr-r68w CVE-2024-31206 HIGH dectalk-tts Uses Unencrypted HTTP Request

CVE-2024-31206 at a Glance

CVE Identifier CVE-2024-31206
GHSA Identifier GHSA-6cf6-8hvr-r68w
Severity HIGH
CVSS v3.1 Base Score 8.2
CWE Classification CWE-319: Cleartext Transmission of Sensitive Information
Affected Product Dectalk tts
Package Ecosystem npm
Published Date
Last Updated

Security Impact

CVSS: 8.2

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality Low (C:L)
Integrity High (I:H)
Availability None (A:N)

How to Fix CVE-2024-31206

To remediate this vulnerability, upgrade all affected Dectalk tts dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

dectalk-tts fixed: 1.0.1
npm install dectalk-tts@1.0.1
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls dectalk-tts

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2024-31206, inspect your project dependencies using npm:

npm ls dectalk-tts

Analyze the terminal output to locate any version of Dectalk tts in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.0.1), your application is affected.

Note: The npm ls dectalk-tts command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-319: Cleartext Transmission of Sensitive Information, where the product transmits sensitive or security-critical data in cleartext in a communication channel that can be sniffed by unauthorized actors. In Dectalk tts, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Impact In `dectalk-tts@1.0.0`, 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)](https://en.wikipedia.org/wiki/Man-in-the-middle_attack) 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](https://github.com/JstnMcBrd/dectalk-tts/blob/main/README.md) 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 [Vulnerable code](https://github.com/JstnMcBrd/dectalk-tts/blob/b3e92156cbb699218ac9b9c7d8979abd0e635767/src/index.ts#L18) [Original report](https://github.com/JstnMcBrd/dectalk-tts/issues/3) [Patch pull request](https://github.com/JstnMcBrd/dectalk-tts/pull/4)

CVE-2024-31206 Affected Dectalk tts Versions

1 component(s)
Fixed Versions:
1.0.1
Product / Package Ecosystem Affected Versions Fixed Version
dectalk-tts
npm
≥ 1.0.0
< 1.0.1
All 1 versions
1.0.0
1.0.1

References

Frequently Asked Questions

What is CVE-2024-31206?
CVE-2024-31206 is a security vulnerability in Dectalk tts involving dectalk-tts Uses Unencrypted HTTP Request under CWE-319: Cleartext Transmission of Sensitive Information.
Which Dectalk tts versions are affected?
Affected versions include releases prior to 1.0.1 across affected packages: dectalk-tts.
What version fixes CVE-2024-31206?
Upgrading to 1.0.1 (or the latest patched release for your respective branch) resolves the vulnerability.
Is dectalk-tts affected?
Yes, dectalk-tts is affected in releases prior to 1.0.1. Upgrade your dependency to 1.0.1 or later.
What is the CVSS score of CVE-2024-31206?
CVE-2024-31206 has a CVSS v3.1 base score of 8.2 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N.
What CWE is associated with CVE-2024-31206?
CVE-2024-31206 is classified under CWE-319: Cleartext Transmission of Sensitive Information (The product transmits sensitive or security-critical data in cleartext in a communication channel that can be sniffed by unauthorized actors.).
How can I check npm dependencies for CVE-2024-31206?
Run the dependency tree command: 'npm ls dectalk-tts'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-6cf6-8hvr-r68w",
  "modified" : "2024-04-05T15:44:23Z",
  "published" : "2024-04-04T14:21:19Z",
  "aliases" : [ "CVE-2024-31206" ],
  "summary" : "dectalk-tts Uses Unencrypted HTTP Request",
  "details" : "### Impact\n\nIn `dectalk-tts@1.0.0`, 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)](https://en.wikipedia.org/wiki/Man-in-the-middle_attack) attack.\n\n<ins>Theft</ins>\n\nBecause `dectalk-tts` is a text-to-speech package, user requests are expected to only contain natural language. The package [README](https://github.com/JstnMcBrd/dectalk-tts/blob/main/README.md) warns that user input is sent to a third-party API, so users should not send sensitive information regardless.\n\nBut if users ignore the warnings and send sensitive information anyway, that information could be stolen by attackers.\n\n<ins>Modification</ins>\n\nAttackers could manipulate requests to the API. However, the worst a modified request could do is return an incorrect audio file or bad request rejection.\n\nAttackers 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.\n\n### Patches\n\nThe network request was upgraded to HTTPS in version `1.0.1`. No other changes were made, so updating is risk-free.\n\n### Workarounds\n\nThere are no workarounds, but here are some precautions:\n\n- Do not send any sensitive information.\n\n- Carefully verify the API response before saving it.\n\n### References\n\n[Vulnerable code](https://github.com/JstnMcBrd/dectalk-tts/blob/b3e92156cbb699218ac9b9c7d8979abd0e635767/src/index.ts#L18)\n[Original report](https://github.com/JstnMcBrd/dectalk-tts/issues/3)\n[Patch pull request](https://github.com/JstnMcBrd/dectalk-tts/pull/4)\n",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "dectalk-tts"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "1.0.0"
      }, {
        "fixed" : "1.0.1"
      } ]
    } ],
    "versions" : [ "1.0.0" ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/JstnMcBrd/dectalk-tts/security/advisories/GHSA-6cf6-8hvr-r68w"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2024-31206"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/JstnMcBrd/dectalk-tts/issues/3"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/JstnMcBrd/dectalk-tts/pull/4"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/JstnMcBrd/dectalk-tts/commit/3600d8ac156f27da553ac4ead46d16989a350105"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/JstnMcBrd/dectalk-tts"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/JstnMcBrd/dectalk-tts/blob/b3e92156cbb699218ac9b9c7d8979abd0e635767/src/index.ts#L18"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-300", "CWE-319", "CWE-598" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2024-04-04T14:21:19Z",
    "nvd_published_at" : "2024-04-04T23:15:15Z"
  }
}