Search Results

have tried a few "smell tests": Does the web application have a posted security policy Do the developers discuss security in updates/change-logs/announcements/newsletters Is security mentioned as a feature …

Additionally, you have to assume that an attacker with physical access can find a local elevation-of-privilege vulnerability at some point. … This feature is generally available, through either built-in functionality or third-party software, for most operating systems. It's got weaknesses of its own, though. …

Attacking your upload feature in particular may be relatively difficult, because the attacker will have to convince the victim to upload a malicious file. …

I am currently implementing a feature that allows users to upload documents (mainly pdfs) and view them in the browser without storing them on a server. …

It basically "pings" other devices within the network and attempts to spread to them if they are also vulnerable. … The best feature of this is that we you disconnect an infected device and connect it to another network, it will start sending the same packages through the new network and start spreading once again. …

[They ignored my request to opt-out from this feature, just stopped sending me these emails] Can it be treated as a vulnerability? Does it have a name? …

A file upload feature which lets you upload PHP scripts isn't a vulnerability by itself. … It may very well turn out that there's no vulnerability at all. …

harm: If users trust the site (even when they shouldn't), an attacker could try to perform phishing, e.g., set up a fake paywall to get payment data, or collect passwords through a fake registration feature …

The vulnerability CVE-2024-7257 isn't in the admin-related code. … This feature is supposed to allow customers to upload a file when they order an item. …

There's nothing inherently wrong with this (it can actually be a security feature), and this isn't related to SSH in particular. …

This feature was not included in HTTP/2. Encrypting this data helps keep actionable information about user behavior out of attackers’ hands. …

The HTTP X-XSS-Protection response header was a feature of Internet Explorer, Chrome and Safari that stopped pages from loading when they detected reflected cross-site scripting (XSS) attacks. … Warning: Even though this feature can protect users of older web browsers that don't yet support CSP, in some cases, XSS protection can create XSS vulnerabilities in otherwise safe websites. …

So this feature doesn't match your understanding of an “isolated VM” which can be used to securely analyze malware. In your screenshot, the term “isolated” also doesn't appear anywhere. … And to be fair, not every RDP vulnerability allows an attacker to compromise the client. …

The VM will from now on only be accessible via RDP, once you enable the isolated VM feature. Isn't that (RDP) a gigantic vulnerable attacking vector for any malware debugged under the VM? …

No feature of the Web Storage API prevents this. In comparison, cookies with the HttpOnly attribute generally cannot be accessed with JavaScript, so this particular attack doesn't work. … While an attacker cannot read the tokens, they can still use them if they've found an XSS vulnerability. Whenever they make a request to the protected API, the token is automatically included. …