Vulnerability Scan Result
| Title: | No title found |
| Description: | No description found |
| ip_address | 74.225.217.73 |
| country | IN  |
| network_name | Microsoft Corporation |
| asn | AS8075 |
80/tcp | http | - - |
443/tcp | tcpwrapped | - - |
No technologies could be detected.
Web Application Vulnerabilities
Evidence
| URL | Cookie Name | Evidence |
|---|---|---|
| https://myportal.redingtonmea.com/ConflictOfInterest/css/Redington_Web_Thm.Redington_Web_Thm.css | dtCookie | Set-Cookie: dtCookie=v_4_srv_1_sn_B3B287F642AD257B41B460572FFECEFC_perc_100000_ol_0_mul_1_app-3A995237bbe4ce141a_1_rcs-3Acss_0 |
Vulnerability description
We found that a cookie has been set without the Secure flag, which means the browser will send it over an unencrypted channel (plain HTTP) if such a request is made. The root cause for this usually revolves around misconfigurations in the code or server settings.
Risk description
The risk exists that an attacker will intercept the clear-text communication between the browser and the server and he will steal the cookie of the user. If this is a session cookie, the attacker could gain unauthorized access to the victim's web session.
Recommendation
Whenever a cookie contains sensitive information or is a session token, then it should always be passed using an encrypted channel. Ensure that the secure flag is set for cookies containing such sensitive information.
Classification
| CWE | CWE-614 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Cookie Name | Evidence |
|---|---|---|
| https://myportal.redingtonmea.com/ConflictOfInterest/css/Redington_Web_Thm.Redington_Web_Thm.css | dtCookie | Set-Cookie: .redingtonmea.com |
Vulnerability description
We found that the target application sets cookies with a domain scope that is too broad. Specifically, cookies intended for use within a particular application are configured in such a way that they can be accessed by multiple subdomains of the same primary domain.
Risk description
The risk is that a cookie set for example.com may be sent along with the requests sent to dev.example.com, calendar.example.com, hostedsite.example.com. Potentially risky websites under your main domain may access those cookies and use the victim session from the main site.
Recommendation
The `Domain` attribute should be set to the origin host to limit the scope to that particular server. For example if the application resides on server app.mysite.com, then it should be set to `Domain=app.mysite.com`
Classification
| CWE | CWE-614 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Cookie Name | Evidence |
|---|---|---|
| https://myportal.redingtonmea.com/ConflictOfInterest/css/Redington_Web_Thm.Redington_Web_Thm.css | dtCookie | The server responded with Set-Cookie header(s) that does not specify the HttpOnly flag: Set-Cookie: dtCookie=v_4_srv_1_sn_B3B287F642AD257B41B460572FFECEFC_perc_100000_ol_0_mul_1_app-3A995237bbe4ce141a_1_rcs-3Acss_0 |
Vulnerability description
We found that a cookie has been set without the HttpOnly flag, which means it can be accessed by potentially malicious JavaScript code running inside the web page. The root cause for this usually revolves around misconfigurations in the code or server settings.
Risk description
The risk is that an attacker who injects malicious JavaScript code on the page (e.g. by using an XSS attack) can access the cookie and can send it to another site. In case of a session cookie, this could lead to session hijacking.
Recommendation
Ensure that the HttpOnly flag is set for all cookies.
Classification
| CWE | CWE-1004 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Vulnerability description
We have noticed that the server is missing the security.txt file, which is considered a good practice for web security. It provides a standardized way for security researchers and the public to report security vulnerabilities or concerns by outlining the preferred method of contact and reporting procedures.
Risk description
There is no particular risk in not having a security.txt file for your server. However, this file is important because it offers a designated channel for reporting vulnerabilities and security issues.
Recommendation
We recommend you to implement the security.txt file according to the standard, in order to allow researchers or users report any security issues they find, improving the defensive mechanisms of your server.
Evidence
Vulnerability description
Website is accessible.
Infrastructure Vulnerabilities
Evidence
| Operating System | Accuracy |
|---|---|
| Linux 4.15 - 5.6 | 95% |
Vulnerability description
OS Detection
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| myportal.redingtonmea.com | A | IPv4 address | 74.225.217.73 |
| myportal.redingtonmea.com | CNAME | Canonical name | app856676.prod.cudawaas.com |
Risk description
An initial step for an attacker aiming to learn about an organization involves conducting searches on its domain names to uncover DNS records associated with the organization. This strategy aims to amass comprehensive insights into the target domain, enabling the attacker to outline the organization's external digital landscape. This gathered intelligence may subsequently serve as a foundation for launching attacks, including those based on social engineering techniques. DNS records pointing to services or servers that are no longer in use can provide an attacker with an easy entry point into the network.
Recommendation
We recommend reviewing all DNS records associated with the domain and identifying and removing unused or obsolete records.