Vulnerability Scan Result

Target:

https://www.grupoenergiabogota.com/

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

Submitted: April 19, 2025 from CO

Public Scan

Scan mode: Passive (non-intrusive)

Summary

low

Info

Low

Medium

High

Critical

Screenshot

Title:	Inicio - Grupo EnergÃa BogotÃ¡
Description:	Grupo Energia Bogota mÃ¡s 128 aÃ±os transportando energÃa en Colombia y a travÃ©s de sus filiales en Guatemala, PerÃº y Brasil

IP Information

IP address	18.245.187.5
Country	US
AS number	AS16509
Net name	Amazon Inc

IP address	18.245.187.14
Country	US
AS number	AS16509
Net name	Amazon Inc

IP address	18.245.187.39
Country	US
AS number	AS16509
Net name	Amazon Inc

IP address	18.245.187.87
Country	US
AS number	AS16509
Net name	Amazon Inc

Open Ports

80/tcp	http	Amazon CloudFront httpd -
443/tcp	https	CloudFront -

Web Technologies

Software / Version	Category
Amazon Web Services	PaaS
AWS Certificate Manager	SSL/TLS certificate authorities
Amazon CloudFront	CDN
Bootstrap 4.6.1	UI frameworks
Google Analytics GA4	Analytics
jQuery 3.6.0	JavaScript libraries
Popper	Miscellaneous
UserWay	Accessibility
Webpack	Miscellaneous
reCAPTCHA	Security
Google Tag Manager	Tag managers
HSTS	Security
Varnish	Caching

Web Application Vulnerabilities

Evidence

URL Evidence

URL	Evidence
https://www.grupoenergiabogota.com/	Response headers include the HTTP Content-Security-Policy security header with the following security issues:`script-src: script-src directive is missing. object-src: Missing object-src allows the injection of plugins which can execute JavaScript. We recommend setting it to 'none'. 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'. default-src: The default-src directive should be set as a fall-back when other restrictions have not been specified.`

https://www.grupoenergiabogota.com/

Response headers include the HTTP Content-Security-Policy security header with the following security issues:script-src: script-src directive is missing. object-src: Missing object-src allows the injection of plugins which can execute JavaScript. We recommend setting it to 'none'. 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'. default-src: The default-src directive should be set as a fall-back when other restrictions have not been specified.

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
Amazon Web Services	PaaS
AWS Certificate Manager	SSL/TLS certificate authorities
Amazon CloudFront	CDN
Bootstrap 4.6.1	UI frameworks
Google Analytics GA4	Analytics
jQuery 3.6.0	JavaScript libraries
Popper	Miscellaneous
UserWay	Accessibility
Webpack	Miscellaneous
reCAPTCHA	Security
Google Tag Manager	Tag managers
HSTS	Security
Varnish	Caching

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
https://www.grupoenergiabogota.com/robots.txt

Vulnerability description

We found the robots.txt on the target server. This file instructs web crawlers what URLs and endpoints of the web application they can visit and crawl. Website administrators often misuse this file while attempting to hide some web pages from the users.

Risk description

There is no particular security risk in having a robots.txt file. However, it's important to note that adding endpoints in it should not be considered a security measure, as this file can be directly accessed and read by anyone.

Recommendation

We recommend you to manually review the entries from robots.txt and remove the ones which lead to sensitive locations in the website (ex. administration panels, configuration files, etc).

Classification

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

Evidence

URL
Missing: https://www.grupoenergiabogota.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.grupoenergiabogota.com	A	IPv4 address	18.245.187.87
www.grupoenergiabogota.com	A	IPv4 address	18.245.187.5
www.grupoenergiabogota.com	A	IPv4 address	18.245.187.14
www.grupoenergiabogota.com	A	IPv4 address	18.245.187.39

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.