CVE-2023-21520
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 · uneditedA PII Enumeration via Credential Recovery in the Self Service (Credential Recovery) of BlackBerry AtHoc version 7.15 could allow an attacker to potentially associate a list of contact details with an AtHoc IWS organization.
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 confidenceA PII enumeration vulnerability exists in the Self Service Credential Recovery feature of BlackBerry AtHoc version 7.15. The flaw allows an unauthenticated attacker to potentially associate contact details with an AtHoc IWS organization by leveraging the password recovery mechanism, exposing user PII.
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= 7.15CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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.
-
Identify BlackBerry AtHoc installationCheck your systems for the presence of BlackBerry AtHoc software. This is typically deployed as a web application on IIS or similar web servers. Look for AtHoc-related processes, services, or installed applications.Affected if BlackBerry AtHoc version 7.15 is installed and running
-
Confirm installed versionLocate the AtHoc version information. This is usually accessible through the AtHoc administration console under System settings, or through installed program metadata on the server.Affected if The installed version is exactly 7.15
-
Verify Self Service Credential Recovery is enabledAccess the AtHoc administration panel and navigate to the Self Service Credential Recovery feature settings. Check whether this feature is turned on for user password recovery operations.Affected if The Self Service Credential Recovery feature is enabled in the AtHoc configuration
-
Inspect password recovery response behaviorTest the credential recovery flow by submitting valid and invalid user identifiers (such as email addresses or employee IDs) to the recovery endpoint. Observe the content and format of error or confirmation messages returned.Affected if Recovery responses expose PII such as partial contact details, phone numbers, email addresses, or organizational affiliation information that could be used for enumeration
-
Check for rate limiting on recovery endpointReview the web server configuration (IIS or equivalent) and AtHoc application settings for rate limiting, account lockout policies, or CAPTCHA requirements on the credential recovery endpoints.Affected if No rate limiting, lockout policies, or additional identity verification is configured on the password recovery mechanism
Your environment is affected if you are running BlackBerry AtHoc version 7.15 with the Self Service Credential Recovery feature enabled, and the password recovery responses expose user PII or lack rate limiting protections.
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 dataImplement rate limiting, account lockout policies, and additional identity verification in the credential recovery flow to prevent automated PII enumeration; consider masking or omitting sensitive details from recovery error responses.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.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 $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-21520 — 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-21520 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