# CVE-2024-20419: Auth bypass in Cisco Smart Software Manager On-Prem

> Unauthenticated remote attackers can change any user's password, including admins, via crafted HTTP requests, leading to full system compromise.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Jul 2024
- **Updated:** 13 Feb 2025
- **Also known as:** GHSA-5697-p67m-73p6

## What is CVE-2024-20419?

CVE-2024-20419 is a critical authentication bypass vulnerability in Cisco Smart Software Manager On-Prem, published on 17 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability in the authentication system of Cisco Smart Software Manager On-Prem (SSM On-Prem) could allow an unauthenticated, remote attacker to change the password of any user, including administrative users.

 This vulnerability is due to improper implementation of the password-change process. An attacker could exploit this vulnerability by sending crafted HTTP requests to an affected device. A successful exploit could allow an attacker to access the web UI or API with the privileges of the compromised user.

Weakness: CWE-620 (Unverified Password Change)

## Which versions are affected by CVE-2024-20419?

It affects 1 product.


Products: Cisco Smart Software Manager On-Prem.

## How do I fix CVE-2024-20419?

No fix has been published for CVE-2024-20419 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-20419 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-20419 exists.

Public exploit code:

- Cisco Smart Software Manager (SSM) On-Prem Account Takeover (CVE-2024-20419) (metasploit)
- Cisco Smart Software Manager On-Prem 8-202206 - Account Takeover (exploitdb)
- Cisco SSM On-Prem <= 8-202206 - Password Reset Account Takeover (nuclei): http/cves/2024/CVE-2024-20419.yaml

## Other vulnerabilities in Cisco Smart Software Manager On-Prem

- [CVE-2026-20160](https://insights.sbomify.com/CVE-2026-20160/): Cisco Smart Software Manager On-Prem Arbitrary Command Execution Vulnerability (critical 9.8)
- [CVE-2020-3158](https://insights.sbomify.com/CVE-2020-3158/): Cisco Smart Software Manager On-Prem Static Default Credential Vulnerability (critical 9.8)
- [CVE-2020-3443](https://insights.sbomify.com/CVE-2020-3443/): Cisco Smart Software Manager On-Prem Privilege Escalation Vulnerability (high 8.8)
- [CVE-2019-16029](https://insights.sbomify.com/CVE-2019-16029/): Cisco Smart Software Manager On-Prem Web Interface Denial of Service Vulnerability (high 8.2)
- [CVE-2021-1219](https://insights.sbomify.com/CVE-2021-1219/): Cisco Smart Software Manager Satellite Static Credential Vulnerability (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-20419 and fix it if it is affected.

What it is: CVE-2024-20419 is a critical authentication bypass vulnerability in Cisco Smart Software Manager On-Prem, published on 17 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-20419 exists.

Affected product: Cisco Smart Software Manager On-Prem. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-20419/ (Markdown: https://insights.sbomify.com/CVE-2024-20419/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-20419
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-20419
- OSV: https://osv.dev/vulnerability/CVE-2024-20419

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-20419/
Summaries are generated and may contain mistakes; the official description above is the record.