According to this scan,
the host for the security system was running on Linux and thus it was prone to
service denial, remotely. As a result, the system became vulnerable. The
identified nodes that contributed to the system vulnerability were 188.8.131.52(1-1-1-167.tvc-ip.com).
The vulnerability of this system was identified through the vulnerability
detection method that is inherent in the security system. The vulnerability of
this system implies that security is prone to any attack, thus any remote
attack is likely to lead to kernel crash, if it is exploited by illegitimate
intruders. The obvious implication of these illegitimate users may deny access
to legitimate users of this security and thus bring about insecurity concerns. The
best way to overcome or fight such types of system vulnerabilities is by upgrading
the system’s Linux kernel version from the version you are using now to 3.0.17,
3.1.9 or 3.2.1.
In this scan, the web
server used was susceptible to any access had a long basic authentication
field. This vulnerability was to the extent of causing continual web server
crashes, or in some cases a cracker or hacker of your security system can execute
arbitrary codes on your security system. The affected nodes revealed in this
scan were 184.108.40.206(1-1-1-169.tvc-ip.com). The best solution for this type of server
vulnerability is upgrading the security system software or protecting the
security with a filtering reverse proxy.
this scan, it was revealed that the security system used was running on a
server with SSL/TTL, and as such the system is liable to information disclosure
susceptibility. The fault detected in this system showed that vulnerability
arose due to a cookie that did not use ‘secure’ attribute and as such hackers
find it easy to access this system. The affected nodes in this scan were 220.127.116.11(1-1-1-169.tvc-ip.com).
The best solution for this security system is to ensure that the ‘secure’
attribute is set hence ensuring all the cookies are sent over a SSL/TTL
In this scan, it was
revealed that the routine reports for all the SSL/TTL cipher suites are
accepted by a service that makes attack vectors exist only on HTTPS services. The
64-bit blocker 3DES was made susceptible to SWEET32 hijacking attacks. The
affected nodes revealed in this scan were 18.104.22.168(mail.hrfmlaw.com) and
22.214.171.124(1-1-1-169.tvc-ip.com). To overcome this challenge, there needs to be
changes made on configurations made in the aforementioned services, to ensure
all the listed cipher suites do not appear at all.