New answers tagged

0

This is a normal log4j mass-scanning. This doesn't mean that it was successful (in this case they were trying to install a cryptominer). Since you had already upgraded everything (and apparently, you weren't even vulnerable to begin with) that should be fine. If you have access to firewall logs at that time, you could confirm there was no outgoing connection ...


0

Status code really not matter for this instance. If the domains / IP's you have listed still available just get the bash files and take a quick look. Most of the exploitation happening regarding log4j is mostly crypto-miners. You can also listen to outbound - inbound traffic on hosted device to comfort yourself. Other than that, you simply need to follow ...


0

The cross-origin nature of a request can be of interest on the server-side beyond allowing/disallowing the request for CORS purposes. In particular, you may want to implement a resource-isolation policy: It is common for resources exposed by a given web application to only be loaded by the application itself, and not by other websites. In such cases, ...


4

There is no reason to handle them on the backend as they can easily be spoofed. The concept of CORS is to ensure one resource (say hacker.com) cannot access another resource (say facebook.com) in the browser unless the accessed resource gives permissions. This is only relevant in the context of a browser as the resources being accessed are cookies, headers ...


Top 50 recent answers are included