Vulnerability Scan Result

Target:

https://telemost.yandex.ru/j/81337029474252

Scanned target: https://telemost.yandex.ru/j/81337029474252

Submitted: Oct 14, 2025 from CI

Public Scan

Scan mode: Passive (non-intrusive)

Summary

medium

Info

Low

Medium

High

Critical

Screenshot

Screenshot could not be taken.

Title:	Яндекс Телемост — бесплатные видеовстречи без регистрации и ограничения по времени
Description:	Бесплатные видеоконференции и встречи прямо в браузере. Подключение без регистрации, удобно с ПК и телефона. Работайте, учитесь и общайтесь онлайн

IP Information

ip_address	87.250.251.10
country	RU
network_name	Teletech D.o.o Beograd
asn	AS208398

Open Ports

80/tcp	http	- -
443/tcp	https	- -

Web Technologies

Software / Version	Category
Yandex SmartCaptcha	Security
core-js 3.32.1	JavaScript libraries
Yandex.Metrika	Analytics
Open Graph	Miscellaneous
React	JavaScript frameworks
HSTS	Security

Web Application Vulnerabilities

Evidence

URL	Cookie Name	Evidence
https://telemost.yandex.ru/j/81337029474252	background, agreementShown, _yasc, yandexuid	The server responded with Set-Cookie header(s) that does not specify the HttpOnly flag: Set-Cookie: background=20 Set-Cookie: agreementShown=1 Set-Cookie: _yasc=lKFRtq6LSDom+jj3g5t7nJD7iVsMiB0opDGoGDB6wvw9PQmWKF5+N0GTp6Dn3A== Set-Cookie: yandexuid=6951102591760441439

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

Evidence

URL	Cookie Name	Evidence
https://telemost.yandex.ru/j/81337029474252	_yasc	Set-Cookie: .yandex.ru

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

Software / Version	Category
Yandex SmartCaptcha	Security
core-js 3.32.1	JavaScript libraries
Yandex.Metrika	Analytics
Open Graph	Miscellaneous
React	JavaScript frameworks
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	Evidence
https://telemost.yandex.ru/j/81337029474252	Response headers do not include the Referrer-Policy HTTP security header as well as the `<meta/>` tag with name 'referrer' is not present in the response.

Vulnerability description

We noticed that the target application's server responses lack the Referrer-Policy HTTP header, which controls how much referrer information the browser will send with each request originated from the current web application.

Risk description

The risk is that if a user visits a web page (e.g. "http://example.com/pricing/") and clicks on a link from that page going to e.g. "https://www.google.com", the browser will send to Google the full originating URL in the `Referer` header, assuming the Referrer-Policy header is not set. The originating URL could be considered sensitive information and it could be used for user tracking.

Recommendation

The Referrer-Policy header should be configured on the server side to avoid user tracking and inadvertent information leakage. The value `no-referrer` of this header instructs the browser to omit the Referer header entirely.

Classification

CWE	CWE-693
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL Evidence

URL	Evidence
https://telemost.yandex.ru/j/81337029474252	Response headers include the HTTP Content-Security-Policy security header with the following security issues: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'. object-src: We recommend restricting object-src to 'none'. report-uri: report-uri is deprecated in CSP3. Please use the report-to directive instead. 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'.

https://telemost.yandex.ru/j/81337029474252

Response headers include the HTTP Content-Security-Policy security header with the following security issues: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'. object-src: We recommend restricting object-src to 'none'. report-uri: report-uri is deprecated in CSP3. Please use the report-to directive instead. 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'.

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	Method	Summary
https://telemost.yandex.ru/j/81337029474252	OPTIONS	We did a HTTP OPTIONS request. The server responded with a 200 status code and the header: `Allow: GET,HEAD` Request / Response

Vulnerability description

We have noticed that the webserver responded with an Allow HTTP header when an OPTIONS HTTP request was sent. This method responds to requests by providing information about the methods available for the target resource.

Risk description

The only risk this might present nowadays is revealing debug HTTP methods that can be used on the server. This can present a danger if any of those methods can lead to sensitive information, like authentication information, secret keys.

Recommendation

We recommend that you check for unused HTTP methods or even better, disable the OPTIONS method. This can be done using your webserver configuration.

Classification

CWE	CWE-16
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL
Missing: https://telemost.yandex.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

Evidence

Domain Queried	DNS Record Type	Description	Value
telemost.yandex.ru	A	IPv4 address	87.250.251.10
telemost.yandex.ru	MX	Mail server	10 mx.yandex.ru
telemost.yandex.ru	AAAA	IPv6 address	2a02:6b8::28c
telemost.yandex.ru	TXT	Text record	"yandex-verification: bdd5e4f331529c13"
telemost.yandex.ru	TXT	Text record	"google-site-verification=WDT04YdIJteeEpewlb7vhASFQUSg6cA5FMnD4AmBPIk"
telemost.yandex.ru	TXT	Text record	"google-site-verification=RumdDvkmY52QVTBTsqzXZUJcfaAVNfTUSzRsEzWTkSg"
telemost.yandex.ru	TXT	Text record	"mailru-verification: fc2f0cf44c1d5286"
telemost.yandex.ru	SPF	Sender Policy Framework	"v=spf1 redirect=_spf.yandex.ru"

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.

Operating System	Accuracy
Crestron XPanel control system	87%

Evidence

Software / Version	Category
React	JavaScript frameworks
Yandex.Metrika	Analytics
Yandex SmartCaptcha	Security
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
React	JavaScript frameworks
Yandex.Metrika	Analytics
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.