CVE-2023-28074
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 · uneditedDell BSAFE Crypto-C Micro Edition, version 4.1.5, and Dell BSAFE Micro Edition Suite, versions 4.0 through 4.6.1 and version 5.0, contains an Out-of-bounds Read vulnerability. An unauthenticated attacker with local access could potentially exploit this vulnerability, leading to Information exposure.
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 confidenceDell BSAFE crypto libraries contain an out-of-bounds read vulnerability that allows an unauthenticated attacker with local system access to read memory outside allocated buffers. This can expose sensitive cryptographic material such as keys, certificates, or other secrets stored in memory.
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>= 4.0.0, <= 4.1.5>= 4.0.0, < 4.6.2= 5.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
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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.
-
Locate Dell BSAFE library files on the systemSearch for files matching Dell BSAFE library names (such as libbsafe, BSAFE, or dell*crypto* libraries) in common system library directories (/usr/lib, /usr/lib64, /opt, or application-specific paths). Also check application dependency lists or manifests that may reference these libraries.Affected if Dell BSAFE crypto libraries are present on the system
-
Identify the installed BSAFE library versionUse commands or tools appropriate to the system to query the library version, such as running 'strings' on the library file, checking version info via 'ldd' or 'nm', or reviewing version metadata in application documentation if BSAFE is bundled.Affected if The version cannot be determined or matches the affected ranges (4.0.0 through 4.1.5 for Crypto C ME, or 4.0.0 through 4.6.1 / 5.0 for Micro Edition Suite)
-
Verify if the BSAFE library is actively loaded or referencedCheck running processes or application configurations to determine if any application is actively using the BSAFE library. Examine process memory maps or application logs that may indicate BSAFE initialization.Affected if An application is actively loading or using the affected BSAFE library version
A system is affected if it has any Dell BSAFE library version within 4.0.0 to 4.1.5 (Crypto C ME) or 4.0.0 to 4.6.1/5.0 (Micro Edition Suite) that is actively in use, and the attacker has local system access to trigger the out-of-bounds read.
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.
From vendor data4.6.2
Apply vendor-supplied patches or update to a patched version of the affected BSAFE libraries. Since local access is required, prioritize systems in physically secure or restricted-access environments.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-28074 — 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-28074 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