Vulnerability Scan Result

Target:

https://www.eliteinnovationsandservice.com/

Scanned target: https://www.eliteinnovationsandservice.com/

Submitted: April 18, 2025 from OM

Public Scan

Scan mode: Passive (non-intrusive)

Summary

medium

Info

Low

Medium

High

Critical

Screenshot

https://www.eliteinnovationsandservice.com/

Title:	Elite Innovations and Services
Description:	No description found

IP Information

IP address	104.21.64.1
Country	-
AS number	AS13335
Net name	Cloudflare Inc

IP address	104.21.112.1
Country	-
AS number	AS13335
Net name	Cloudflare Inc

IP address	104.21.16.1
Country	-
AS number	AS13335
Net name	Cloudflare Inc

IP address	104.21.80.1
Country	-
AS number	AS13335
Net name	Cloudflare Inc

IP address	104.21.32.1
Country	-
AS number	AS13335
Net name	Cloudflare Inc

IP address	104.21.48.1
Country	-
AS number	AS13335
Net name	Cloudflare Inc

IP address	104.21.96.1
Country	-
AS number	AS13335
Net name	Cloudflare Inc

Open Ports

80/tcp	http	Cloudflare http proxy -
443/tcp	https	cloudflare -
8080/tcp	http	Cloudflare http proxy -
8443/tcp	http	cloudflare -

Web Technologies

Software / Version	Category
FancyBox 3.5.7	JavaScript libraries
Google Font API	Font scripts
HTTP/3	Miscellaneous
jQuery 3.5.1	JavaScript libraries
Kajabi	Ecommerce
AOS	JavaScript libraries
Moment.js 2.24.0	JavaScript libraries
Open Graph	Miscellaneous
Parsley.js	JavaScript libraries
Popper	Miscellaneous
Ruby	Programming languages
Ruby on Rails	Web frameworks
Rudderstack	Customer data platform
Cloudflare	CDN
Cloudflare Bot Management	Security
jsDelivr	CDN
Lodash 1.8.2	JavaScript libraries

Web Application Vulnerabilities

Evidence

Risk Level	CVSS	CVE	Summary	Affected software
	5	CVE-2022-24785	Moment.js is a JavaScript date library for parsing, validating, manipulating, and formatting dates. A path traversal vulnerability impacts npm (server) users of Moment.js between versions 1.0.1 and 2.29.1, especially if a user-provided locale string is directly used to switch moment locale. This problem is patched in 2.29.2, and the patch can be applied to all affected versions. As a workaround, sanitize the user-provided locale name before passing it to Moment.js.	moment 2.24.0
	5	CVE-2022-31129	moment is a JavaScript date library for parsing, validating, manipulating, and formatting dates. Affected versions of moment were found to use an inefficient parsing algorithm. Specifically using string-to-date parsing in moment (more specifically rfc2822 parsing, which is tried by default) has quadratic (N^2) complexity on specific inputs. Users may notice a noticeable slowdown is observed with inputs above 10k characters. Users who pass user-provided strings without sanity length checks to moment constructor are vulnerable to (Re)DoS attacks. The problem is patched in 2.29.4, the patch can be applied to all affected versions with minimal tweaking. Users are advised to upgrade. Users unable to upgrade should consider limiting date lengths accepted from user input.	moment 2.24.0

Vulnerability description

We noticed known vulnerabilities in the target application based on the server responses. They are usually related to outdated systems and expose the affected applications to the risk of unauthorized access to confidential data and possibly denial of service attacks. Depending on the system distribution the affected software can be patched but displays the same version, requiring manual checking.

Risk description

The risk is that an attacker could search for an appropriate exploit (or create one himself) for any of these vulnerabilities and use it to attack the system.

Recommendation

In order to eliminate the risk of these vulnerabilities, we recommend you check the installed software version and upgrade to the latest version.

Classification

CWE	CWE-1026
OWASP Top 10 - 2017	A9 - Using Components with Known Vulnerabilities
OWASP Top 10 - 2021	A6 - Vulnerable and Outdated Components

Evidence

URL	Evidence
https://www.eliteinnovationsandservice.com/	Response headers do not include the HTTP Strict-Transport-Security header

Vulnerability description

We noticed that the target application lacks the HTTP Strict-Transport-Security header in its responses. This security header is crucial as it instructs browsers to only establish secure (HTTPS) connections with the web server and reject any HTTP connections.

Risk description

The risk is that lack of this header permits an attacker to force a victim user to initiate a clear-text HTTP connection to the server, thus opening the possibility to eavesdrop on the network traffic and extract sensitive information (e.g. session cookies).

Recommendation

The Strict-Transport-Security HTTP header should be sent with each HTTPS response. The syntax is as follows: `Strict-Transport-Security: max-age=<seconds>[; includeSubDomains]` The parameter `max-age` gives the time frame for requirement of HTTPS in seconds and should be chosen quite high, e.g. several months. A value below 7776000 is considered as too low by this scanner check. The flag `includeSubDomains` defines that the policy applies also for sub domains of the sender of the response.

Classification

CWE	CWE-693
OWASP Top 10 - 2017	A6 - Security Misconfiguration
OWASP Top 10 - 2021	A5 - Security Misconfiguration

Evidence

URL Evidence

URL	Evidence
https://www.eliteinnovationsandservice.com/	Response headers include the HTTP Content-Security-Policy security header with the following security issues:base-uri: Missing base-uri allows the injection of base tags. They can be used to set the base URL for all relative (script) URLs to an attacker controlled domain. We recommend setting it to 'none' or 'self'. frame-ancestors: This directive tells the browser whether you want to allow your site to be framed or not. By preventing a browser from framing your site you can defend against attacks like clickjacking. The recommended value is 'none' or 'self'. default-src: The default-src directive should be set as a fall-back when other restrictions have not been specified. object-src: Missing object-src allows the injection of plugins which can execute JavaScript. We recommend setting it to 'none'. script-src: script-src directive is missing.

https://www.eliteinnovationsandservice.com/

Response headers include the HTTP Content-Security-Policy security header with the following security issues:base-uri: Missing base-uri allows the injection of base tags. They can be used to set the base URL for all relative (script) URLs to an attacker controlled domain. We recommend setting it to 'none' or 'self'. frame-ancestors: This directive tells the browser whether you want to allow your site to be framed or not. By preventing a browser from framing your site you can defend against attacks like clickjacking. The recommended value is 'none' or 'self'. default-src: The default-src directive should be set as a fall-back when other restrictions have not been specified. object-src: Missing object-src allows the injection of plugins which can execute JavaScript. We recommend setting it to 'none'. script-src: script-src directive is missing.

Vulnerability description

We noticed that the Content-Security-Policy (CSP) header configured for the web application includes unsafe directives. The CSP header activates a protection mechanism implemented in web browsers which prevents exploitation of Cross-Site Scripting vulnerabilities (XSS) by restricting the sources from which content can be loaded or executed.

Risk description

For example, if the unsafe-inline directive is present in the CSP header, the execution of inline scripts and event handlers is allowed. This can be exploited by an attacker to execute arbitrary JavaScript code in the context of the vulnerable application.

Recommendation

Remove the unsafe values from the directives, adopt nonces or hashes for safer inclusion of inline scripts if they are needed, and explicitly define the sources from which scripts, styles, images or other resources can be loaded.

Classification

CWE	CWE-693
OWASP Top 10 - 2017	A6 - Security Misconfiguration
OWASP Top 10 - 2021	A5 - Security Misconfiguration

Evidence

Software / Version	Category
FancyBox 3.5.7	JavaScript libraries
Google Font API	Font scripts
HTTP/3	Miscellaneous
jQuery 3.5.1	JavaScript libraries
Kajabi	Ecommerce
AOS	JavaScript libraries
Moment.js 2.24.0	JavaScript libraries
Open Graph	Miscellaneous
Parsley.js	JavaScript libraries
Popper	Miscellaneous
Ruby	Programming languages
Ruby on Rails	Web frameworks
Rudderstack	Customer data platform
Cloudflare	CDN
Cloudflare Bot Management	Security
jsDelivr	CDN
Lodash 1.8.2	JavaScript libraries

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

OWASP Top 10 - 2017	A6 - Security Misconfiguration
OWASP Top 10 - 2021	A5 - Security Misconfiguration

Evidence

URL
Missing: https://www.eliteinnovationsandservice.com/.well-known/security.txt

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

OWASP Top 10 - 2017	A6 - Security Misconfiguration
OWASP Top 10 - 2021	A5 - Security Misconfiguration

Infrastructure Vulnerabilities

Evidence

Domain Queried	DNS Record Type	Description	Value
www.eliteinnovationsandservice.com	A	IPv4 address	104.21.48.1
www.eliteinnovationsandservice.com	A	IPv4 address	104.21.112.1
www.eliteinnovationsandservice.com	A	IPv4 address	104.21.64.1
www.eliteinnovationsandservice.com	A	IPv4 address	104.21.16.1
www.eliteinnovationsandservice.com	A	IPv4 address	104.21.96.1
www.eliteinnovationsandservice.com	A	IPv4 address	104.21.80.1
www.eliteinnovationsandservice.com	A	IPv4 address	104.21.32.1
www.eliteinnovationsandservice.com	AAAA	IPv6 address	2606:4700:3030::6815:5001
www.eliteinnovationsandservice.com	AAAA	IPv6 address	2606:4700:3030::6815:2001
www.eliteinnovationsandservice.com	AAAA	IPv6 address	2606:4700:3030::6815:3001
www.eliteinnovationsandservice.com	AAAA	IPv6 address	2606:4700:3030::6815:1001
www.eliteinnovationsandservice.com	AAAA	IPv6 address	2606:4700:3030::6815:6001
www.eliteinnovationsandservice.com	AAAA	IPv6 address	2606:4700:3030::6815:4001
www.eliteinnovationsandservice.com	AAAA	IPv6 address	2606:4700:3030::6815:7001

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.

Evidence

Software / Version	Category
Kajabi	Ecommerce
Ruby	Programming languages
Ruby on Rails	Web frameworks
Rudderstack	Customer data platform
Parsley.js	JavaScript libraries
jsDelivr	CDN
Cloudflare Bot Management	Security
Cloudflare	CDN
HTTP/3	Miscellaneous
Google Font API	Font scripts
Open Graph	Miscellaneous

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
Cloudflare	CDN

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.