New answers tagged vulnerability
3
The HTTP method does not matter for Cross Site Scripting attacks (XSS). It is even possible to get XSS trough the HTTP TRACE method.
Is it possible to have reflective XSS through POST requests?
Most definitely!
-1
This is how you can benefit to each other:
You can give them the details of the hole
They can give you a lot of money
This is how you can harm each other:
You can publicize the hole, or exploit it for yourself
They can initiate a legal case against you
Check this. It is actually a clear Prisoner's Dilemma situation.
The sad truth is, that in such a case,...
2
There are two quick observation:
Using eval is very dangerous and your variable ${command} is not efficiently sanitized. (They could contain backticks, period, control chars, etc)
Using bash for sensible operation is not recommended as they suffer from a lot of vulnerabilities. I recommend using poor shell (like dash), for critical scripts. (Or more evolved ...
0
First of all, there is no reason to worry about code injection on a local shell script.
If you are running this remotely it could be an issue. I did some experimenting with the example below and didn't find any direct ways to inject any extra commands, except for the one word. Keep in mind, that you should also whitelist the allowed commands in a production ...
8
Responsible disclosure, which most people on this site seem to endorse (including me), and is regarded as the most ethical way to notify a company of a vulnerability, is precisely what your comment says you won't do: Saying that you will tell the public.
With responsible disclosure, you're just giving them a chance to plug the hole and manage PR first, by ...
0
Does this have any security impact?
The answer is 'possibly'. Anywhere you have a external data being injected into a webpage there is a risk of XSS, and this risk is mitigated both by the quality of the sanitization of the external data and the way the page has been constructed.
In general escaping or removing ", < and > is a decent start but many ...
1
As a general rule, every security application that performs monitoring or blocking will have a place for you to review any alerts. If it doesn't have that, then it's either useless or a complete fraud.
In your case, there is a detailed view.
Thie picture below was taken from McAfee Knowledge Center article TS102852. You can find the same article by ...
0
You can look at all current network connections using the windows cli/shell/cmd. This will additional show the process opening the connections.
netstat -nao
Another way would be using a gui application from the windows sysinternal suite.
This will show you all tcp connections and the opened ports of you system.
tcpview.exe and portmon.exe
You can ...
1
As I assume you want to monitoring tool beside then WAF, there is two well known tools for this purpose:
ManageEngine event log analyzer
Nagios IIS log monitoring
3
Not any sort of vulnerability; simply a usability issue that might affect users visiting the site from a malformed URL.
It is not an easy way to perform a DOS attack, because there is no evidence that this is taking any more resources on the server than hitting non-redirecting set of pages, or preventing other users from accessing different pages. You can ...
8
If you can fake the price this way then this is basically due to improper validation of user input. It does not matter if the fake price comes because you've used another API endpoint (spoofing name resolution with manipulating hosts file or DNS) or if you've edited the page in the browser or if you've changed what got submitted to the server by intercepting ...
1
Sounds like you need to do a bit more to reduce your attack surface. While you have already done a lot of things to improve your situation which is good, unfortunately you have absolutely no control of your physical network which is generally the source of most hacking attempts. This is compounded even further by the fact that that it is a shared network and ...
2
Prototype pollution can be exploited at the front end. Payloads can be sent in similar fashion to reflected and stored XSS, and affect the behaviour of the front end for the victim recieving them. So this is a real issue that you should deal with. The most famous example of prototype pollution vulnerabilities is probably from jQuery - a client side library.
...
0
Buffer overflows don't just occur with text, so it may be possible to pass an 'image' that exploits something in the image processing. Bad code always exists though...using OWASP has a good example page, and we can construct a simple function which could overflow:
int main(int argc, char **argv)
{
char items = imageprocessor(); // process image seen
...
Top 50 recent answers are included
