mirror of
https://github.com/drwetter/testssl.sh.git
synced 2025-09-12 17:21:17 +02:00
Doing a better guess for Opossum when tcp/80 is not a/v
This labels the result of a failed test for reaching port 80 when no direct connection is possible as likely not vulnerable. This seems safe to say, as there's another check whether a proxy is configured, like for corporate environments where a connection is only allowed though the proxy.
This commit is contained in:
parent
a549acd86d
commit
cb971b5336
@ -17735,8 +17735,10 @@ run_opossum() {
|
|||||||
prln_local_problem "direct connection to port 80 failed, better try without proxy"
|
prln_local_problem "direct connection to port 80 failed, better try without proxy"
|
||||||
fileout "$jsonID" "WARN" "direct connection to port 80 failed, try w/o no proxy" "$cve" "$cwe"
|
fileout "$jsonID" "WARN" "direct connection to port 80 failed, try w/o no proxy" "$cve" "$cwe"
|
||||||
else
|
else
|
||||||
outln "connection to port 80 failed"
|
out "likely "
|
||||||
fileout "$jsonID" "INFO" "connection to port 80 failed" "$cve" "$cwe"
|
pr_svrty_good "not vulnerable (OK)"
|
||||||
|
outln ", connection to port 80 failed"
|
||||||
|
fileout "$jsonID" "OK" "connection to port 80 failed" "$cve" "$cwe"
|
||||||
fi
|
fi
|
||||||
fi
|
fi
|
||||||
;;
|
;;
|
||||||
|
Loading…
x
Reference in New Issue
Block a user