CVE-2017-1000372
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 OpenBSD's implementation of the stack guard page that allows attackers to bypass it resulting in arbitrary code execution using setuid binaries such as /usr/bin/at. This affects OpenBSD 6.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 confidenceOpenBSD's stack guard page implementation contains a flaw that allows attackers to bypass this security mechanism, enabling arbitrary code execution. The vulnerability specifically targets setuid binaries such as /usr/bin/at, which run with elevated privileges. Successful exploitation could allow an attacker to execute code with the privileges of the targeted setuid binary.
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<= 6.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.
-
Identify the operating systemRun 'uname -a' or check /etc/os-release to confirm the system is OpenBSDAffected if The system is not running OpenBSD (this CVE only affects OpenBSD)
-
Check the installed OpenBSD versionRun 'uname -r' or 'sysctl kern.version' to get the exact version numberAffected if The version is 6.1 or lower (e.g., 6.1, 6.0, 5.9, etc.)
-
Verify presence of vulnerable setuid binariesCheck if /usr/bin/at exists and has the setuid bit set using 'ls -la /usr/bin/at'Affected if The binary exists and has setuid permissions (permissions contain 's' instead of 'x' for owner)
-
Check for other setuid binaries that could be targetsRun 'find /usr -perm -4000 2>/dev/null' to list all setuid binaries on the systemAffected if Multiple setuid binaries exist, particularly in /usr/bin or /usr/sbin
You are affected if you are running OpenBSD version 6.1 or earlier and have setuid binaries (especially /usr/bin/at) present on the system.
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 OpenBSD security patches for this vulnerability or upgrade to a version newer than OpenBSD 6.1. Until patches are applied, consider restricting access to vulnerable setuid binaries or implementing additional runtime protections.
OpenBSD 6.2
- Backup all critical data and configuration files from the current system
- Verify the integrity of the OpenBSD 6.2 installation media by checking SHA256 checksums from official OpenBSD sources
- Create a bootable installation media (USB or CD) with OpenBSD 6.2
- Schedule a maintenance window as the upgrade will require system downtime
- Boot from the OpenBSD 6.2 installation media
- Select the 'Upgrade' option when prompted (not 'Install')
- Follow the upgrade prompts, preserving existing configurations when asked
- After upgrade completes, verify /usr/bin/at and other setuid binaries have correct permissions
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.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 $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-1000372 — 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-1000372 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