CVE-2023-28759
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 · uneditedAn issue was discovered in Veritas NetBackup before 10.0 on Windows. A vulnerability in the way the client validates the path to a DLL prior to loading may allow a lower-level user to elevate privileges and compromise the system.
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 · moderate confidenceVeritas NetBackup client for Windows fails to properly validate DLL paths before loading, allowing an authenticated low-privilege user to plant a malicious DLL and execute arbitrary code with elevated privileges. This is a DLL hijacking/planting privilege escalation vulnerability affecting versions prior to 10.0.
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< 10.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Veritas NetBackup client is installedOpen Control Panel > Programs and Features, or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion' in PowerShell to list installed programsAffected if Veritas NetBackup or NetBackup client appears in the installed programs list
-
Determine the installed NetBackup versionCheck the version in Programs and Features, or inspect the NetBackup client binary version by locating the installation directory (typically C:\Program Files\Veritas\NetBackup) and right-clicking the main executable to view Properties > DetailsAffected if The version number is below 10.0 (for example, 9.x, 8.x, etc.)
-
Verify NetBackup services are runningOpen Services (services.msc) and look for services starting with 'NetBackup' or 'Veritas', or run 'Get-Service | Where-Object {$_.DisplayName -like "*NetBackup*"}' in PowerShellAffected if Any NetBackup services are in a Running state, as the DLL loading occurs during service execution
-
Check for low-privilege user access to NetBackup directoriesRight-click the NetBackup installation folder (typically C:\Program Files\Veritas\NetBackup), select Properties > Security, and verify if standard users or authenticated users have Write or Modify permissionsAffected if Low-privilege users have Write or Modify access to any NetBackup program directories where DLLs could be planted
You are affected if NetBackup client version is below 10.0, the service is running, and low-privilege users have write access to NetBackup directories where they could plant a malicious DLL.
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 · scoped10.0
Upgrade Veritas NetBackup client to version 10.0 or later on all Windows systems. Apply the update following Veritas release notes and ensure proper testing in a staging environment before production deployment.
NetBackup 10.0 or later
- Verify current NetBackup version by checking the installed version in Programs and Features or using 'bpcd -version'
- Download NetBackup 10.0 or later from Veritas Support Portal (www.veritas.com)
- Review Veritas NetBackup 10.0 release notes for upgrade prerequisites and compatibility requirements
- Create a full backup of the NetBackup configuration and database before upgrading
- Stop all NetBackup services on the Windows client/server
- Run the NetBackup 10.0 installer with administrative privileges
- Follow the installation wizard to complete the upgrade
- Restart NetBackup services after installation completes
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-28759 — 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-2023-28759 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