dbcve.org
Sg200 50 FirmwareOperating system · Cisco

CVE-2019-1943

MEDIUM · 6.1 CVSS v3.0 Published 2019-07-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
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
A vulnerability in the web interface of Cisco Small Business 200, 300, and 500 Series Switches software could allow an unauthenticated, remote attacker to redirect a user to a malicious web page. The vulnerability is due to improper input validation of the parameters of an HTTP request. An attacker could exploit this vulnerability by intercepting a user's HTTP request and modifying it into a request that causes the web interface to redirect the user to a specific malicious URL. This type of vulnerability is known as an open redirect attack and is used in phishing attacks that get users to unknowingly visit malicious sites.

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

An open redirect vulnerability in the web interface of Cisco Small Business 200, 300, and 500 Series Switches allows unauthenticated remote attackers to modify HTTP request parameters, causing the interface to redirect users to attacker-controlled malicious URLs. This occurs due to improper input validation of the parameters in HTTP requests.

MitigationApply Cisco-provided software updates/patches for affected switch series. As an interim measure, restrict access to the web interface using ACLs or disable it entirely if not required, and educate users about phishing risks from suspicious redirects.

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
Sg200 50 FirmwareOperating system
Affected:all versions
Sg200 50p FirmwareOperating system
Affected:all versions
Sg200 50fp FirmwareOperating system
Affected:all versions
Sg200 26 FirmwareOperating system
Affected:all versions
Sg200 26p FirmwareOperating system
Affected:all versions
Sg200 26fp FirmwareOperating system
Affected:all versions
Sg200 18 FirmwareOperating system
Affected:all versions
Sg200 10fp FirmwareOperating system
Affected:all versions

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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

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 the switch model
    Log into the switch CLI and run 'show version' or physically inspect the device label to confirm the model number (e.g., SG200-50, SG200-26, SG200-18, SG200-10FP)
    Affected if The model matches one of the affected models: SG200-50, SG200-50p, SG200-50fp, SG200-26, SG200-26p, SG200-26fp, SG200-18, or SG200-10fp
  2. Verify the web interface is enabled
    In the switch CLI, run 'show running-config | include http' or 'show ip http' to check if the HTTP/HTTPS server is configured and active
    Affected if The output shows 'ip http server' or 'ip http secure-server' is enabled, meaning the web interface is active
  3. Confirm network accessibility of the web interface
    From a workstation on the same network, attempt to reach the switch web interface using a browser at http://<switch-ip> or https://<switch-ip> and verify the login page loads
    Affected if The web interface is reachable over the network on HTTP port 80 or HTTPS port 443, indicating the attack surface is exposed
  4. Check for external access exposure
    Review any ACLs, NAT rules, or firewall policies that may allow external users to reach the switch web interface IP address
    Affected if The switch web interface IP is accessible from outside the local management network or from untrusted VLANs

If the device is one of the listed affected models and the web interface is enabled and network-accessible (especially from untrusted networks), the environment is vulnerable to this open redirect flaw.

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

Apply Cisco-provided software updates/patches for affected switch series. As an interim measure, restrict access to the web interface using ACLs or disable it entirely if not required, and educate users about phishing risks from suspicious redirects.

Fix this in Sg200 50 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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