CVE-2022-22319
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 · uneditedIBM Robotic Process Automation 21.0.1 could allow a register user on the system to physically delete a queue that could cause disruption for any scripts dependent on the queue. IBM X-Force ID: 218366.
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 confidenceIBM Robotic Process Automation 21.0.1 lacks proper authorization controls on queue deletion, allowing any authenticated user to delete queues. This causes denial of service for automated scripts and workflows that depend on those queues, as they lose access to critical processing queues.
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= 21.0.1= 21.0.1.2all versionsCVSS 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
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
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 installed IBM RPA versionCheck the product version in the IBM Robotic Process Automation installation directory or via the admin console. On Windows, look in the installation folder for version.info or check Help > About in the RPA platform. For the SaaS offering, check the tenant administration panel for version information.Affected if The installed version is 21.0.1 or 21.0.1.2, or the product is IBM RPA As A Service (any version)
-
Confirm queue functionality is in useAccess the RPA platform web interface or client and navigate to the queue management section. Verify that queue objects exist in the environment and are actively used by bots or workflows.Affected if Queues are present and actively used by automation workflows in the environment
-
Test queue deletion authorizationLog in to the RPA platform with a non-administrator user account that has standard or limited permissions. Navigate to an existing queue and attempt to delete it using the queue management interface or API.Affected if A non-administrator user is able to successfully delete a queue without receiving an authorization or permission denied error
-
Verify RBAC configuration for queuesAccess the administration or security settings panel in the RPA platform. Examine the role-based access control configuration for queue operations, specifically looking for permissions assigned to roles regarding queue deletion.Affected if No RBAC controls exist or the delete queue permission is granted to non-administrator roles
You are affected if your environment runs IBM RPA version 21.0.1, 21.0.1.2, or is the As A Service offering, and non-administrator users can delete queues without proper authorization checks.
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 role-based access control (RBAC) to restrict queue deletion permissions to administrators only, and validate user permissions before any destructive queue operations.
- 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-2022-22319 — 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-2022-22319 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