Sf302 08pp FirmwareOperating system · Cisco
CVE-2019-1814
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 · uneditedA vulnerability in the interactions between the DHCP and TFTP features for Cisco Small Business 300 Series (Sx300) Managed Switches could allow an unauthenticated, remote attacker to cause the device to become low on system memory, which in turn could lead to an unexpected reload of the device and result in a denial of service (DoS) condition on an affected device. The vulnerability is due to a failure to free system memory when an unexpected DHCP request is received. An attacker could exploit this vulnerability by sending a crafted DHCP packet to the targeted device. A successful exploit could allow the attacker to cause an unexpected reload of the device.
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 · moderate confidenceA memory leak vulnerability exists in the DHCP and TFTP feature interaction of Cisco Small Business 300 Series Managed Switches. When an unexpected DHCP request is received, system memory is not properly freed. An attacker sending a crafted DHCP packet can exhaust device memory, causing the switch to reload unexpectedly and result in a denial of service.
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
Sf302 08pp FirmwareOperating system
< 1.4.10.6
Sf302 08mpp FirmwareOperating system
< 1.4.10.6
Sg300 10pp FirmwareOperating system
< 1.4.10.6
Sg300 10mpp FirmwareOperating system
< 1.4.10.6
Sf300 24pp FirmwareOperating system
< 1.4.10.6
Sf300 48pp FirmwareOperating system
< 1.4.10.6
Sg300 28pp FirmwareOperating system
< 1.4.10.6
Sf300 08 FirmwareOperating system
< 1.4.10.6CVSS 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
- Changed
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the switch modelAccess the switch web interface or CLI and locate the model number displayed in the device information or system summaryAffected if The model is not one of: Sf302-08pp, Sf302-08mpp, Sg300-10pp, Sg300-10mpp, Sf300-24pp, Sf300-48pp, Sg300-28pp, or Sf300-08
-
Check the firmware versionIn the web interface go to Administration > Firmware Upgrade, or via CLI run 'show version' and locate the firmware version stringAffected if The installed firmware version is 1.4.10.6 or higher (any version below 1.4.10.6 is affected)
-
Verify DHCP is enabledIn the web interface navigate to IP Configuration > DHCP and check if the DHCP client or server feature is enabled; via CLI use 'show ip interface' or check DHCP-related configurationAffected if DHCP is actively enabled on the switch (the memory leak occurs when processing DHCP requests)
-
Confirm TFTP feature statusCheck if TFTP firmware upload/download functionality is configured or enabled on the device via the web interface under Administration > Firmware Upgrade or via CLI commandsAffected if TFTP feature is configured or was recently used (the vulnerability stems from DHCP and TFTP feature interaction)
A user is affected if the switch model matches one of the eight listed models, the firmware version is below 1.4.10.6, and DHCP is enabled (with TFTP interaction likely present).
Generated from the published advisory. Verify against your own configuration.
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 data1.4.10.6
Apply the Cisco firmware patch for this vulnerability when released; meanwhile, restrict unauthorized DHCP access to the affected devices through network segmentation or ACLs to reduce attack surface.
Fix this in Sf302 08pp Firmware
Scoped from the published advisory
- Consultation4.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,152.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-1814 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-1814 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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