CVE-2023-28818
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 IT Analytics 11 before 11.2.0. The application upgrade process included unsigned files that could be exploited and result in a customer installing unauthentic components. A malicious actor could install rogue Collector executable files (aptare.jar or upgrademanager.zip) on the Portal server, which might then be downloaded and installed on collectors.
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 IT Analytics versions before 11.2.0 have an insecure upgrade mechanism that does not verify file signatures. An attacker with write access to the Portal server can plant malicious aptare.jar or upgrademanager.zip files, which are then automatically downloaded and executed by collectors during upgrade or maintenance operations.
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.6.00= 11.0.00= 11.1.00CVSS 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
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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.
-
Determine the installed NetBackup IT Analytics versionAccess the Portal web interface and navigate to the Help or About section to view the product version. Alternatively, check version files in the Portal server installation directory if accessible.Affected if The displayed version is 11.0.00 or 11.1.00, indicating a vulnerable NetBackup IT Analytics installation.
-
Determine the installed Aptare IT Analytics versionAccess the Aptare Portal interface and locate the version information in the administration or about page. Check for any version documentation or release notes within the installation.Affected if The displayed version is before 10.6.00, indicating a vulnerable Aptare IT Analytics installation.
-
Confirm the Portal server component is presentVerify the NetBackup IT Analytics Portal component is installed and running. This is typically accessible via web browser on the configured Portal port (default 443 or 8443).Affected if The Portal server is running and accessible, which is required for the upgrade mechanism to be exploited.
-
Identify if upgrade or maintenance operations are configuredCheck the Portal administration settings for scheduled upgrade tasks, automatic update checks, or collector maintenance configurations. Look for any upgrade-related jobs or policies.Affected if Automatic upgrade or maintenance operations are enabled, which would trigger the vulnerable file download and execution process.
You are affected if your installed version is NetBackup IT Analytics 11.0.00 or 11.1.00, or Aptare IT Analytics before 10.6.00, and the Portal server component is present and accessible in your environment.
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.6.00
Upgrade to NetBackup IT Analytics 11.2.0 or later. Additionally, restrict physical and logical access to the Portal server to prevent unauthorized file injection.
NetBackup IT Analytics 11.2.0 or later (also applies to Aptare It Analytics customers upgrading to a corresponding fixed release)
- 1. Back up the current NetBackup IT Analytics or Aptare It Analytics Portal server and all Collector configurations
- 2. Download Veritas NetBackup IT Analytics version 11.2.0 or later from the Veritas download site (www.veritas.com)
- 3. Review Veritas upgrade documentation for your specific version path before initiating the upgrade
- 4. Execute the upgrade process following the official Veritas upgrade procedures, ensuring the signed installer packages are used
- 5. After upgrade completion, verify the upgrade was successful by checking the Portal server version and confirming all Collectors are operational
- 6. Validate the integrity of downloaded upgrade components using the provided checksums/signature verification
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation8.0 h
- Testing12.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 $8,256.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-28818 — 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-28818 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