Unauthenticated remote code execution via stack buffer overflow
Published Jan 22, 2020 · Updated Aug 5, 2024
Stack-based buffer overflow in Ruckus Unleashed through 200.7.10.102.64 allows remote attackers to execute code via unauthenticated HTTP requests. The zap executable uses an unsafe strcpy operation while parsing its -D argument in zap_parse_args, allowing attacker-controlled data to overwrite the stack. The request reaches the vulnerable parser without authentication and can run arbitrary commands with the access point's privileges.
Summary
What happened
Stack-based buffer overflow in Ruckus Unleashed through 200.7.10.102.64 allows remote attackers to execute code via unauthenticated HTTP requests. The zap executable uses an unsafe strcpy operation while parsing its -D argument in zap_parse_args, allowing attacker-controlled data to overwrite the stack. The request reaches the vulnerable parser without authentication and can run arbitrary commands with the access point's privileges.
The record
- CVE
- CVE-2019-19840
- Published
- Jan 22, 2020
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1210
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 22, 2020CVE publishedPublication date reported by the CVE source.
- Aug 5, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Aleph Research proof of concept for zap stack overflowproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo