VxSS compromise via hard-coded credential
Published Jul 27, 2022 · Updated Aug 3, 2024
Hard-coded credentials in Veritas NetBackup OpsCenter 10.0 and earlier allow local users to compromise the VxSS subsystem. OpsCenter embeds a reusable credential for the underlying VxSS subsystem rather than requiring individually provisioned authentication. Local access to the OpsCenter host is required, and Veritas has not disclosed the VxSS operations exposed by successful credential use.
Summary
What happened
Hard-coded credentials in Veritas NetBackup OpsCenter 10.0 and earlier allow local users to compromise the VxSS subsystem. OpsCenter embeds a reusable credential for the underlying VxSS subsystem rather than requiring individually provisioned authentication. Local access to the OpsCenter host is required, and Veritas has not disclosed the VxSS operations exposed by successful credential use.
The record
- CVE
- CVE-2022-36952
- Published
- Jul 27, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-798, T1078
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 27, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo