CVE-2021-22934
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 vulnerability in Pulse Connect Secure before 9.1R12 could allow an authenticated administrator or compromised Pulse Connect Secure device in a load-balanced configuration to perform a buffer overflow via a malicious crafted web request.
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 confidenceA buffer overflow vulnerability in Pulse Connect Secure versions prior to 9.1R12 allows an authenticated administrator or a compromised device in a load-balanced configuration to send a maliciously crafted web request that triggers the overflow.
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< 9.1CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/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.
-
Identify the installed productLocate the product name in the system administration interface or system information page. The product will be listed as either Pulse Connect Secure or Ivanti Connect Secure.Affected if The product is Pulse Connect Secure or Ivanti Connect Secure.
-
Retrieve the installed versionAccess the admin web console or use the system status/diagnostics command to obtain the exact software version number.Affected if Version is below 9.1R12 for Pulse Connect Secure, or exactly 9.1 for Ivanti Connect Secure.
-
Confirm administrator access is enabledCheck if the administrative web interface (typically on port 443 or 8443) is accessible and enabled on the device.Affected if The admin interface is reachable, as an authenticated administrator is required to trigger the overflow.
-
Check for load-balanced configurationReview network configuration or device cluster settings to determine if the system is deployed in a load-balanced setup.Affected if The device is part of a load-balanced environment, as a compromised node in such a configuration can trigger the flaw.
A system is affected if it runs Pulse Connect Secure versions prior to 9.1R12 or Ivanti Connect Secure version 9.1, has an accessible admin interface, and either has an authenticated admin session or operates in a load-balanced configuration.
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
Upgrade Pulse Connect Secure to version 9.1R12 or later. In load-balanced environments, ensure all nodes are updated simultaneously and monitor for signs of device compromise.
Pulse Connect Secure 9.1R12 or later
- Download Pulse Connect Secure version 9.1R12 or later from the official Pulse Secure support site (kb.pulsesecure.net)
- Review the upgrade instructions in the Pulse Connect Secure administration guide
- Back up the current device configuration
- Perform the upgrade following the documented procedure
- Verify the upgrade was successful and the device is functioning properly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing8.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 $4,288.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-22934 — 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-2021-22934 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