CVE-2023-47579
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 · uneditedRelyum RELY-PCIe 22.2.1 devices suffer from a system group misconfiguration, allowing read access to the central password hash file of the operating system.
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 confidenceRelyum RELY-PCIe 22.2.1 devices contain a system group misconfiguration that permits read access to the operating system's central password hash file (typically /etc/shadow on Linux-based systems), potentially exposing credential hashes for offline cracking or privilege escalation.
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= 22.2.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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 device model is Relyum RELY-PCIeIdentify the hardware model via system information, dmesg, or device documentation. Look for 'RELY-PCIe' or 'Relyum' in boot logs, /proc/cpuinfo, or hardware inventory outputs.Affected if The device is not a Relyum RELY-PCIe variant.
-
Check firmware version equals 22.2.1Retrieve the installed firmware version from the device. Common methods include: checking /etc/version, /etc/release, or running 'dmidecode' if available. Compare your found version against the affected range.Affected if The firmware version is not 22.2.1.
-
Inspect /etc/shadow file permissionsExecute 'ls -l /etc/shadow' or 'stat /etc/shadow' to view the file's owner, group, and permission bits. Verify if the file is readable by non-root users.Affected if The file shows read permissions for group or other (e.g., permissions like -r-----r-- or looser, or group ownership that includes unprivileged users).
-
Check system group membership of accessing userRun 'id <username>' or 'groups' to see which groups the current user belongs to. Compare against the group ownership of /etc/shadow.Affected if The user belongs to the group that has read access to /etc/shadow.
The environment is affected if the device is a Relyum RELY-PCIe running firmware 22.2.1 and /etc/shadow is readable by non-privileged users or groups due to the misconfiguration.
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 dataRemediate the system group misconfiguration to enforce proper access controls on the password hash file, restricting read access to only privileged system accounts.
- Consultation3.0 h
- Implementation2.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 $2,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-47579 — 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-2023-47579 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