CVE-2024-28222
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 · uneditedIn Veritas NetBackup before 8.1.2 and NetBackup Appliance before 3.1.2, the BPCD process inadequately validates the file path, allowing an unauthenticated attacker to upload and execute a custom file.
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 confidenceThe BPCD (Backup Exec Client Service Daemon) in Veritas NetBackup versions prior to 8.1.2 and NetBackup Appliance prior to 3.1.2 contains a path traversal vulnerability due to inadequate validation of file paths in requests, allowing unauthenticated remote attackers to write arbitrary files to the filesystem and achieve remote code execution.
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< 8.1.2< 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
- 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.
-
Verify BPCD service is running and accessibleCheck if the BPCD (Backup Exec Client Service Daemon) process is running and listening on port 13782. Use 'netstat -an | grep 13782' or 'ss -tlnp | grep 13782' to confirm the service is bound to a network interface.Affected if BPCD is listening on a reachable network interface on port 13782, making the vulnerability exploitable from the network.
-
Determine NetBackup versionRun the command 'nbemmcmd -get_version' or check the installation directory for version files. On Windows, inspect the registry under HKLM\SOFTWARE\Veritas\NetBackup\CurrentVersion. On Linux/Unix, check /usr/openv/netbackup/version or similar installation paths.Affected if The installed version is lower than 8.1.2, placing the system within the vulnerable version range.
-
Determine NetBackup Appliance versionIf running NetBackup Appliance, check the appliance version via the management console or by running 'nbacman --version' or accessing the Appliance web interface to view the software version.Affected if The appliance software version is lower than 3.1.2, placing the system within the vulnerable version range.
-
Confirm BPCD accepts unauthenticated connectionsAttempt to send a probe request to the BPCD service on port 13782 using a tool like netcat or openssl s_client. The vulnerability allows unauthenticated access, so the service should respond without requiring authentication credentials.Affected if The BPCD service accepts and processes requests without authentication, which is the condition required for the path traversal exploitation.
If the BPCD service is network-accessible on port 13782 AND the NetBackup version is below 8.1.2 (or NetBackup Appliance version is below 3.1.2), the environment is affected by this vulnerability.
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 · scoped3.1.28.1.2
Upgrade to NetBackup 8.1.2 or later / NetBackup Appliance 3.1.2 or later. If patching is not immediately feasible, restrict network access to the BPCD service port (default 13782) and implement additional monitoring on this interface.
NetBackup 8.1.2 or later; NetBackup Appliance 3.1.2 or later
- Backup the current NetBackup configuration and verify backup integrity
- Schedule the upgrade during a planned maintenance window
- Download NetBackup 8.1.2 (or later) from Veritas Support portal for NetBackup software, or NetBackup Appliance 3.1.2 (or later) for appliance deployments
- Review Veritas upgrade documentation and release notes for 8.1.2/3.1.2 for any specific pre-upgrade requirements
- For NetBackup: Run the upgrade installer following Veritas standard upgrade procedures, or use NBU upgrade catalog commands if applicable
- For NetBackup Appliance: Use the Appliance web console or CLI to apply the 3.1.2 (or later) update following Veritas appliance upgrade procedures
- After upgrade, verify the BPCD process version and confirm it is 8.1.2 or higher
- Validate that NetBackup services start correctly and the BPCD service is running
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation4.0 h
- Testing8.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,784.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-28222 — 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-2024-28222 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