Business CentralApplication · Redhat
CVE-2019-14839
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 · uneditedIt was observed that while login into Business-central console, HTTP request discloses sensitive information like username and password when intercepted using some tool like burp suite etc.
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 confidenceThe Business-central console login process transmits username and password in plain text within HTTP requests, allowing an attacker with network interception capabilities (e.g., Burp Suite) to capture credentials in clear text.
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
Business CentralApplication
<= 7.48.0
Descision ManagerApplication
= 7.0
Process AutomationApplication
= 7.0CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 Business Central product and versionCheck the installed version of Redhat Business Central, Decision Manager, or Process Automation. Typically found in the application's about section or via the runtime banner. Compare against the affected ranges: <= 7.48.0 for Business Central, 7.0 for Decision Manager and Process Automation.Affected if The installed version falls within the affected ranges (Business Central <= 7.48.0, Decision Manager 7.0, or Process Automation 7.0)
-
Verify login page accessibility over HTTPAttempt to access the Business Central console login page using HTTP (non-SSL) on the typical ports 8080 or 8000. For example, navigate to http://hostname:8080/business-central or http://hostname:8000/business-central.Affected if The login page loads successfully over HTTP (unencrypted connection)
-
Inspect login form submission methodView the HTML source of the login page or use browser developer tools to examine the login form's 'action' attribute. Determine whether the form submits to an http:// (HTTP) or https:// (HTTPS) endpoint.Affected if The login form's action attribute points to an HTTP URL (http://), indicating credentials will be transmitted in plain text
A user is affected if they are running an affected version AND the Business Central login page is accessible or configured to submit credentials over unencrypted HTTP rather than HTTPS.
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 · scopedEnforce HTTPS/TLS for all Business-central console connections and ensure the login form submits credentials over an encrypted channel rather than plain HTTP.
Red Hat Process Automation Manager 7.1 or later (specific fixed version available via RHSA)
- Contact Red Hat support or reference the official RHSA (Red Hat Security Advisory) for CVE-2019-14839 to obtain the specific patch or updated package for your product version.
- Apply the security update through your Red Hat Satellite or yum update mechanism for the affected package (rhpam-business-central, rhpam-decision-manager, or rhpam-process-automation-manager).
- After applying the update, restart the affected services to ensure the security fix takes effect.
- Verify the fix by logging into the Business Central console and confirming that credentials are no longer exposed in HTTP requests when intercepted by a proxy tool.
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Business Central
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-14839 — 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-2019-14839 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