dbcve.org
Ip150 FirmwareOperating system · Paradox

CVE-2020-25189

CRITICAL · 9.8 CVSS v3.1 Published 2020-11-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
The affected product is vulnerable to three stack-based buffer overflows, which may allow an unauthenticated attacker to remotely execute arbitrary code on the IP150 (firmware versions 5.02.09).

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

The IP150 firmware 5.02.09 contains three stack-based buffer overflow vulnerabilities that allow unauthenticated remote attackers to execute arbitrary code. The critical severity (9.8) reflects the combination of network-exploitable flaws with no authentication required and the potential for complete system compromise.

MitigationIf a vendor firmware update is available, apply it immediately. Otherwise, isolate the IP150 device behind a firewall or VLAN to limit exposure, and monitor for indicators of compromise until a patch is released.

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
Ip150 FirmwareOperating system
Affected:= 5.02.09

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Identify Paradox Ip150 device on network
    Locate the IP150 hardware module on the network via network scans, device discovery, or asset inventory
    Affected if The device is a Paradox IP150 firmware module
  2. Determine installed firmware version
    Access the device admin interface (web, CLI, or SNMP) and retrieve the firmware version number
    Affected if The displayed firmware version is 5.02.09
  3. Confirm version matches affected release
    Compare the retrieved version against the affected version: 5.02.09
    Affected if The installed firmware version is exactly 5.02.09

If the Paradox IP150 firmware version is 5.02.09, the environment is vulnerable to remote code execution via the stack buffer overflow flaws.

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

If a vendor firmware update is available, apply it immediately. Otherwise, isolate the IP150 device behind a firewall or VLAN to limit exposure, and monitor for indicators of compromise until a patch is released.

Fix this in Ip150 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,150
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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