Vulnerability Scan Result
| Title: | No title found |
| Description: | No description found |
| ip_address | 66.33.60.194 |
| country | US  |
| network_name | Amazon.com, Inc. |
| asn | AS16509 |
| ip_address | 76.76.21.93 |
| country | US |
| network_name | Amazon.com, Inc. |
| asn | AS16509 |
80/tcp | http | Vercel - |
443/tcp | https | Vercel - |
| Software / Version | Category |
|---|---|
| Vercel | PaaS |
| HSTS | Security |
Web Application Vulnerabilities
Evidence
Vulnerability description
We found that the target application's web server presents an SSL/TLS certificate that is not trusted by web browsers. This issue typically arises when the server uses a self-signed certificate, a certificate from an untrusted authority, or a certificate that has expired or is invalid for other reasons. The lack of a trusted certificate makes it challenging for users to verify the authenticity of the server, undermining the security of the SSL/TLS connection.
Risk description
The risk is that an attacker could easily mount a man-in-the-middle attack in order to sniff the SSL communication by presenting the user a fake SSL certificate.
Recommendation
We recommend you to configure a trusted SSL certificate for the web server. Examples of how to configure SSL for various servers for Apache and Nginx are referenced.
Classification
| CWE | CWE-295 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| Software / Version | Category |
|---|---|
| Vercel | PaaS |
| HSTS | Security |
Vulnerability description
We noticed that server software and technology details are exposed, potentially aiding attackers in tailoring specific exploits against identified systems and versions.
Risk description
The risk is that an attacker could use this information to mount specific attacks against the identified software type and version.
Recommendation
We recommend you to eliminate the information which permits the identification of software platform, technology, server and operating system: HTTP server headers, HTML meta information, etc.
Classification
| CWE | CWE-200 |
| 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.
Classification
| CWE | CWE-1188 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Infrastructure Vulnerabilities
Evidence
We found insecure DNS cookie usage on the following nameservers: ns1.vercel-dns-3.com, ns2.vercel-dns-3.com, ns3.vercel-dns-3.com, ns4.vercel-dns-3.com
Vulnerability description
We found that the server does not implement DNS Cookies or uses them insecurely. DNS Cookies help prevent DNS-based attacks, such as spoofing and amplification attacks.
Risk description
The risk exists because without DNS Cookies, the server is vulnerable to DNS spoofing and amplification attacks. Attackers can manipulate responses or use the server in distributed denial-of-service (DDoS) attacks, compromising network availability and security.
Recommendation
We recommend enabling DNS Cookies to prevent spoofed DNS responses. Ensure proper cookie validation is implemented to mitigate DNS amplification attacks. Regularly update DNS servers to support the latest DNS security features.
Evidence
| Operating System | Accuracy |
|---|---|
| Android 5.0.1 | 90% |
Vulnerability description
OS Detection
Evidence
| Software / Version | Category |
|---|---|
| Vercel | PaaS |
| HSTS | Security |
Vulnerability description
We noticed that server software and technology details are exposed, potentially aiding attackers in tailoring specific exploits against identified systems and versions.
Risk description
The risk is that an attacker could use this information to mount specific attacks against the identified software type and version.
Recommendation
We recommend you to eliminate the information which permits the identification of software platform, technology, server and operating system: HTTP server headers, HTML meta information, etc.
Evidence
| Software / Version | Category |
|---|---|
| Vercel | PaaS |
| HSTS | Security |
Vulnerability description
We noticed that server software and technology details are exposed, potentially aiding attackers in tailoring specific exploits against identified systems and versions.
Risk description
The risk is that an attacker could use this information to mount specific attacks against the identified software type and version.
Recommendation
We recommend you to eliminate the information which permits the identification of software platform, technology, server and operating system: HTTP server headers, HTML meta information, etc.
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| nurol-makina-sanayi.turkishbrands.org | A | IPv4 address | 76.76.21.22 |
| nurol-makina-sanayi.turkishbrands.org | A | IPv4 address | 66.33.60.129 |
| nurol-makina-sanayi.turkishbrands.org | NS | Name server | ns1.vercel-dns-3.com |
| nurol-makina-sanayi.turkishbrands.org | NS | Name server | ns2.vercel-dns-3.com |
| nurol-makina-sanayi.turkishbrands.org | NS | Name server | ns3.vercel-dns-3.com |
| nurol-makina-sanayi.turkishbrands.org | NS | Name server | ns4.vercel-dns-3.com |
| nurol-makina-sanayi.turkishbrands.org | SOA | Start of Authority | ns1.vercel-dns-3.com. awsdns-hostmaster.amazon.com. 1 3600 900 1209600 900 |
| nurol-makina-sanayi.turkishbrands.org | CAA | Certificate Authority Authorization | 0 issue "globalsign.com" |
| nurol-makina-sanayi.turkishbrands.org | CAA | Certificate Authority Authorization | 0 issue "letsencrypt.org" |
| nurol-makina-sanayi.turkishbrands.org | CAA | Certificate Authority Authorization | 0 issue "pki.goog" |
| nurol-makina-sanayi.turkishbrands.org | CAA | Certificate Authority Authorization | 0 issue "sectigo.com" |
| nurol-makina-sanayi.turkishbrands.org | CNAME | Canonical name | cname.vercel-dns.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.