CVE-2022-36116
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 setValidationInfo administrative function. Removing the validation applied to newly designed processes increases the chance of successfully hiding malicious code that could be executed in a production environment.
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 confidenceBlue Prism Enterprise versions 6.0 through 7.01 contains an access control bypass vulnerability. When the Blue Prism Application server is exposed in a misconfigured environment, an authenticated attacker can reverse engineer the software to circumvent access controls on the setValidationInfo administrative function. This allows removal of validation from newly designed processes, enabling malicious code to be hidden and executed in production environments.
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.
-
Verify Blue Prism versionCheck the installed Blue Prism Enterprise version through the application UI (Help > About) or installation logsAffected if Installed version is 6.0 through 7.0 (any version >= 6.4 and < 7.1)
-
Determine Application server exposureReview network configuration and firewall rules to determine if the Blue Prism Application server is directly accessible from untrusted networks or the internetAffected if The Application server is exposed to untrusted/networked environments without proper network segmentation
-
Confirm authentication requirementsVerify whether the environment permits authenticated users to access the setValidationInfo administrative functionAffected if Standard authenticated users can access the setValidationInfo function without elevated administrative privileges
-
Inspect process validation statusReview process objects in the Blue Prism database or control room to identify any processes where validation has been removedAffected if There are processes in the environment with validation removed that were not intentionally devalidated by authorized administrators
Environment is affected if Blue Prism version is 6.0-7.0 AND the Application server is network-accessible to authenticated users who can access the setValidationInfo function.
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
Remediate by implementing proper network segmentation and firewall rules to prevent direct exposure of the Blue Prism Application server. Additionally, enforce role-based access controls on the setValidationInfo function and implement application-level hardening to resist reverse engineering attempts.
Blue Prism 7.1 or later
- Identify all Blue Prism installations in the environment and verify their current version numbers
- Schedule a maintenance window for the upgrade process
- Backup all critical Blue Prism databases and configuration files
- Upgrade Blue Prism servers from versions 6.4-7.0 to version 7.1 or later
- Verify that the upgrade completed successfully by checking the version number in the Blue Prism application
- Test the setValidationInfo function to confirm access controls are properly enforced
- Review and document any process validation settings that may have been affected by the upgrade
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-36116 — 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-36116 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