Vulnerability Scan Result

Target:

https://www.glspaketti.fi/

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

Submitted: Nov 04, 2025 from TG

Public Scan

Scan mode: Passive (non-intrusive)

Summary

high

Info

Low

Medium

High

Critical

Screenshot

Screenshot could not be taken.

Title:	GLS Finland Shop
Description:	No description found

IP Information

ip_address	172.104.157.157
country	DE
network_name	Akamai Technologies Inc
asn	AS63949

Open Ports

22/tcp	ssh	OpenSSH 8
80/tcp	http	Apache httpd -
443/tcp	https	Apache httpd -

Web Technologies

Software / Version	Category
Apache HTTP Server	Web servers
Magento	Ecommerce
MySQL	Databases
PHP	Programming languages
React	JavaScript frameworks
styled-components 5.3.3	JavaScript frameworks, Development
HSTS	Security

Web Application Vulnerabilities

Evidence

URL	Method	Summary
https://www.glspaketti.fi/?canary=svumpvlydj	TRACE	We injected a random query parameter inside a HTTP TRACE request. The server responded with a 200 OK HTTP status code and we found the random value reflected in the body of the response.

Vulnerability description

We have noticed that the webserver responded with a 200 OK HTTP status when a TRACE/TRACK HTTP request was sent. Originally intended for debugging purposes, these methods respond to requests by echoing back the contents of the request received.

Risk description

The only risk this might present nowadays is revealing HTTP headers that have been appended by intermediate proxy servers on the way to the destination. This can present a danger if any of those headers contain sensitive information like authentication information, secret keys.

Recommendation

Generally, it is good practice to disable unused functionality to minimize your attack surface. We recommend that you disable unused HTTP methods, or even better, allow only the ones that you know are used. This can be done using your webserver configuration.

Classification

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

Evidence

Software / Version	Category
Apache HTTP Server	Web servers
Magento	Ecommerce
MySQL	Databases
PHP	Programming languages
React	JavaScript frameworks
styled-components 5.3.3	JavaScript frameworks, Development
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://www.glspaketti.fi/	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

URL
Missing: https://www.glspaketti.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	Summary
https://www.glspaketti.fi/	OPTIONS	We did a HTTP OPTIONS request. The server responded with a 200 status code and the header: `Allow: GET,POST,OPTIONS,HEAD,TRACE` 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

Infrastructure Vulnerabilities

Evidence

CVE	CVSS	EPSS Score	EPSS Percentile	CISA KEV	Summary
CVE-2023-38408	9.8	0.65917	0.98445	No	The PKCS#11 feature in ssh-agent in OpenSSH before 9.3p2 has an insufficiently trustworthy search path, leading to remote code execution if an agent is forwarded to an attacker-controlled system. (Code in /usr/lib is not necessarily safe for loading into ssh-agent.) NOTE: this issue exists because of an incomplete fix for CVE-2016-10009.
CVE-2019-16905	7.8	0.00093	0.26997	No	OpenSSH 7.7 through 7.9 and 8.x before 8.1, when compiled with an experimental key type, has a pre-authentication integer overflow if a client or server is configured to use a crafted XMSS key. This leads to memory corruption and local code execution because of an error in the XMSS key parsing algorithm. NOTE: the XMSS implementation is considered experimental in all released OpenSSH versions, and there is no supported way to enable it when building portable OpenSSH.
CVE-2020-15778	7.4	0.64132	0.98359	No	scp in OpenSSH through 8.3p1 allows command injection in the scp.c toremote function, as demonstrated by backtick characters in the destination argument. NOTE: the vendor reportedly has stated that they intentionally omit validation of "anomalous argument transfers" because that could "stand a great chance of breaking existing workflows."
CVE-2021-41617	7	0.00469	0.63835	No	sshd in OpenSSH 6.2 through 8.x before 8.8, when certain non-default configurations are used, allows privilege escalation because supplemental groups are not initialized as expected. Helper programs for AuthorizedKeysCommand and AuthorizedPrincipalsCommand may run with privileges associated with group memberships of the sshd process, if the configuration specifies running the command as a different user.
CVE-2025-26465	6.8	0.48988	0.97647	No	A vulnerability was found in OpenSSH when the VerifyHostKeyDNS option is enabled. A machine-in-the-middle attack can be performed by a malicious machine impersonating a legit server. This issue occurs due to how OpenSSH mishandles error codes in specific conditions when verifying the host key. For an attack to be considered successful, the attacker needs to manage to exhaust the client's memory resource first, turning the attack complexity high.

Vulnerability description

Vulnerabilities found for Openssh 8.0

Risk description

These vulnerabilities expose the affected applications to the risk of unauthorized access to confidential data and possibly to denial of service attacks. An attacker could search for an appropriate exploit (or create one) for any of these vulnerabilities and use it to attack the system. Notes: - The vulnerabilities are identified based on the server's version.; - Only the first 5 vulnerabilities with the highest risk are shown for each port.; 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

We recommend you to upgrade the affected software to the latest version in order to eliminate the risks imposed by these vulnerabilities.

Evidence

Domain Queried	DNS Record Type	Description	Value
www.glspaketti.fi	A	IPv4 address	172.104.157.157
www.glspaketti.fi	NS	Name server	dns1.louhi.net
www.glspaketti.fi	NS	Name server	dns3.louhi.fi
www.glspaketti.fi	NS	Name server	dns2.louhi.net
www.glspaketti.fi	MX	Mail server	10 glspaketti.fi
www.glspaketti.fi	SOA	Start of Authority	dns1.louhi.net. hostmaster.louhi.net. 2016031813 3600 600 86400 3600
www.glspaketti.fi	SPF	Sender Policy Framework	"v=spf1 include:sparkpostmail.com ~all"
www.glspaketti.fi	CNAME	Canonical name	glspaketti.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
Magento	Ecommerce
MySQL	Databases
PHP	Programming languages
Apache HTTP Server	Web servers
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.