RhnsdApplication · Redhat
CVE-2017-7560
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 · uneditedIt was found that rhnsd PID files are created as world-writable that allows local attackers to fill the disks or to kill selected processes.
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 · high confidenceThe rhnsd (Red Hat Network Service Daemon) creates PID files in a world-writable location (likely /var/run/), setting overly permissive file permissions (likely 666). This allows any local user to either fill disk space by writing large amounts of data to the PID file path, or manipulate PID files to point to arbitrary processes and kill them, causing denial of service or disrupting system services.
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
RhnsdApplication
all versionsCVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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.
-
Check if rhnsd is installedRun 'rpm -q rhnsd' or 'which rhnsd' to see if the Red Hat Network Service Daemon is present on the systemAffected if rhnsd is installed - the vulnerability applies to all versions of this package
-
Identify the rhnsd PID file locationRun 'ps aux | grep rhnsd' to find the running process, then check /var/run/ for rhnsd.pid or similar PID filesAffected if A PID file exists in /var/run/ or similar world-writable directory
-
Check PID file permissionsRun 'ls -la /var/run/rhnsd.pid' (or the actual PID file path found) to view file permissionsAffected if Permissions show 666 (rw-rw-rw-) or similar world-writable settings (such as 777)
-
Verify directory is world-writableRun 'ls -la /var/run/' and confirm the directory has world-write permissions (typically 755 or looser)Affected if The /var/run/ directory allows any local user to write files
-
Confirm PID file ownership and permissions match vulnerable stateCompare the actual permission output against the affected state: any user can read AND write to the PID fileAffected if Non-root users can write to the PID file path (permissions 666 or directory allows modification)
If rhnsd is installed and its PID file exists with world-writable permissions (666) in /var/run/, the system is vulnerable to local user DoS and disk space exhaustion.
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.
From vendor dataRestrict PID file creation permissions to prevent world-writable access, typically by setting umask or explicit chmod/chown operations during PID file creation to owner-only (0600) or group-readable (0640) permissions.
Fix this in Rhnsd
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-7560 — 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-7560 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