dbcve.org
Blue PrismApplication · Ssctech

CVE-2022-36119

HIGH · 8.8 CVSS v3.1 Published 2022-08-25
Fix available
A fix is available. Upgrade to 7.1 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
An 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 a domain authenticated user to send a crafted message to the Blue Prism Server and accomplish a remote code execution attack that is possible because of insecure deserialization. Exploitation of this vulnerability allows for code to be executed in the context of the Blue Prism Server service.

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 confidence

Blue Prism Enterprise versions 6.0 through 7.01 contain an insecure deserialization vulnerability allowing a domain-authenticated user to send crafted messages to the Blue Prism Server, achieving remote code execution in the context of the server service. This occurs in misconfigured environments where the application server is exposed.

MitigationRestrict network exposure of the Blue Prism Application server and upgrade to a patched version. Apply principle of least privilege to domain user accounts and review serialization configuration.

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
Blue PrismApplication
Affected:>= 6.4, < 7.1

CVSS 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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Blue Prism version
    Locate the Blue Prism installation and check the version. Common locations: Registry key HKLM\SOFTWARE\Blue Prism\Installation\Version, or check the About section in Blue Prism Interactive client, or examine the DLL version in the installation directory (typically C:\Program Files\Blue Prism Limited\Blue Prism Automate).
    Affected if Version is 6.4 or higher but lower than 7.1 (or 7.01). Compare your installed version against this range.
  2. Confirm application server is network-exposed
    Check if the Blue Prism Application Server (BPServer.exe) is listening on accessible network interfaces. Review firewall rules allowing inbound connections to the BPServer port (default 8181). Use netstat -an | findstr 8181 or equivalent to verify the server bind address is not localhost-only.
    Affected if The BPServer process is bound to 0.0.0.0 or a routable IP address and accepts external connections, rather than being restricted to localhost or behind a restricted network.
  3. Verify domain authentication is enabled
    Check Blue Prism configuration for authentication settings. In the Blue Prism Deployment Manager or by examining the BPSVC.exe.config file, verify that Windows Authentication or Domain authentication is enabled for user logins.
    Affected if Domain-authenticated users can authenticate to the Blue Prism Server, as this is required for the attack vector described in the CVE.

You are affected if Blue Prism Enterprise version is 6.4 or higher but lower than 7.1, the application server is exposed to the network, and domain authentication is enabled, allowing a domain-authenticated attacker to exploit the insecure deserialization for RCE.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 7.1 or later
Fixed in 7.1
Interim mitigation

Restrict network exposure of the Blue Prism Application server and upgrade to a patched version. Apply principle of least privilege to domain user accounts and review serialization configuration.

Recommended fix High confidence

Blue Prism 7.1 or later

  1. Verify the current Blue Prism version by checking the About section in the Blue Prism product or using the Blue Prism Portal
  2. Schedule a maintenance window for the upgrade process
  3. Ensure all currently running processes and workflows are paused or completed
  4. Create a full backup of the Blue Prism database and configuration files
  5. Download Blue Prism version 7.1 or later from the official Blue Prism portal (portal.blueprism.com)
  6. Stop the Blue Prism Server service on the application server
  7. Install the Blue Prism 7.1 upgrade following the official installation documentation
  8. Start the Blue Prism Server service after installation completes
Caveat Review Blue Prism 7.1 release notes for any feature changes or breaking changes before upgrading, as some workflow behaviors may have changed

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Blue Prism Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-36119 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-36119 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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