Last Seen: 2025-04-24
Tags:
self-signed

GeneralInformation

80 / tcp
1300038943 | 2025-04-09T21:42:39.148643
161 / udp
735985454 | 2025-04-22T05:34:02.388113
443 / tcp
0 | 2025-04-20T06:55:40.545725
515 / tcp
-1810918953 | 2025-04-23T02:54:20.194464
5353 / udp
-483012041 | 2025-04-24T17:48:40.427453
49152 / tcp
-1777091293 | 2025-04-11T03:18:08.480367

Vulnerabilities

Note: the device may not be impacted by all of these issues. The vulnerabilities are implied based on the software and version.

2019(1)
CVE-2019-11072
9.8lighttpd before 1.4.54 has a signed integer overflow, which might allow remote attackers to cause a denial of service (application crash) or possibly have unspecified other impact via a malicious HTTP GET request, as demonstrated by mishandling of /%2F? in burl_normalize_2F_to_slash_fix in burl.c. NOTE: The developer states "The feature which can be abused to cause the crash is a new feature in lighttpd 1.4.50, and is not enabled by default. It must be explicitly configured in the config file (e.g. lighttpd.conf). Certain input will trigger an abort() in lighttpd when that feature is enabled. lighttpd detects the underflow or realloc() will fail (in both 32-bit and 64-bit executables), also detected in lighttpd. Either triggers an explicit abort() by lighttpd. This is not exploitable beyond triggering the explicit abort() with subsequent application exit.
2018(1)
CVE-2018-19052
7.5An issue was discovered in mod_alias_physical_handler in mod_alias.c in lighttpd before 1.4.50. There is potential ../ path traversal of a single directory above an alias target, with a specific mod_alias configuration where the matched alias lacks a trailing '/' character, but the alias target filesystem path does have a trailing '/' character.



Contact Us

Shodan ® - All rights reserved