CVE-2017-1000374
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 · uneditedA flaw exists in NetBSD's implementation of the stack guard page that allows attackers to bypass it resulting in arbitrary code execution using certain setuid binaries. This affects NetBSD 7.1 and possibly earlier versions.
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 · moderate confidenceNetBSD's stack guard page implementation contains a flaw that allows attackers to bypass this security mitigation, enabling arbitrary code execution through certain setuid binaries. This effectively defeats a fundamental memory protection mechanism designed to prevent stack-based buffer overflow exploits from gaining elevated privileges.
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<= 7.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
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/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.
-
Confirm NetBSD is the running operating systemRun 'uname -a' or check '/etc/os-release' to verify the OS is NetBSDAffected if The system is not running NetBSD (this CVE only affects NetBSD)
-
Determine the installed NetBSD versionRun 'uname -r' or check the kernel version to obtain the exact NetBSD release versionAffected if The version is 7.1 or any earlier release (e.g., 7.0, 6.x, 5.x)
-
Identify setuid binaries on the systemRun 'find / -perm -4000 -type f 2>/dev/null' to list all setuid binariesAffected if Any setuid binaries exist and are executable by the user checking (the vulnerability allows privilege escalation through these)
-
Verify stack guard page is in useCheck kernel configuration or examine if stack protection is enabled via 'sysctl kern.stackgap' or similar sysctl values related to stack guard pagesAffected if Stack guard pages are enabled (the vulnerability specifically bypasses this mitigation)
The system is affected if it runs NetBSD version 7.1 or earlier and has setuid binaries with stack guard page protection enabled.
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.
dbcve · scopedApply NetBSD security patches for version 7.1 and earlier; if no patch is available, consider disabling unnecessary setuid binaries or implementing additional runtime protections such as execshield or SEGNOP handling until a patch can be applied.
NetBSD 7.2 or later (preferably NetBSD 8.x stable)
- 1. Backup all critical data and system configuration before proceeding
- 2. Download the latest NetBSD stable release (NetBSD 8.x or the latest 7.x stable branch after 7.1)
- 3. Review NetBSD upgrade documentation for your specific installation method
- 4. Upgrade the NetBSD system to the fixed release
- 5. Reboot the system to load the updated kernel with the stack guard page fix
- 6. Verify the system is running the updated kernel version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-1000374 — 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-2017-1000374 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