Vulnerability Scan Result

Target:

https://es.linkedin.com/company/geniallyofficial

Scanned target: https://es.linkedin.com/company/geniallyofficial

Submitted: Dec 03, 2025 from RS

Public Scan

Scan mode: Passive (non-intrusive)

Summary

medium

Info

Low

Medium

High

Critical

Screenshot

Screenshot could not be taken.

Title:	Genially \| LinkedIn
Description:	Genially \| 35.129 seguidores en LinkedIn. El espacio para explorar, aprender y gamificar \| El espacio para explorar, aprender y gamificar

IP Information

ip_address	13.107.213.45
country	US
network_name	Microsoft Corporation
asn	AS8075

ip_address	13.107.246.45
country	US
network_name	Microsoft Corporation
asn	AS8075

Open Ports

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

Web Technologies

Software / Version	Category
Azure	PaaS
Azure Front Door	Load balancers
web-vitals	JavaScript libraries, RUM
Java	Programming languages
DigiCert	SSL/TLS certificate authorities
HSTS	Security
JSP	Web frameworks

Web Application Vulnerabilities

Evidence

URL	Cookie Name	Evidence
https://es.linkedin.com/company/geniallyofficial	JSESSIONID	Set-Cookie: .es.linkedin.com

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

URL	Cookie Name	Evidence
https://es.linkedin.com/company/geniallyofficial	JSESSIONID, lang, bcookie, li_gc, lidc	The server responded with Set-Cookie header(s) that does not specify the HttpOnly flag: Set-Cookie: JSESSIONID=ajax:7130274691963616566 Set-Cookie: lang=v=2⟨=es-es Set-Cookie: bcookie="v=2&0a54383f-6861-4f2e-86eb-17ba38bc8154" Set-Cookie: li_gc=MTswOzE3NjQ3NjYzMTQ7MjswMjEZRySrJGDP1kE8JmVUVCdSTvstCgkBbVoUmVuScp0N0w== Set-Cookie: lidc="b=VGST08:s=V:r=V:a=V:p=V:g=3356:u=1:x=1:i=1764766314:t=1764852714:v=2:sig=AQFyEj4CtoZgFr6Kk2EYDyXZzH3IaFOd"

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://es.linkedin.com/company/geniallyofficial	trkCode, trkInfo, rtc	Set-Cookie: trkCode=bf Set-Cookie: trkInfo=AQHQabCPr0s90QAAAZrkRRkIj8gA_-Q0PB8z0-scqsxgFjoFdKGvLn2U_irY_E4Y0Bydj9kxwGKPHIJgstbhqRO3QkH8r9yFJhCrb_59T0CTdOAksk9IrmKfx3Gh1v0Z6OKVLPg= Set-Cookie: rtc=AQHvKli71iwnpAAAAZrkRRkIba9iBmPXS8U-hKu_96HrBnMhsmQmNNAhOP9p1ts54KM9LjvHSrJNzbxIA8uRqts4Q7IbI688vrNAv0Gik8o7cPFrYacpLxmd619egPdiNqyJjTvp-PGEL-3uAYOsRc3RQarYkTiGXNa-w9O579QiiMaUpf55e46sDd6MfgTV3QI1NMJX_oK2iqB3vHon33HHll4TkngT4rWc-XSRGQ==

Vulnerability description

We found that a cookie has been set without the Secure flag, which means the browser will send it over an unencrypted channel (plain HTTP) if such a request is made. The root cause for this usually revolves around misconfigurations in the code or server settings.

Risk description

The risk exists that an attacker will intercept the clear-text communication between the browser and the server and he will steal the cookie of the user. If this is a session cookie, the attacker could gain unauthorized access to the victim's web session.

Recommendation

Whenever a cookie contains sensitive information or is a session token, then it should always be passed using an encrypted channel. Ensure that the secure flag is set for cookies containing such sensitive information.

Classification

CWE	CWE-614
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL
https://es.linkedin.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).

Evidence

URL	Evidence
https://es.linkedin.com/company/geniallyofficial	Response headers do not include the X-Content-Type-Options HTTP security header

Vulnerability description

We noticed that the target application's server responses lack the X-Content-Type-Options header. This header is particularly important for preventing Internet Explorer from reinterpreting the content of a web page (MIME-sniffing) and thus overriding the value of the Content-Type header.

Risk description

The risk is that lack of this header could make possible attacks such as Cross-Site Scripting or phishing in Internet Explorer browsers.

Recommendation

We recommend setting the X-Content-Type-Options header such as `X-Content-Type-Options: nosniff`.

Classification

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

Evidence

URL	Evidence
https://es.linkedin.com/company/geniallyofficial	Response does not include the HTTP Content-Security-Policy security header or meta tag

Vulnerability description

We noticed that the target application lacks the Content-Security-Policy (CSP) header in its HTTP responses. The CSP header is a security measure that instructs web browsers to enforce specific security rules, effectively preventing the exploitation of Cross-Site Scripting (XSS) vulnerabilities.

Risk description

The risk is that if the target application is vulnerable to XSS, lack of this header makes it easily exploitable by attackers.

Recommendation

Configure the Content-Security-Header to be sent with each HTTP response in order to apply the specific policies needed by the application.

Classification

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

Evidence

Software / Version	Category
Azure	PaaS
Azure Front Door	Load balancers
web-vitals	JavaScript libraries, RUM
Java	Programming languages
DigiCert	SSL/TLS certificate authorities
HSTS	Security
JSP	Web frameworks

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

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

https://es.linkedin.com/company/geniallyofficial

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

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	Evidence
https://es.linkedin.com/company/geniallyofficial	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
OWASP Top 10 - 2021

Evidence

URL	Evidence
https://es.linkedin.com/company/geniallyofficial	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

Infrastructure Vulnerabilities

Operating System	Accuracy
Crestron XPanel control system	87%

Evidence

Software / Version	Category
Java	Programming languages
JSP	Web frameworks
Azure Front Door	Load balancers
Azure	PaaS
web-vitals	JavaScript libraries, RUM
HSTS	Security
DigiCert	SSL/TLS certificate authorities

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
es.linkedin.com	A	IPv4 address	13.107.246.45
es.linkedin.com	A	IPv4 address	13.107.213.45
es.linkedin.com	AAAA	IPv6 address	2620:1ec:bdf::45
es.linkedin.com	AAAA	IPv6 address	2620:1ec:46::45
es.linkedin.com	CNAME	Canonical name	cctld.linkedin.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.