dbcve.org
Ipip CoffeeApplication · Ipip

CVE-2016-10673

HIGH · 8.1 CVSS v3.0 Published 2018-06-04
Fix available
A fix is available. Upgrade to after 1.0.9 or later.
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
ipip-coffee queries geolocation information from IP ipip-coffee downloads geolocation resources over HTTP, which leaves it vulnerable to MITM attacks. This could impact the integrity and availability of the data being used to make geolocation decisions by an application.

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 ipip-coffee package downloads geolocation resources over unencrypted HTTP, allowing attackers on the network path to intercept and modify the geolocation data through MITM attacks. This compromises the integrity and availability of geolocation decisions made by applications using this package.

MitigationReplace HTTP URLs with HTTPS equivalents for all geolocation resource downloads to ensure data is transmitted over encrypted channels with server authenticity verification.

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
Ipip CoffeeApplication
Affected:<= 1.0.9

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 ipip-coffee is installed
    Run 'npm list ipip-coffee' or inspect your project's node_modules/ipip-coffee directory and package.json dependencies
    Affected if The package appears in your installed dependencies
  2. Verify the installed version
    Run 'npm list ipip-coffee --depth=0' to see the installed version, or read the version field from node_modules/ipip-coffee/package.json
    Affected if The installed version is 1.0.9 or lower (any version <= 1.0.9)
  3. Inspect the package source for HTTP resource downloads
    Search the node_modules/ipip-coffee directory for HTTP URLs (http://) used to fetch geolocation data. Look for network requests to external geolocation resources in the source files
    Affected if The source code contains 'http://' URLs pointing to geolocation resources instead of 'https://' URLs

You are affected if the ipip-coffee package is installed at version 1.0.9 or lower and the package code downloads geolocation data over unencrypted HTTP URLs.

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.9
Interim mitigation

Replace HTTP URLs with HTTPS equivalents for all geolocation resource downloads to ensure data is transmitted over encrypted channels with server authenticity verification.

Fix this in Ipip Coffee Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-10673 — 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-10673 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