CVE-2023-23958
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 · uneditedSymantec Protection Engine, prior to 9.1.0, may be susceptible to a Hash Leak vulnerability.
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 confidenceSymantec Protection Engine prior to version 9.1.0 contains a Hash Leak vulnerability, which could allow an attacker to obtain hash values through the affected product, potentially aiding in further cryptographic or authentication attacks.
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< 9.1.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
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 version of Symantec Protection EngineLocate the product installation directory and check for version information in about, license, or version files typically found in the program directory, or use the product's administrative console or command-line utility if availableAffected if The installed version is any version prior to 9.1.0
-
Compare the version against the affected rangeDocument the exact version number found and compare it to the vulnerability threshold of 9.1.0Affected if The version number is less than 9.1.0 (for example, 9.0.x, 8.x, or earlier)
-
Identify if the product is exposed to network or unauthenticated accessReview network listening ports, firewall rules, and access control configurations for the Symantec Protection Engine serviceAffected if The product's hash computation or cryptographic functions are accessible to unauthorized or network-based attackers
The environment is affected if Symantec Protection Engine is installed with any version prior to 9.1.0, regardless of exposure level, as the hash leak vulnerability exists in the product itself.
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 · scoped9.1.0
Upgrade Symantec Protection Engine to version 9.1.0 or later to remediate this vulnerability.
Symantec Protection Engine 9.1.0 or later
- 1. Back up the current Symantec Protection Engine configuration and any custom settings
- 2. Download the Symantec Protection Engine 9.1.0 (or later) installation package from the Broadcom support portal at support.broadcom.com
- 3. Stop the Symantec Protection Engine service before upgrading
- 4. Install or apply the version 9.1.0 upgrade following the vendor's documented upgrade procedure
- 5. Restart the Symantec Protection Engine service after the upgrade completes
- 6. Verify the installation by checking the version number and ensuring the service is running normally
- 7. Confirm the vulnerability is remediated by reviewing the system logs for any errors
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.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 $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-23958 — 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-23958 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