React Native Baidu Voice SynthesizerFramework / library · React Native Baidu Voice Synthesizer Project

CVE-2016-10697

HIGH · 8.1 CVSS v3.0 Published 2018-06-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
react-native-baidu-voice-synthesizer is a baidu voice speech synthesizer for react native. react-native-baidu-voice-synthesizer downloads resources over HTTP, which leaves it vulnerable to MITM attacks. It may be possible to cause remote code execution (RCE) by swapping out the requested resources with an attacker controlled copy if the attacker is on the network or positioned in between the user and the remote server.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The react-native-baidu-voice-synthesizer library downloads voice synthesis resources over unencrypted HTTP connections, making it vulnerable to Man-in-the-Middle (MITM) attacks. An attacker positioned on the network can intercept these downloads and replace the legitimate resources with malicious code, potentially achieving remote code execution on devices running the affected application.

MitigationReplace all HTTP URLs used for downloading resources with HTTPS equivalents, ensuring all network communications are encrypted and server identity is verified to prevent injection attacks.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
React Native Baidu Voice SynthesizerFramework / library
Affected:= 1.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if react-native-baidu-voice-synthesizer is in dependencies
    Inspect package.json file and look for react-native-baidu-voice-synthesizer in the dependencies or devDependencies section
    Affected if The library is listed as a dependency in package.json
  2. Verify the installed version of the library
    Run 'npm list react-native-baidu-voice-synthesizer' or check the package-lock.json file for the installed version
    Affected if The installed version is 1.0.0
  3. Search for HTTP URLs in the library source code
    Locate the node_modules/react-native-baidu-voice-synthesizer directory and grep for 'http://' URLs, particularly in files related to downloading or fetching voice resources
    Affected if HTTP URLs (not HTTPS) are found pointing to voice synthesis resource endpoints
  4. Check if the voice synthesis download feature is used in the application
    Search project source files for imports and usage of the react-native-baidu-voice-synthesizer module (e.g., 'require("react-native-baidu-voice-synthesizer")' or 'import BaiduVoice')
    Affected if The library is imported and its download/synthesize functions are called in application code
  5. Inspect network traffic configuration for voice downloads
    Review any configuration files or code that specifies the voice synthesis API endpoint URL, looking for non-HTTPS schemes
    Affected if The voice synthesis endpoint is configured with an http:// URL rather than https://

A user is affected if react-native-baidu-voice-synthesizer version 1.0.0 is installed AND the library is actively used to download voice synthesis resources over HTTP connections.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace all HTTP URLs used for downloading resources with HTTPS equivalents, ensuring all network communications are encrypted and server identity is verified to prevent injection attacks.

Fix this in React Native Baidu Voice Synthesizer Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,936.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-10697 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-10697 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data