CVE-2018-15771
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 · uneditedDell EMC RecoverPoint versions prior to 5.1.2.1 and RecoverPoint for VMs versions prior to 5.2.0.2 contain an information disclosure vulnerability. A malicious boxmgmt user may potentially be able to determine the existence of any system file via Boxmgmt CLI.
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 confidenceDell EMC RecoverPoint and RecoverPoint for VMs contain an information disclosure vulnerability where a malicious boxmgmt user can determine the existence of any system file via the Boxmgmt CLI, exposing file presence information that should not be accessible to standard users.
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< 5.1.2.1< 5.2.0.2CVSS 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
- None
- Availability
- None
CVSS:3.0/AV:L/AC:L/PR:L/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.
-
Identify the installed RecoverPoint versionAccess the RecoverPoint management interface or use the CLI command 'boxmgmt -c get_version' to retrieve the installed software versionAffected if The version is below 5.1.2.1 for RecoverPoint or below 5.2.0.2 for RecoverPoint for VMs
-
Identify the installed RecoverPoint for VMs versionAccess the vCenter or use the RecoverPoint for VMs management console to check the installed versionAffected if The version is below 5.2.0.2 for RecoverPoint for VMs
-
Verify boxmgmt CLI access existsConfirm that the boxmgmt CLI tool is present and accessible on the system. This is the interface through which the vulnerable file existence check can be performedAffected if The boxmgmt CLI is available and can be invoked by users with boxmgmt privileges
-
Check for unauthorized boxmgmt user accessReview system user accounts and permissions to determine if any untrusted users have been granted boxmgmt-level access to the CLIAffected if Any user with boxmgmt privileges exists who should not have access to system file information via CLI commands
A system is affected if it is running RecoverPoint version below 5.1.2.1 or RecoverPoint for VMs version below 5.2.0.2 and has boxmgmt CLI access available to users who should not see arbitrary file existence information.
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 data5.1.2.15.2.0.2
Upgrade to RecoverPoint version 5.1.2.1 or later, or RecoverPoint for VMs version 5.2.0.2 or later, to remediate this vulnerability.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-15771 — 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-2018-15771 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