Filtered by vendor Boa
Subscriptions
Total
11 CVE
CVE | Vendors | Products | Updated | CVSS v3.1 |
---|---|---|---|---|
CVE-2022-45956 | 1 Boa | 1 Boa | 2024-11-21 | 5.3 Medium |
Boa Web Server versions 0.94.13 through 0.94.14 fail to validate the correct security constraint on the HEAD HTTP method allowing everyone to bypass the Basic Authorization mechanism. | ||||
CVE-2022-44117 | 1 Boa | 1 Boa | 2024-11-21 | 9.8 Critical |
Boa 0.94.14rc21 is vulnerable to SQL Injection via username. NOTE: the is disputed by multiple third parties because Boa does not ship with any support for SQL. | ||||
CVE-2021-33558 | 1 Boa | 1 Boa | 2024-11-21 | 7.5 High |
Boa 0.94.13 allows remote attackers to obtain sensitive information via a misconfiguration involving backup.html, preview.html, js/log.js, log.html, email.html, online-users.html, and config.js. NOTE: multiple third parties report that this is a site-specific issue because those files are not part of Boa. | ||||
CVE-2018-21028 | 1 Boa | 1 Boa | 2024-11-21 | 7.5 High |
Boa through 0.94.14rc21 allows remote attackers to trigger a memory leak because of missing calls to the free function. | ||||
CVE-2018-21027 | 1 Boa | 1 Boa | 2024-11-21 | 9.8 Critical |
Boa through 0.94.14rc21 allows remote attackers to trigger an out-of-memory (OOM) condition because malloc is mishandled. | ||||
CVE-2017-9833 | 1 Boa | 1 Boa | 2024-11-21 | 7.5 High |
/cgi-bin/wapopen in Boa 0.94.14rc21 allows the injection of "../.." using the FILECAMERA variable (sent by GET) to read files with root privileges. NOTE: multiple third parties report that this is a system-integrator issue (e.g., a vulnerability on one type of camera) because Boa does not include any wapopen program or any code to read a FILECAMERA variable. | ||||
CVE-2016-9564 | 1 Boa | 1 Boa | 2024-11-21 | N/A |
Buffer overflow in send_redirect() in Boa Webserver 0.92r allows remote attackers to DoS via an HTTP GET request requesting a long URI with only '/' and '.' characters. | ||||
CVE-2009-4496 | 1 Boa | 1 Boa | 2024-11-21 | N/A |
Boa 0.94.14rc21 writes data to a log file without sanitizing non-printable characters, which might allow remote attackers to modify a window's title, or possibly execute arbitrary commands or overwrite files, via an HTTP request containing an escape sequence for a terminal emulator. | ||||
CVE-2007-4915 | 1 Boa | 1 Boa Webserver | 2024-11-21 | N/A |
The Intersil isl3893 extensions for Boa 0.93.15, as used on the FreeLan RO80211G-AP and other devices, do not prevent stack writes from entering memory locations used for string constants, which allows remote attackers to change the admin password stored in memory via a long username in an HTTP Basic Authentication request. | ||||
CVE-2000-0920 | 1 Boa | 1 Boa Webserver | 2024-11-20 | N/A |
Directory traversal vulnerability in BOA web server 0.94.8.2 and earlier allows remote attackers to read arbitrary files via a modified .. (dot dot) attack in the GET HTTP request that uses a "%2E" instead of a "." | ||||
CVE-2024-43367 | 1 Boa | 1 Boa | 2024-08-20 | 7.5 High |
Boa is an embeddable and experimental Javascript engine written in Rust. Starting in version 0.16 and prior to version 0.19.0, a wrong assumption made when handling ECMAScript's `AsyncGenerator` operations can cause an uncaught exception on certain scripts. Boa's implementation of `AsyncGenerator` makes the assumption that the state of an `AsyncGenerator` object cannot change while resolving a promise created by methods of `AsyncGenerator` such as `%AsyncGeneratorPrototype%.next`, `%AsyncGeneratorPrototype%.return`, or `%AsyncGeneratorPrototype%.throw`. However, a carefully constructed code could trigger a state transition from a getter method for the promise's `then` property, which causes the engine to fail an assertion of this assumption, causing an uncaught exception. This could be used to create a Denial Of Service attack in applications that run arbitrary ECMAScript code provided by an external user. Version 0.19.0 is patched to correctly handle this case. Users unable to upgrade to the patched version would want to use `std::panic::catch_unwind` to ensure any exceptions caused by the engine don't impact the availability of the main application. |
Page 1 of 1.