dbcve.org
Decision ManagerApplication · Redhat

CVE-2019-14841

HIGH · 8.8 CVSS v3.1 Published 2022-10-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
A flaw was found in the RHDM, where an authenticated attacker can change their assigned role in the response header. This flaw allows an attacker to gain admin privileges in the Business Central Console.

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

In Red Hat Decision Manager (RHDM), an authenticated attacker can modify their assigned role directly in the response header, allowing them to escalate privileges to administrator level in the Business Central Console. This represents a client-side privilege escalation vulnerability where the application trusts role information submitted by the user without proper server-side validation.

MitigationImplement server-side validation of role assignments using session-based authorization rather than trusting client-supplied role data in headers. Ensure role changes can only be made through authorized administrative channels.

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
Decision ManagerApplication
Affected:= 7.0
Process AutomationApplication
Affected:= 7.0

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. Confirm Red Hat Decision Manager or Process Automation is installed
    Identify the installation directory and product metadata. Look for jboss or wildfly application server directories with RHDM or RHPAM components.
    Affected if The product is Red Hat Decision Manager 7.0 or Red Hat Process Automation 7.0
  2. Verify the exact product version
    Check the installed version number against the affected range. Consult the product's about or version information page in the administration console.
    Affected if The installed version is exactly 7.0 for either product
  3. Determine if Business Central Console is deployed and accessible
    Access the Business Central Console web interface. Identify whether the application is reachable and user authentication is enabled.
    Affected if Business Central Console is deployed and accessible to authenticated users
  4. Inspect application configuration for role header handling
    Review the application server configuration files and any middleware proxies to determine if role information submitted in HTTP headers is processed without server-side validation.
    Affected if The application accepts and processes role assignments from client-supplied headers without validating them server-side
  5. Check for proxy or filter configurations that inspect or modify role headers
    Examine web.xml, jboss-web.xml, and any servlet filters or valve configurations that handle role or authorization headers.
    Affected if There is no server-side validation configured for role header values and the application trusts client-supplied role data

A user is affected if they are running Red Hat Decision Manager 7.0 or Red Hat Process Automation 7.0 with Business Central Console where role assignments from HTTP headers are processed without server-side validation.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement server-side validation of role assignments using session-based authorization rather than trusting client-supplied role data in headers. Ensure role changes can only be made through authorized administrative channels.

Recommended fix Moderate confidence

Red Hat Decision Manager 7.x or Process Automation 7.x with errata update containing CVE-2019-14841 fix

  1. 1. Identify the current Red Hat Decision Manager or Process Automation installation version
  2. 2. Upgrade to a version that includes the security fix for CVE-2019-14841
  3. 3. After upgrade, verify that Business Central Console access controls function correctly
  4. 4. Review user role assignments in the system to ensure proper permissions are maintained
Caveat Standard upgrade considerations apply - test in non-production environment first, backup configuration, review release notes for any breaking changes between versions

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

Fix this in Decision Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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