Security readout for executives and security teams
Plain-English summary
This flaw affects Linux NFS servers in specific kernel ranges. If a vulnerable server exports a filesystem with rootsquash enabled, remote NFS users may read or write files they should not be allowed to access. Treat exposed NFS shares as potentially serious, especially where they contain sensitive or operational files.
Executive priority
Prioritize if NFS is used for sensitive data, shared application storage, or administrative workflows. Business risk comes from unauthorized remote file read or write through a trusted file-sharing service. Systems without nfsd or rootsquash exports are less likely to be exposed.
Technical view
CVE-2018-1000028 is an incorrect access control issue in Linux kernel nfsd introduced after commit bdcf0a423ea1 and affecting listed 4.15-rc4+, 4.14.8+, 4.9.76+, and 4.4.111+ ranges. The condition described requires an NFS export using rootsquash. The source states it was fixed after upstream commit 1995266727fa8143897e89b55f5d3c79aa828420.
Likely exposure
Exposure is most likely on Linux systems running the kernel NFS server and exporting filesystems with rootsquash enabled. The CVE data does not identify specific distributions, packages, or CPEs, so teams must map kernel builds and vendor backports locally.
Exploitation context
The source bundle does not report active exploitation, and the CVE is not flagged in KEV. The described attack context is remote NFS access to an exported filesystem with rootsquash enabled, potentially allowing unauthorized file reads or writes through NFS access control failure.
Researcher notes
Evidence is limited to the CVE description and upstream kernel fix reference. No CVSS, CWE, distro package list, CPEs, or public exploitation evidence is provided. Pay close attention to vendor backports because distribution kernel version strings may not directly match upstream ranges.
Mitigation direction
- Apply vendor or kernel updates that include the referenced upstream fix.
- Identify NFS exports using rootsquash and prioritize those servers for remediation.
- Restrict NFS access to trusted networks and clients while remediation is pending.
- Review vendor advisories for distribution-specific patched kernel versions.
- Monitor sensitive NFS shares for unexpected file changes or access patterns.
Validation and detection
- Inventory Linux hosts running nfsd and record kernel versions.
- Review NFS export configuration for rootsquash-enabled filesystems.
- Confirm installed kernels include the upstream fix or vendor backport.
- Check vendor security advisories for distro-specific applicability.
- Validate NFS permissions with authorized regression tests after patching.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2018-1000028 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/linus/1995266727fa8143897e89b55f5d3c79aa828420CVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
