VDB

CVE-2017-1000

CVE-2017-1000 REJECTED

Reported by intel

DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was in a CNA pool that was not assigned to any issues during 2017. Notes: none.

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
linux-awsUbuntu:16.04:LTS4.4.0-1030.39
linux-raspi2Ubuntu:16.04:LTS4.4.0-1069.77
linuxUbuntu:14.04:LTS3.13.0-128.177
linux-hweUbuntu:16.04:LTS4.10.0-32.36~16.04.1

Timeline

  • Apr 30, 2017 PoC Published (4 in total, the first dated here)
  • Jul 2, 2018 CVE Published
  • Apr 12, 2026 Distribution Patch (5 in total, the first dated here)
  • Apr 12, 2026 Security Advisory (20 in total, the first dated here)
  • Oct 5, 2026 Coalition ESS Score

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2017-1000
vulnetix vdb fixes CVE-2017-1000

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2017-1000/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›