CVE-2016-10602
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 · uneditedhaxe is a cross-platform toolkit haxe downloads zipped 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 zip file with an attacker controlled zip file 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 confidenceThe haxe cross-platform toolkit downloads zipped resources over unencrypted HTTP, allowing attackers positioned on the network to perform Man-in-the-Middle (MITM) attacks. Attackers can replace legitimate zip files with malicious ones during transit, potentially leading to remote code execution when the zip is extracted and executed.
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<= 5.0.10CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Haxe versionRun 'haxe -version' or 'haxe --version' in a terminal to determine the installed version numberAffected if The version displayed is 5.0.10 or lower (the product is only affected up to version 5.0.10, versions above are not listed as affected)
-
Locate Haxe download configurationSearch for configuration files in the Haxe installation directory or user config folder (typically ~/.haxe or similar) that define download URLs for resources or templatesAffected if Any configuration file contains HTTP (non-HTTPS) URLs for downloading zipped resources, templates, or libraries
-
Inspect build or download scriptsReview any custom build scripts, haxelib configurations, or project files that trigger automatic downloads of Haxe-related resourcesAffected if Scripts or configurations specify HTTP URLs instead of HTTPS for fetching zip files or other downloadable content
-
Check for outdated download mechanismsExamine the Haxe toolchain's default download behavior - look for any hardcoded HTTP endpoints in the Haxe installation or in any downloaded templates/libsAffected if The Haxe installation or its downloaded components use HTTP URLs to fetch zipped resources
You are affected if your Haxe version is 5.0.10 or lower AND any HTTP (non-encrypted) URLs are used for downloading resources, templates, or libraries that could be intercepted and replaced by an attacker.
Generated from the published advisory. Verify against your own configuration.
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 dataReplace HTTP URLs with HTTPS for all resource downloads and implement integrity verification (such as checksums or signatures) to ensure downloaded files have not been tampered with.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-10602 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2016-10602 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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