dbcve.org
Process Automation ManagerApplication · Redhat

CVE-2022-2458

HIGH · 8.2 CVSS v3.1 Published 2022-08-10
Fix available
A fix is available. Upgrade to 7.13.1 or later.
See remediation →
91/100
Remediation priority · Urgent
Remotely reachable No privileges 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
XML external entity injection(XXE) is a vulnerability that allows an attacker to interfere with an application's processing of XML data. This attack occurs when XML input containing a reference to an external entity is processed by a weakly configured XML parser. The software processes an XML document that can contain XML entities with URIs that resolve to documents outside of the intended sphere of control, causing the product to embed incorrect documents into its output. Here, XML external entity injection lead to External Service interaction & Internal file read in Business Central and also Kie-Server APIs.

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

XXE vulnerability in Business Central and Kie-Server APIs allows attackers to inject malicious XML with external entity references. A weakly configured XML parser processes these entities, enabling reading of internal files and interaction with internal/external services.

MitigationConfigure XML parsers to disable external entity processing and DTD parsing. Use secure XML parser settings that prevent entity expansion and external resource loading.

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
Process Automation ManagerApplication
Affected:< 7.13.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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/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 checks

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

  1. Identify Redhat Process Automation Manager version
    Check the installed version of Redhat Process Automation Manager using the package manager, installation directory, or version lookup command provided by Red Hat. Compare it to the affected range: versions < 7.13.1
    Affected if The installed version is below 7.13.1
  2. Confirm Business Central component is in use
    Determine if the Business Central web interface or API endpoint is accessible and in use within your environment
    Affected if Business Central is deployed and accessible
  3. Confirm Kie-Server component is in use
    Determine if the Kie-Server REST API or associated endpoints are exposed and in use within your environment
    Affected if Kie-Server API is deployed and accessible
  4. Inspect XML parser configuration
    Review the XML parser configuration files or settings used by Business Central and Kie-Server. Look for settings related to external entity processing, DTD parsing, and external resource loading. Check if these security controls are explicitly disabled or not configured.
    Affected if XML parsers allow external entity processing or DTD parsing (the secure setting to disable these is not applied)
  5. Verify XML input handling
    Review how XML inputs are processed when received by Business Central or Kie-Server APIs. Determine whether there are input validation or sanitization mechanisms in place for XML content
    Affected if There is no input validation preventing malicious XML with external entity references from being processed

You are affected if your Redhat Process Automation Manager version is below 7.13.1 AND Business Central or Kie-Server APIs are in use with XML parsers that have not been configured to disable external entity and DTD processing.

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.13.1 or later
Fixed in 7.13.1
Interim mitigation

Configure XML parsers to disable external entity processing and DTD parsing. Use secure XML parser settings that prevent entity expansion and external resource loading.

Recommended fix Moderate confidence

Process Automation Manager 7.13.1

  1. Upgrade Process Automation Manager to version 7.13.1 or later to resolve the XXE vulnerability
  2. After upgrade, verify that Business Central and Kie-Server APIs are functioning normally
  3. Validate that XML parsing configurations disable external entity processing as an additional defense-in-depth measure

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

Fix this in Process Automation Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-2458 — 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-2458 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