Vulnerability Scan Result

Target:

https://www.iltalehti.fi/

Scanned target: https://www.iltalehti.fi/

Submitted: Nov 04, 2025 from MN

Public Scan

Scan mode: Passive (non-intrusive)

Summary

low

Info

Low

Medium

High

Critical

Screenshot

Screenshot could not be taken.

Title:	Iltalehti \| IL - Suomen suurin uutispalvelu
Description:	Uutiset, urheilu, viihde, talous, sää, terveys, ruoka, matkailu, autot ja tyyli – Iltalehti, kaikki tuoreet uutiset yhdestä osoitteesta kellon ympäri!

IP Information

ip_address	3.167.227.88
country	US
network_name	-
asn	-

ip_address	3.167.227.65
country	US
network_name	-
asn	-

ip_address	3.167.227.29
country	US
network_name	-
asn	-

ip_address	3.167.227.17
country	US
network_name	-
asn	-

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
core-js 3.46.0	JavaScript libraries
Open Graph	Miscellaneous
Prebid 9.18.0	Advertising
PWA	Miscellaneous
Webpack	Miscellaneous
Google Tag Manager	Tag managers
HSTS	Security

Web Application Vulnerabilities

Evidence

URL Evidence

URL	Evidence
https://www.iltalehti.fi/	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'. 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'. default-src: The default-src directive should be set as a fall-back when other restrictions have not been specified. frame-ancestors: Allow only resources downloaded over HTTPS. 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://www.iltalehti.fi/

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'. 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'. default-src: The default-src directive should be set as a fall-back when other restrictions have not been specified. frame-ancestors: Allow only resources downloaded over HTTPS. 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	Evidence
https://www.iltalehti.fi/	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
https://www.iltalehti.fi/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
Amazon Web Services	PaaS
AWS Certificate Manager	SSL/TLS certificate authorities
Amazon CloudFront	CDN
core-js 3.46.0	JavaScript libraries
Open Graph	Miscellaneous
Prebid 9.18.0	Advertising
PWA	Miscellaneous
Webpack	Miscellaneous
Google Tag Manager	Tag managers
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
Missing: https://www.iltalehti.fi/.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.

Evidence

URL	Method	Parameters	Evidence
https://www.iltalehti.fi/ulkomaat/a/8d0e8d49-bc58-4d07-894b-7f0789fd3450	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: anne.salminen@iltalehti.fi

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	Method	Parameters	Evidence
https://www.iltalehti.fi/info/palaute	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	The following form allows file upload: ` * Palautteen syy * Palaute Asiaan liittyvÃ¤t kuvat tai videot: Liitteiden yhteiskoko max. 50 MB LisÃ¤Ã¤ liite TÃ¤ytÃ¤ yhteystiedot, jos haluat, ettÃ¤ vastaamme viestiisi. KÃ¤sittelemme yhteystiedot luottamuksellisesti. Nimi SÃ¤hkÃ¶postiosoite <input class="input" type="email" name="email" value=&qu... (truncated)

Vulnerability description

We found the file upload functionality in the web application. While this is not a security issue by itself, it may represent a first step in an attack involving storing data on the target server.

Risk description

The risk is that an attacker might use the file upload functionality for path traversal, persistent XSS, transmission of malware or denial of service, if such vulnerabilities are present.

Recommendation

Use a server-generated filename, inspect the content of uploaded files, enforce a whitelist of non-executable file types and a size limit, and reject attempts to upload archive formats such as ZIP.

Classification

CWE	CWE-434
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Infrastructure Vulnerabilities

Evidence

Domain Queried	DNS Record Type	Description	Value
www.iltalehti.fi	A	IPv4 address	3.167.227.17
www.iltalehti.fi	A	IPv4 address	3.167.227.65
www.iltalehti.fi	A	IPv4 address	3.167.227.29
www.iltalehti.fi	A	IPv4 address	3.167.227.88
www.iltalehti.fi	NS	Name server	ns-1394.awsdns-46.org
www.iltalehti.fi	NS	Name server	ns-178.awsdns-22.com
www.iltalehti.fi	NS	Name server	ns-1968.awsdns-54.co.uk
www.iltalehti.fi	NS	Name server	ns-981.awsdns-58.net
www.iltalehti.fi	SOA	Start of Authority	ns-178.awsdns-22.com. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400
www.iltalehti.fi	AAAA	IPv6 address	2600:9000:27e6:dc00:3:3f58:f680:93a1
www.iltalehti.fi	AAAA	IPv6 address	2600:9000:27e6:a400:3:3f58:f680:93a1
www.iltalehti.fi	AAAA	IPv6 address	2600:9000:27e6:d600:3:3f58:f680:93a1
www.iltalehti.fi	AAAA	IPv6 address	2600:9000:27e6:5c00:3:3f58:f680:93a1
www.iltalehti.fi	AAAA	IPv6 address	2600:9000:27e6:1600:3:3f58:f680:93a1
www.iltalehti.fi	AAAA	IPv6 address	2600:9000:27e6:1200:3:3f58:f680:93a1
www.iltalehti.fi	AAAA	IPv6 address	2600:9000:27e6:4800:3:3f58:f680:93a1
www.iltalehti.fi	AAAA	IPv6 address	2600:9000:27e6:a800:3:3f58:f680:93a1
www.iltalehti.fi	CNAME	Canonical name	www-prod-iltalehti-fi.il.fi

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
Amazon Web Services	PaaS
Google Tag Manager	Tag managers
HSTS	Security
Amazon CloudFront	CDN
AWS Certificate Manager	SSL/TLS certificate authorities
PWA	Miscellaneous
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.