dbcve.org
Linux KernelOperating system · Linux

CVE-2017-1000377

MEDIUM · 5.9 CVSS v3.0 Published 2017-06-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
64/100
Remediation priority · Elevated
No privileges Zero-click

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 · unedited
An issue was discovered in the size of the default stack guard page on PAX Linux (originally from GRSecurity but shipped by other Linux vendors), specifically the default stack guard page is not sufficiently large and can be "jumped" over (the stack guard page is bypassed), this affects PAX Linux Kernel versions as of June 19, 2017 (specific version information is not available at this time).

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 confidence

In PAX Linux (a security-hardened Linux kernel distribution), the default stack guard page is too small to provide effective protection against stack buffer overflow exploitation. The stack guard page is a security mechanism that separates the stack from other memory regions; when it can be 'jumped' over, attackers can potentially bypass this mitigation and reach the stack memory where they could execute code or cause denial of service.

MitigationIncrease the default stack guard page size to a value that cannot be trivially jumped over by overflowing buffers. This requires modifying the kernel configuration and recompiling PAX Linux with an appropriate stack guard page size.

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
Linux KernelOperating system
Affected:all versions

CVSS 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
Local
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm the kernel is PAX Linux
    Run 'uname -a' or check /proc/version to examine the kernel string. Look for 'PAX' or 'pax' in the kernel name.
    Affected if The kernel is not a PAX Linux kernel (this CVE only affects PAX Linux)
  2. Check for PaX flags support
    Look for /proc/sys/kernel/pax or run 'sysctl -a | grep -i pax' to see if PaX security features are available on the system.
    Affected if No PaX-specific sysctls or flags are present, indicating this is not a PaX-hardened system
  3. Examine stack guard page configuration
    Check /proc/sys/kernel/pax/soft (if it exists) or look for stack guard-related entries in /proc (some PAX builds expose stack guard settings via /proc filesystem). Also check dmesg for any PAX banner messages showing stack guard size.
    Affected if The system shows stack guard page size is configured to a small value (typically less than 65536 bytes or a few pages)
  4. Verify stack guard is not being bypassed
    Check if executable stacks are allowed: look for 'exec-shield' or 'exec-stack' in /proc/sys/kernel/ or run 'sysctl -a | grep exec'. Also check if PaX flags on binaries allow executable stacks via 'paxctl -v <binary>' if available.
    Affected if Executable stacks are enabled or PaX stack protection is disabled, weakening the stack guard protection

A system is affected if it is running PAX Linux with the default (small) stack guard page size that can be trivially jumped over by overflowing a buffer, which can be confirmed by checking the PaX kernel version and stack guard configuration settings.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Increase the default stack guard page size to a value that cannot be trivially jumped over by overflowing buffers. This requires modifying the kernel configuration and recompiling PAX Linux with an appropriate stack guard page size.

Fix this in Linux Kernel Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-1000377 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-1000377 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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