dbcve.org
Mediant 500l Msbr FirmwareOperating system · Audiocodes

CVE-2019-9231

HIGH · 8.8 CVSS v3.0 Published 2019-07-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
An issue was discovered on AudioCodes Mediant 500L-MSBR, 500-MBSR, M800B-MSBR and 800C-MSBR devices with firmware versions before 7.20A.202.307. A Cross-Site Request Forgery (CSRF) vulnerability in the management web interface allows remote attackers to execute malicious and unauthorized actions, because CSRFProtection=1 is not a default and is not documented.

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

A CSRF vulnerability exists in the management web interface of AudioCodes Mediant 500L-MSBR, 500-MBSR, M800B-MSBR, and 800C-MSBR devices with firmware versions prior to 7.20A.202.307. Attackers can trick authenticated administrators into executing unauthorized actions by leveraging the absence of CSRF token validation in the web interface. The CSRFProtection=1 setting is not enabled by default and is undocumented, making exploitation straightforward.

MitigationUpgrade the firmware to version 7.20A.202.307 or later which includes proper CSRF protection. Alternatively, if upgrading is not immediately feasible, implement additional network-based controls to limit exposure of the management interface to trusted networks only.

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
Mediant 500l Msbr FirmwareOperating system
Affected:>= f7.20a, < f7.20a.202.307
Mediant 500 Mbsr FirmwareOperating system
Affected:>= f7.20a, < f7.20a.202.307
Mediant M800b Msbr FirmwareOperating system
Affected:>= f7.20a, < f7.20a.202.307
Mediant 800c Msbr FirmwareOperating system
Affected:>= f7.20a, < f7.20a.202.307

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/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. Identify device model
    Access the device web interface or CLI and retrieve the hardware model information. Look for Mediant 500L-MSBR, 500-MBSR, M800B-MSBR, or 800C-MSBR in the device status or system information page.
    Affected if The device is NOT one of these four models.
  2. Check firmware version
    Navigate to the device management web interface, typically at the IP address of the device. Go to the Status or Maintenance section to view the firmware version. Alternatively, use the CLI command 'show system information' or similar to retrieve the firmware build number.
    Affected if The firmware version is NOT >= f7.20a AND < f7.20A.202.307.
  3. Inspect CSRF protection setting
    Access the device configuration files or web interface settings. Look for a parameter named CSRFProtection or similar security token settings in the web server or application configuration. Check if it is set to 1 or enabled.
    Affected if The CSRFProtection setting is NOT set to 1 or is missing from the configuration.
  4. Verify web management interface accessibility
    Confirm that the device web management interface is accessible over HTTP/HTTPS from the network. Check the listening services and exposed ports on the device.
    Affected if The management web interface is exposed to untrusted networks.

You are affected if you have a Mediant 500L-MSBR, 500-MBSR, M800B-MSBR, or 800C-MSBR device running firmware version f7.20a through f7.20A.202.306 and the CSRFProtection setting is not enabled in your configuration.

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

Upgrade the firmware to version 7.20A.202.307 or later which includes proper CSRF protection. Alternatively, if upgrading is not immediately feasible, implement additional network-based controls to limit exposure of the management interface to trusted networks only.

Fix this in Mediant 500l Msbr Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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