Opencall Media PlatformApplication · Hpe

CVE-2019-11999

MEDIUM · 6.9 CVSS v3.1 Published 2020-04-16
Fix available
A fix is available. Upgrade to 4.4.8 / 4.5.2 or later.
See remediation →
73/100
Remediation priority · Elevated
Remotely reachable

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
Potential security vulnerabilities have been identified in HPE OpenCall Media Platform (OCMP) resulting in remote arbitrary file download and cross site scripting. HPE has made the following updates available to resolve the vulnerability in the impacted versions of OCMP. * For OCMP version 4.4.X - please upgrade to OCMP 4.4.8 and then install RP806 * For OCMP 4.5.x please contact HPE Technical Support to obtain the necessary software updates.

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

HPE OpenCall Media Platform (OCMP) versions 4.4.X and 4.5.x contain two distinct vulnerabilities: arbitrary file download allowing remote attackers to retrieve sensitive files from the server, and cross-site scripting (XSS) enabling injection of malicious scripts into web pages served by the application.

MitigationFor OCMP 4.4.X, upgrade to version 4.4.8 and install patch RP806. For OCMP 4.5.x, obtain necessary updates from HPE Technical Support.

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
Opencall Media PlatformApplication
Affected:>= 4.4.0, < 4.4.8>= 4.5.0, < 4.5.2

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
High
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/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 OCMP installation and version
    Locate the HPE OpenCall Media Platform installation directory or check system inventory for OCMP. Look for version information in configuration files, startup scripts, or the web application's About/Help page.
    Affected if Installed version falls within 4.4.0 to 4.4.7 or 4.5.0 to 4.5.1 (versions prior to 4.4.8 and 4.5.2)
  2. Confirm web interface is accessible
    Verify that the OCMP web management interface is reachable over HTTP/HTTPS. This vulnerability affects the web component of the platform.
    Affected if The OCMP web interface is exposed and accessible to network users or attackers
  3. Check for arbitrary file download exposure
    Test whether the web application permits path traversal in download requests. Attempt to access a known file outside the intended web root directory through the application's download functionality.
    Affected if The application allows retrieval of files from arbitrary server paths without proper authorization
  4. Check for XSS vulnerability in web pages
    Inspect web application forms, parameters, or output fields for lack of input sanitization. Submit script tags or HTML elements as input and verify they are reflected unescaped in responses.
    Affected if User-supplied input is rendered in browser responses without encoding, allowing script injection

A user is affected if OCMP version is 4.4.x prior to 4.4.8 or 4.5.x prior to 4.5.2 and the web interface is accessible, since both the arbitrary file download and XSS vulnerabilities are present in these versions.

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.

From vendor data
Upgrade available Upgrade to 4.4.8 / 4.5.2 or later
Fixed in 4.4.84.5.2
Interim mitigation

For OCMP 4.4.X, upgrade to version 4.4.8 and install patch RP806. For OCMP 4.5.x, obtain necessary updates from HPE Technical Support.

Fix this in Opencall Media Platform Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,580
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-11999 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