CVE-2022-36118
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 · uneditedAn issue was discovered in Blue Prism Enterprise 6.0 through 7.01. In a misconfigured environment that exposes the Blue Prism Application server, it is possible for an authenticated user to reverse engineer the Blue Prism software and circumvent access controls for the SetProcessAttributes administrative function. Abusing this function will allow any Blue Prism user to publish, unpublish, or retire processes. Using this function, any logged-in user can change the status of a process, an action allowed only intended for users with the Edit Process permission.
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 confidenceIn Blue Prism Enterprise 6.0 through 7.01, a misconfigured environment that exposes the Application server allows authenticated users to reverse engineer the software and bypass access controls on the SetProcessAttributes administrative function. This enables any logged-in user to publish, unpublish, or retire processes, which should be restricted to users with Edit Process permission.
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>= 6.4, < 7.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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/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 Blue Prism versionCheck the installed Blue Prism version in the system (typically via Control Panel > Programs or the Blue Prism product itself) and compare it to the affected range of >= 6.4 and < 7.1Affected if The installed version falls within 6.4 through 7.0.x (or 7.01)
-
Verify Application server exposureReview network configuration to determine if the Blue Prism Application server port/service is exposed beyond the intended internal network (check firewall rules, load balancer settings, and IIS/web server bindings for Blue Prism endpoints)Affected if The Application server is accessible from untrusted networks or not properly network-segmented
-
Confirm SetProcessAttributes function accessibilityUsing a standard (non-admin) user account, attempt to access or invoke the SetProcessAttributes administrative function through the Blue Prism API or web interface to test if the access control is enforcedAffected if A standard user account can successfully call SetProcessAttributes without receiving an access denied error
-
Test process publishing capability for standard usersLog in as a regular user without Edit Process permission and attempt to publish, unpublish, or retire a process through the Blue Prism interface or APIAffected if The standard user can successfully publish, unpublish, or retire processes despite lacking Edit Process permission
A user is affected if Blue Prism version is between 6.4 and 7.0.x (inclusive), the Application server is network-exposed, AND a standard user can perform administrative process actions like publishing or retiring processes without proper permissions.
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 · scoped7.1
Restrict exposure of the Blue Prism Application server in misconfigured environments, ensure proper network segmentation, and upgrade to a version beyond 7.01 that addresses this access control bypass.
Blue Prism 7.1 or later
- Upgrade Blue Prism to version 7.1 or later to resolve the access control bypass vulnerability
- After upgrading, verify that the SetProcessAttributes function properly enforces Edit Process permissions
- Confirm that users without Edit Process permission can no longer publish, unpublish, or retire processes
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-36118 — 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-36118 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