CVE-2018-18652
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 · uneditedA remote command execution vulnerability in Veritas NetBackup Appliance before 3.1.2 allows authenticated administrators to execute arbitrary commands as root. This issue was caused by insufficient filtering of user provided input.
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 confidenceVeritas NetBackup Appliance versions before 3.1.2 contain a remote command execution vulnerability where authenticated administrators can execute arbitrary commands as root due to insufficient filtering of user-provided input, allowing attackers with admin credentials to inject and execute OS commands.
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< 3.1.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
- Network
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:H/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.
-
Confirm Veritas NetBackup Appliance is installedIdentify the installed product by checking system information, hostname, or running 'getosname' or 'uname -a' if on the appliance console. Look for 'NetBackup Appliance' in the product name.Affected if The system is not a Veritas NetBackup Appliance (the vulnerability only affects this specific product).
-
Determine the installed versionLog into the appliance console or admin interface and run 'nbappcli version' or check the About/Version section in the NetBackup Appliance web UI. Alternatively, check /opt/VERITAS/nbuphp/version file if accessible.Affected if The installed version is lower than 3.1.2 (e.g., 3.0.x, 3.1.0, 3.1.1).
-
Verify admin web interface accessibilityCheck if TCP port 443 or 8443 is open and responding on the appliance's management IP address by running 'nmap -p 443,8443 <appliance_ip>' or 'netstat -an | grep -E '443|8443'' on the appliance.Affected if The admin web interface is exposed to untrusted networks (an attacker with admin credentials could reach it).
-
Review admin user accountsList local admin accounts in the appliance via 'nbac cli user list' or check the Users section in the appliance console to identify who has administrative privileges.Affected if Admin accounts exist and are accessible (the vulnerability requires valid admin credentials to exploit).
The environment is affected if the system is a Veritas NetBackup Appliance running a version lower than 3.1.2 with an accessible admin interface that could accept malicious command injection.
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 data3.1.2
Upgrade Veritas NetBackup Appliance to version 3.1.2 or later. If immediate patching is not possible, restrict administrative access to trusted personnel and monitor for suspicious command execution activity.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-18652 — 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-18652 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