dbcve.org
Control ManagerApplication · Avaya

CVE-2019-7003

CRITICAL · 10.0 CVSS v3.1 Published 2019-07-11
Fix available
A fix is available. Upgrade to 8.0.4.0 or later.
See remediation →
100/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
A SQL injection vulnerability in the reporting component of Avaya Control Manager could allow an unauthenticated attacker to execute arbitrary SQL commands and retrieve sensitive data related to other users on the system. Affected versions of Avaya Control Manager include 7.x and 8.0.x versions prior to 8.0.4.0. Unsupported versions not listed here were not evaluated.

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 · high confidence

SQL injection vulnerability in the reporting component of Avaya Control Manager allows unauthenticated attackers to execute arbitrary SQL commands and retrieve sensitive data related to other users on the system. This affects versions 7.x and 8.0.x prior to 8.0.4.0.

MitigationUpgrade to Avaya Control Manager 8.0.4.0 or later to resolve the SQL injection vulnerability in the reporting component.

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
Control ManagerApplication
Affected:>= 7.0, < 8.0.4.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
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/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. Confirm Avaya Control Manager is installed
    Check for Avaya Control Manager installation directories (commonly under /opt/avaya or C:\Avaya\ControlManager) or look for the 'acm' or 'avaya-control-manager' service running on the system
    Affected if Avaya Control Manager software is found on the system
  2. Identify installed version
    Locate version file or use command-line tool provided with the installation, typically found in the installation directory or accessible via 'avayactl' or similar management utility
    Affected if Version is 7.x or 8.0.x and is lower than 8.0.4.0
  3. Verify reporting component is enabled
    Check if the reporting component/web interface is accessible and enabled - look for reporting service process or web endpoint (commonly on port 8080 or 8443)
    Affected if Reporting component is exposed and running on the system
  4. Check network exposure of reporting interface
    Determine if the reporting component is accessible from network by testing common reporting URLs or ports against the server IP/hostname
    Affected if Reporting interface is reachable from network without authentication

If Avaya Control Manager version is 7.0 through 8.0.3.x and the reporting component is accessible, the system is vulnerable to unauthenticated SQL injection.

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 8.0.4.0 or later
Fixed in 8.0.4.0
Interim mitigation

Upgrade to Avaya Control Manager 8.0.4.0 or later to resolve the SQL injection vulnerability in the reporting component.

Recommended fix High confidence

Control Manager 8.0.4.0 or later

  1. 1. Identify the current version of Avaya Control Manager by accessing the admin interface or using the version check command
  2. 2. Navigate to the official Avaya support portal (support.avaya.com or downloads.avaya.com) and locate the Control Manager 8.0.4.0 or later version
  3. 3. Download the upgrade package following Avaya's authentication and download procedures
  4. 4. Review the upgrade documentation and release notes for Control Manager 8.0.4.0
  5. 5. Create a complete backup of the current Control Manager configuration and database
  6. 6. Follow the documented upgrade procedure to install version 8.0.4.0 or later
  7. 7. After upgrade, verify the reporting component is functioning correctly and the SQL injection vulnerability is resolved
  8. 8. Confirm the installed version matches the fixed release (8.0.4.0 or higher)
Caveat Review release notes for any configuration changes or migration requirements between 7.x/8.0.x and 8.0.4.0

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

Fix this in Control Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
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,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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