dbcve.org
Bionode SraApplication · Bionode

CVE-2016-10613

MEDIUM · 5.9 CVSS v3.0 Published 2018-06-01
Fix available
A fix is available. Upgrade to after 1.0.3 or later.
See remediation →
68/100
Remediation priority · Elevated
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
bionode-sra is a Node.js wrapper for SRA Toolkit. bionode-sra downloads data resources over HTTP, which leaves it vulnerable to MITM attacks.

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

bionode-sra is a Node.js wrapper for the SRA Toolkit that downloads data resources over unencrypted HTTP, allowing remote attackers to intercept or modify the downloaded data through Man-in-the-Middle attacks.

MitigationReplace all HTTP URLs with HTTPS for data resource downloads to enable encrypted transport and prevent MITM 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
Bionode SraApplication
Affected:<= 1.0.3

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
None
Availability
None

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

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 bionode-sra is installed
    Run 'npm list bionode-sra' in your project directory or check package.json dependencies
    Affected if bionode-sra appears in the installed packages or dependencies
  2. Identify the installed version
    Run 'npm list bionode-sra' to see the installed version number, or check the version field in package.json
    Affected if The version is 1.0.3 or lower
  3. Inspect source code for HTTP download URLs
    Search the bionode-sra package files (typically in node_modules/bionode-sra/) for 'http://' URLs, particularly in files handling data retrieval
    Affected if HTTP URLs are present in code that handles SRA data downloads
  4. Check module configuration for unencrypted connections
    Review any configuration files or initialization code in bionode-sra for data source URLs
    Affected if Configuration specifies HTTP instead of HTTPS endpoints for data retrieval
  5. Verify if SRA data downloads use unencrypted transport
    Run a test download operation with network monitoring (e.g., Wireshark) to observe the protocol used
    Affected if The traffic to SRA data sources travels over plain HTTP

You are affected if bionode-sra version 1.0.3 or lower is installed AND your environment downloads SRA data over unencrypted 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
Upgrade available Upgrade to a release after 1.0.3
Interim mitigation

Replace all HTTP URLs with HTTPS for data resource downloads to enable encrypted transport and prevent MITM attacks.

Fix this in Bionode Sra Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Get it on GitHub Scan in the browser

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-10613 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