dbcve.org
Lpar2rrdApplication · Xorux

CVE-2020-24032

CRITICAL · 9.8 CVSS v3.1 Published 2020-08-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable 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
tz.pl on XoruX LPAR2RRD and STOR2RRD 2.70 virtual appliances allows cmd=set&tz=OS command injection via shell metacharacters in a timezone.

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 confidence

A command injection vulnerability exists in tz.pl on XoruX LPAR2RRD and STOR2RRD 2.70 virtual appliances. The timezone parameter (tz=) in the cmd=set command accepts shell metacharacters, allowing an attacker to inject and execute arbitrary OS commands on the affected system.

MitigationUpgrade to a patched version of LPAR2RRD/STOR2RRD that addresses this vulnerability. If no patch is available, restrict network access to the management interface and implement input validation on the tz.pl endpoint to sanitize shell metacharacters from the timezone parameter.

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
Lpar2rrdApplication
Affected:= 2.7.0
Stor2rrdApplication
Affected:= 2.7.0

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
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 checks

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

  1. Identify if LPAR2RRD or STOR2RRD is installed
    Look for the LPAR2RRD or STOR2RRD installation directory on the system, commonly found under /opt/lpar2rrd, /opt/stor2rrd, or similar paths. Check for the presence of product-specific directories and scripts.
    Affected if Either LPAR2RRD or STOR2RRD is found on the system
  2. Check the installed product version
    Locate the version file or check the product's web interface for the version number. Compare your installed version against the affected range (version 2.7.0).
    Affected if The installed version is exactly 2.7.0
  3. Locate the tz.pl script
    Find the tz.pl file within the product installation directory - it is typically located in the cgi-bin or scripts folder of the web interface.
    Affected if The tz.pl script exists in the product's web directory
  4. Verify the vulnerable parameter handling exists
    Inspect the tz.pl script to confirm it processes the tz parameter within a cmd=set command and passes it to system calls without proper sanitization. Look for shell execution patterns involving the timezone parameter.
    Affected if The tz.pl script accepts and processes the tz parameter in cmd=set without input sanitization

If the installed version is 2.7.0 and the tz.pl script with the cmd=set endpoint and tz parameter is accessible, the system is vulnerable to command injection.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a patched version of LPAR2RRD/STOR2RRD that addresses this vulnerability. If no patch is available, restrict network access to the management interface and implement input validation on the tz.pl endpoint to sanitize shell metacharacters from the timezone parameter.

Recommended fix Moderate confidence

Latest available version on stor2rrd.com (vendor should be contacted to confirm the specific fixed release that addresses CVE-2020-24032)

  1. 1. Identify the current installed version of LPAR2RRD or STOR2RRD by checking the application interface or running: lpar2rrd -v or stor2rrd -v
  2. 2. Download the latest version from the official vendor website at www.stor2rrd.com
  3. 3. Backup the existing installation directory and configuration files before upgrading
  4. 4. Follow the vendor's standard upgrade procedure for your installation type (virtual appliance or manual installation)
  5. 5. After upgrade, verify the tz.pl script no longer accepts shell metacharacters in the timezone parameter
  6. 6. Test that the timezone setting functionality works correctly with valid timezone values
Caveat Review vendor release notes for any configuration or feature changes between version 2.70 and the target upgrade version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Lpar2rrd Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-24032 — 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-2020-24032 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