CVE-2016-10576
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 · uneditedFuseki server wrapper and management API in fuseki before 1.0.1 downloads binary 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 confidenceThe Fuseki server wrapper and management API versions prior to 1.0.1 download binary resources over unencrypted HTTP connections instead of HTTPS, allowing a network-attacker to perform man-in-the-middle attacks. An attacker positioned on the network can intercept and replace the requested binary resources with malicious counterparts, potentially achieving remote code execution on the targeted system.
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< 1.0.1CVSS 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.
-
Identify Fuseki installation and versionLocate the Fuseki installation directory and check the version file or executable version (often found in fuseki-server.jar or via --version flag). Compare against the affected range: any version before 1.0.1 is vulnerable.Affected if The installed Fuseki version is below 1.0.1.
-
Verify the server wrapper component is in useDetermine whether the Fuseki server wrapper (fuseki-server) or management API component is deployed and running. Check for the presence of fuseki-server.jar or equivalent wrapper scripts in the installation.Affected if The Fuseki server wrapper or management API is actively running and the version is below 1.0.1.
-
Inspect network configuration for download behaviorReview Fuseki configuration files (such as purei.n3 or.ttl configuration files in the /etc or configuration directory) for any download URLs. Monitor network traffic or proxy logs to observe whether HTTP (port 80) connections are used for fetching binary resources.Affected if Fuseki is configured to download binary resources over unencrypted HTTP rather than HTTPS.
A user is affected if they are running any version of Fuseki Project Fuseki below 1.0.1 that uses the server wrapper or management API with unencrypted HTTP downloads.
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 data1.0.1
Upgrade Fuseki to version 1.0.1 or later which uses HTTPS for resource downloads. If immediate upgrading is not feasible, ensure downloads occur only over trusted networks and implement binary integrity verification mechanisms.
- Consultation1.0 h
- Implementation1.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 $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-10576 — 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-10576 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