Vulnerability Scan Result

Target:

http://interrao.ru/ (redirect)

Scanned target: https://www.interrao.ru/

Submitted: Nov 17, 2025 from LY

Public Scan

Scan mode: Passive (non-intrusive)

Summary

high

Info

Low

Medium

High

Critical

Screenshot

Screenshot could not be taken.

Title:	Интер РАО
Description:

IP Information

ip_address	213.221.45.163
country	RU
network_name	PJSC Vimpelcom
asn	AS3216

Open Ports

80/tcp	tcpwrapped	- -
443/tcp	tcpwrapped	- -

Web Technologies

Software / Version	Category
GSAP 1.19.0	JavaScript frameworks
Hammer.js 2.0.7	JavaScript libraries
jQuery 3.7.1	JavaScript libraries
Yandex.Metrika	Analytics
Nginx	Web servers, Reverse proxies
Open Graph	Miscellaneous
PHP	Programming languages
ScrollMagic 2.0.8	JavaScript libraries
1C-Bitrix	CMS, Ecommerce
Highcharts 4.2.6	JavaScript graphics
HSTS	Security

Web Application Vulnerabilities

Evidence

CVE	CVSS	EPSS Score	EPSS Percentile	Summary
CVE-2021-29489	7.6	0.00227	0.45462	Highcharts JS is a JavaScript charting library based on SVG. In Highcharts versions 8 and earlier, the chart options structure was not systematically filtered for XSS vectors. The potential impact was that content from untrusted sources could execute code in the end user's browser. The vulnerability is patched in version 9. As a workaround, implementers who are not able to upgrade may apply DOMPurify recursively to the options structure to filter out malicious markup.
CVE-2018-20801	7.5	0.01321	0.79257	In js/parts/SvgRenderer.js in Highcharts JS before 6.1.0, the use of backtracking regular expressions permitted an attacker to conduct a denial of service attack against the SVGRenderer component, aka ReDoS.

Vulnerability description

Outdated or vulnerable software components include versions of server-side software that are no longer supported or have known, publicly disclosed vulnerabilities. Using outdated software significantly increases the attack surface of a system and may allow unauthorized access, data leaks, or service disruptions. Vulnerabilities in these components are often well-documented and actively exploited by attackers. Without security patches or vendor support, any weaknesses remain unmitigated, exposing the application to risks. In some cases, even after patching, the reported version may remain unchanged, requiring manual verification.

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. Since the vulnerabilities were discovered using only version-based testing, the risk level for this finding will not exceed 'high' severity. Critical risks will be assigned to vulnerabilities identified through accurate active testing methods.

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-1035
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL Evidence

URL	Evidence
https://www.interrao.ru/	Response headers include the HTTP Content-Security-Policy security header with the following security issues:default-src: The default-src directive should be set as a fall-back when other restrictions have not been specified. script-src: 'unsafe-eval' allows the execution of code injected into DOM APIs such as eval(). 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'. object-src: Missing object-src allows the injection of plugins which can execute JavaScript. We recommend setting it to 'none'. script-src: ''unsafe-inline'' allows the execution of unsafe in-page scripts and event handlers. script-src: 'self' can be problematic if you host JSONP, Angular or user uploaded files.

https://www.interrao.ru/

Response headers include the HTTP Content-Security-Policy security header with the following security issues:default-src: The default-src directive should be set as a fall-back when other restrictions have not been specified. script-src: 'unsafe-eval' allows the execution of code injected into DOM APIs such as eval(). 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'. object-src: Missing object-src allows the injection of plugins which can execute JavaScript. We recommend setting it to 'none'. script-src: ''unsafe-inline'' allows the execution of unsafe in-page scripts and event handlers. script-src: 'self' can be problematic if you host JSONP, Angular or user uploaded files.

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
OWASP Top 10 - 2021

Evidence

URL
https://www.interrao.ru/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).

Evidence

Software / Version	Category
GSAP 1.19.0	JavaScript frameworks
Hammer.js 2.0.7	JavaScript libraries
jQuery 3.7.1	JavaScript libraries
Yandex.Metrika	Analytics
Nginx	Web servers, Reverse proxies
Open Graph	Miscellaneous
PHP	Programming languages
ScrollMagic 2.0.8	JavaScript libraries
1C-Bitrix	CMS, Ecommerce
Highcharts 4.2.6	JavaScript graphics
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

URL	Method	Parameters	Evidence
https://www.interrao.ru/	GET	Headers: User-Agent=Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/108.0.0.0 Safari/537.36	Email Address: office@interrao.ru

Vulnerability description

We noticed that this web application exposes email addresses, which might be unintended. While not inherently a vulnerability, this information could be leveraged in social engineering or spam related activities.

Risk description

The risk is that exposed email addresses within the application could be accessed by unauthorized parties. This could lead to privacy violations, spam, phishing attacks, or other forms of misuse.

Recommendation

Compartmentalize the application to have 'safe' areas where trust boundaries can be unambiguously drawn. Do not allow email addresses to go outside of the trust boundary, and always be careful when interfacing with a compartment outside of the safe area.

Classification

CWE	CWE-200
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL
Missing: https://www.interrao.ru/.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.

Infrastructure Vulnerabilities

Operating System	Accuracy
Tomato 1.28 (Linux 2.4.20)	100%

Evidence

Domain Queried	DNS Record Type	Description	Value
www.interrao.ru	A	IPv4 address	213.221.45.163
www.interrao.ru	SPF	Sender Policy Framework	"v=spf1 mx ip4:213.221.45.163 -all"

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.