# CVE-2019-1912: Cisco Small Business 220 Series Smart Switches Authentication Bypass Vulnerability

> Unauthenticated remote attackers can upload arbitrary files to Cisco Small Business 220 Series Smart Switches, enabling configuration modification or reverse shell injection.

- **Severity:** Critical 9.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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:** 7 Aug 2019
- **Updated:** 19 Nov 2024
- **Also known as:** GHSA-q6mv-m62h-7q28

## What is CVE-2019-1912?

CVE-2019-1912 is a critical missing authorization vulnerability in Cisco Small Business 220 Series Smart Plus Switches, published on 7 Aug 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability in the web management interface of Cisco Small Business 220 Series Smart Switches could allow an unauthenticated, remote attacker to upload arbitrary files. The vulnerability is due to incomplete authorization checks in the web management interface. An attacker could exploit this vulnerability by sending a malicious request to certain parts of the web management interface. Depending on the configuration of the affected switch, the malicious request must be sent via HTTP or HTTPS. A successful exploit could allow the attacker to modify the configuration of an affected device or to inject a reverse shell. This vulnerability affects Cisco Small Business 220 Series Smart Switches running firmware versions prior to 1.1.4.4 with the web management interface enabled. The web management interface is enabled via both HTTP and HTTPS by default.

Weakness: CWE-863 (Incorrect Authorization), CWE-285 (Improper Authorization)

## Which versions are affected by CVE-2019-1912?

It affects 11 products.


Products: Cisco Sf-220-24 Firmware, Cisco Sf220-24p Firmware, Cisco Sf220-48 Firmware, Cisco Sf220-48p Firmware, Cisco Sg220-26 Firmware, Cisco Sg220-26p Firmware, Cisco Sg220-28 Firmware, Cisco Sg220-28mp Firmware, Cisco Sg220-50 Firmware, Cisco Sg220-50p Firmware, Cisco Sg220-52 Firmware.

## How do I fix CVE-2019-1912?

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

## Is CVE-2019-1912 being exploited?

There is no known exploitation of CVE-2019-1912 in the wild and no public exploit code.

Public exploit code:

- Cisco Small Business 220 Series - Multiple Vulnerabilities (exploitdb)

## Other vulnerabilities in Cisco Small Business 220 Series Smart Plus Switches

- [CVE-2019-1913](https://insights.sbomify.com/CVE-2019-1913/): Cisco Small Business 220 Series Smart Switches Remote Code Execution Vulnerabilities (critical 9.8)
- [CVE-2019-1914](https://insights.sbomify.com/CVE-2019-1914/): Cisco Small Business 220 Series Smart Switches Command Injection Vulnerability (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-1912 and fix it if it is affected.

What it is: CVE-2019-1912 is a critical missing authorization vulnerability in Cisco Small Business 220 Series Smart Plus Switches, published on 7 Aug 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-1912 in the wild and no public exploit code.

Affected product: Cisco Small Business 220 Series Smart Plus Switches. 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-2019-1912/ (Markdown: https://insights.sbomify.com/CVE-2019-1912/index.md)
```

## Sources

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

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