CVE-2017-5495
What it is
All versions of Quagga, 0.93 through 1.1.0, are vulnerable to an unbounded memory allocation in the telnet 'vty' CLI, leading to a Denial-of-Service of Quagga daemons, or even the entire host. When Quagga daemons are configured with their telnet CLI enabled, anyone who can connect to the TCP ports can trigger this vulnerability, prior to authentication. Most distributions restrict the Quagga telnet interface to local access only by default. The Quagga telnet interface 'vty' input buffer grows automatically, without bound, so long as a newline is not entered. This allows an attacker to cause the Quagga daemon to allocate unbounded memory by sending very long strings without a newline. Eventually the daemon is terminated by the system, or the system itself runs out of memory. This is fixed in Quagga 1.1.1 and Free Range Routing (FRR) Protocol Suite 2017-01-10.
At a glance
- Exploitability
- Can be exploited over the network without logging in. High risk of service disruption.
- Exploit odds
- 18.8% chance of exploitation in the next 30 days (EPSS). Higher than most.
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 18.8% in the next 30 days (EPSS).
- Severity: 7.5 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 18.8% · EPSS, next 30 days
- Weakness
- CWE-119 · Buffer errors
- Record status
- Modified
Affected
- Quagga ≤ 1.1.0
Attack profile CVSS 3.0 · 7.5
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Raw vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2017-5495.md and follow it. Check whether this project is affected by CVE-2017-5495. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- http://savannah.nongnu.org/forum/forum.php?forum_id=8783
- https://github.com/freerangerouting/frr/pull/63
- http://savannah.nongnu.org/forum/forum.php?forum_id=8783
- https://github.com/freerangerouting/frr/pull/63
References
- http://rhn.redhat.com/errata/RHSA-2017-0794.html
- http://savannah.nongnu.org/forum/forum.php?forum_id=8783
- http://www.securityfocus.com/bid/95745
- http://www.securitytracker.com/id/1037688
- https://github.com/freerangerouting/frr/pull/63
- https://lists.quagga.net/pipermail/quagga-dev/2017-January/016586.html
- http://rhn.redhat.com/errata/RHSA-2017-0794.html
- http://savannah.nongnu.org/forum/forum.php?forum_id=8783
- http://www.securityfocus.com/bid/95745
- http://www.securitytracker.com/id/1037688
- https://github.com/freerangerouting/frr/pull/63
- https://lists.quagga.net/pipermail/quagga-dev/2017-January/016586.html