CVE-2021-42371
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 · uneditedlpar2rrd is a hardcoded system account in XoruX LPAR2RRD and STOR2RRD before 7.30.
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 confidenceA hardcoded system account named 'lpar2rrd' exists in XoruX LPAR2RRD and STOR2RRD versions prior to 7.30. This default credential creates an authentication bypass vector, allowing attackers with knowledge of this account to gain unauthorized system access.
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< 7.30< 7.30CVSS 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.1/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 if LPAR2RRD or STOR2RRD is installedSearch for installation directories or check for running processes: look for /opt/lpar2rrd or /opt/stor2rrd, or run 'ps aux | grep -E "(lpar2rrd|stor2rrd)"'Affected if Either LPAR2RRD or STOR2RRD is found on the system
-
Determine installed versionCheck for a version file in the installation directory, or run version-checking commands provided by the product if available, then compare the version number to 7.30Affected if The installed version is lower than 7.30
-
Check for the hardcoded lpar2rrd system accountVerify if a system user named 'lpar2rrd' exists by checking /etc/passwd, running 'id lpar2rrd', or querying the system's user databaseAffected if A system account named 'lpar2rrd' exists and the product version is below 7.30
-
Review application authentication configurationExamine application configuration files for hardcoded credentials, particularly looking for authentication settings or user definitions that reference the lpar2rrd accountAffected if Hardcoded credentials for the lpar2rrd account are found in configuration files
The environment is affected if LPAR2RRD or STOR2RRD is installed with a version lower than 7.30 and a system account named 'lpar2rrd' exists on the host.
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 · scoped7.30
Upgrade to LPAR2RRD and STOR2RRD version 7.30 or later to remove the hardcoded credential. If immediate upgrade is not feasible, identify and disable the hardcoded account, then implement proper credential management.
7.30
- Backup the current Lpar2rrd and/or Stor2rrd installation and configuration data
- Download version 7.30 or later from the official Lpar2rrd/Stor2rrd download page (lpar2rrd.com or stor2rrd.com)
- Stop any running Lpar2rrd/Stor2rrd services
- Extract and install the new version following the standard upgrade documentation
- Restart the Lpar2rrd/Stor2rrd services
- Verify the hardcoded account has been removed or changed from the default
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-42371 — 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-2021-42371 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