dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-0394

HIGH · 7.8 CVSS v3.1 Published 2024-04-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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
Rapid7 Minerva Armor versions below 4.5.5 suffer from a privilege escalation vulnerability whereby an authenticated attacker can elevate privileges and execute arbitrary code with SYSTEM privilege.  The vulnerability is caused by the product's implementation of OpenSSL's`OPENSSLDIR` parameter where it is set to a path accessible to low-privileged users.  The vulnerability has been remediated and fixed in version 4.5.5. 

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

Rapid7 Minerva Armor versions below 4.5.5 contain a privilege escalation vulnerability where an authenticated attacker can execute arbitrary code with SYSTEM privileges. The root cause is OpenSSL's OPENSSLDIR being configured to a path accessible to low-privileged users, allowing modification of SSL-related files.

MitigationUpgrade to Minerva Armor version 4.5.5 or later, which remediates the vulnerability by configuring OPENSSLDIR to a secure location not accessible to low-privileged users.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/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. Confirm Minerva Armor installation and version
    Locate the Minerva Armor installation directory and identify the installed version number (typically found in product metadata, version file, or executable properties). Compare the version against the affected range (below 4.5.5).
    Affected if The installed version is below 4.5.5.
  2. Locate OpenSSL configuration file
    Find the openssl.cnf or openssl.cfg configuration file used by the OpenSSL installation bundled with or used by Minerva Armor. Common locations include the installation directory, system config directories, or paths specified by environment variables.
    Affected if An OpenSSL configuration file exists and is being used by the Minerva Armor environment.
  3. Identify OPENSSLDIR setting
    Open the OpenSSL configuration file and search for the 'OPENSSLDIR' directive. Note the path value specified (for example: OPENSSLDIR = "C:\Program Files\Minerva Armor\ssl" or similar).
    Affected if OPENSSLDIR is set to a specific path within the Minerva Armor installation directory.
  4. Verify directory permissions on OPENSSLDIR
    Check file system permissions on the OPENSSLDIR path. Use operating system tools to list ACLs or effective permissions, specifically examining whether low-privileged users or the 'Users' group have write, modify, or create permissions to that directory or its contents.
    Affected if Low-privileged users (non-admin, non-SYSTEM) can write to or modify files within the OPENSSLDIR path.

A user is affected if Minerva Armor version is below 4.5.5 AND the OPENSSLDIR points to a directory writable by low-privileged users, enabling modification of SSL-related files for privilege escalation.

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 Minerva Armor version 4.5.5 or later, which remediates the vulnerability by configuring OPENSSLDIR to a secure location not accessible to low-privileged users.

Recommended fix High confidence

Rapid7 Minerva Armor version 4.5.5

  1. Identify the current installed version of Rapid7 Minerva Armor
  2. Upgrade to Minerva Armor version 4.5.5 or later
  3. Verify the upgrade was successful and the version is correct
  4. Test that the privilege escalation vulnerability is no longer present

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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