Vulnerability Scan Result
| Title: | itexa ag – Home |
| Description: | Ihr IT-Dienstleister und Cloud-Spezialist aus der Region. Tel. 081 330 20 10. |
| ip_address | 149.126.4.62 |
| country | CH  |
| network_name | cyon AG |
| asn | AS47302 |
21/tcp | ftp | Pure-FTPd - |
22/tcp | ssh | OpenSSH 8 |
25/tcp | nagios-nsca | Nagios NSCA - |
80/tcp | http | - - |
110/tcp | pop3 | Dovecot pop3d - |
143/tcp | imap | Dovecot imapd - |
443/tcp | https | - - |
465/tcp | nagios-nsca | Nagios NSCA - |
587/tcp | nagios-nsca | Nagios NSCA - |
993/tcp | imaps | - - |
995/tcp | pop3s | - - |
3306/tcp | mysql | MySQL 5.5.5-10.6.25-MariaDB-cll-lve-log |
| Software / Version | Category |
|---|---|
| UIKit | UI frameworks |
| HTTP/3 | Miscellaneous |
| PHP | Programming languages |
| Joomla | CMS |
Web Application Vulnerabilities
Evidence
| Software / Version | Category |
|---|---|
| UIKit | UI frameworks |
| HTTP/3 | Miscellaneous |
| PHP | Programming languages |
| Joomla | CMS |
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.
Classification
| CWE | CWE-200 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
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://itexa.ch/ | 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-1021 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Evidence |
|---|---|
| https://itexa.ch/ | 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
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.
Classification
| CWE | CWE-1188 |
| 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.67238 | 0.98583 | 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.00271 | 0.50573 | 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-2026-35385 | 7.5 | 0.00059 | 0.18399 | No | In OpenSSH before 10.3, a file downloaded by scp may be installed setuid or setgid, an outcome contrary to some users' expectations, if the download is performed as root with -O (legacy scp protocol) and without -p (preserve mode). |
| CVE-2020-15778 | 7.4 | 0.64277 | 0.98464 | 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.00274 | 0.50847 | 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. |
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
We managed to detect a publicly accessible SSH service. Starting Nmap ( https://nmap.org ) at 2026-05-15 05:59 EEST Nmap scan report for itexa.ch (149.126.4.62) Host is up (0.017s latency). rDNS record for 149.126.4.62: s053.cyon.net
PORT STATE SERVICE VERSION 22/tcp open ssh OpenSSH 8.0 (protocol 2.0) | ssh-auth-methods: | Supported authentication methods: | publickey |_ password
Service detection performed. Please report any incorrect results at https://nmap.org/submit/ . Nmap done: 1 IP address (1 host up) scanned in 0.73 seconds
Vulnerability description
We found that the SSH service with username/password authentication is publicly accessible. Network administrators often use remote administration protocols to control devices like switches, routers, and other essential systems. However, allowing these services to be accessible via the Internet can increase security risks, creating potential opportunities for attacks on the organization.
Risk description
Exposing this service online with username/password authentication can enable attackers to launch authentication attacks, like guessing login credentials, and potentially gaining unauthorized access. Vulnerabilities, such as unpatched software, protocol flaws, or backdoors could also be exploited. An example is the CVE-2024-3094 (XZ Utils Backdoor) vulnerability.
Recommendation
We recommend turning off SSH with username/password authentication access over the Internet and instead using a Virtual Private Network (VPN) that mandates two-factor authentication (2FA). If the SSH service is essential for business purposes, we recommend limiting access only from designated IP addresses using a firewall. Furthermore, it is advisable to utilize SSH Public Key Authentication since it employs a key pair to verify the identity of a user or process.
Evidence
We managed to detect a publicly accessible MySQL service. PORT STATE SERVICE VERSION 3306/tcp open mysql MySQL 5.5.5-10.6.25-MariaDB-cll-lve-log
Vulnerability description
We identified that the MySQL service is publicly accessible. MySQL serves as a common database for numerous web applications and services for data storage, making it a potential prime target for determined attackers.
Risk description
The risk exists that an attacker exploits this issue by launching a password-based attack on the MySQL service. Furthermore, they could exploit zero-day vulnerabilities to obtain remote access to the MySQL database server, thereby gaining complete control over its operating system and associated services. Such an attack could lead to the exposure of confidential or sensitive information.
Recommendation
We recommend turning off public Internet access to MySQL and opting for a Virtual Private Network (VPN) that enforces two-factor authentication (2FA). Avoid enabling direct user authentication to the MySQL service via the Internet, as this could enable attackers to engage in password-guessing and potentially initiate attacks leading to complete control. However, if the MySQL service is required to be directly accessible over the Internet, we recommend reconfiguring it to be accessible only from known IP addresses.
Evidence
We managed to detect a publicly accessible File Transfer Protocol (FTP) service. PORT STATE SERVICE VERSION 21/tcp open ftp Pure-FTPd
Vulnerability description
We found that the File Transfer Protocol (FTP) service is publicly accessible. The FTP enables client systems to connect to upload and download files. Nonetheless, FTP lacks encryption for the data exchanged between the server and the client, leaving all transferred data exposed in plaintext.
Risk description
Exposing this service online can enable attackers to execute man-in-the-middle attacks, capturing sensitive user credentials and the contents of files because FTP operates without encryption. The entirety of the communication between the client and the server remains unsecured in plaintext. This acquired information could further facilitate additional attacks within the network.
Recommendation
We recommend turning off FTP access over the Internet and instead using a Virtual Private Network (VPN) that mandates two-factor authentication (2FA). If the FTP service is essential for business purposes, we recommend limiting access only from designated IP addresses using a firewall. Furthermore, utilizing SFTP (Secure File Transfer Protocol) is recommended as this protocol employs encryption to secure data transfers.
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| _dmarc.itexa.ch | TXT | Text record | "v=DMARC1; p=none; ruf=mailto:alert@itexa.ch; rua=mailto:alert@itexa.ch" |
Vulnerability description
We found that the DMARC record for the domain is not configured with sp policy, meaning that no policy is enforced for subdomains. When a DMARC record does not include a subdomain policy (sp directive), subdomains are not explicitly covered by the main domain's DMARC policy. This means that emails sent from subdomains (e.g., sub.example.com) may not be subject to the same DMARC enforcement as the main domain (example.com). As a result, attackers could potentially spoof emails from subdomains without being blocked or flagged, even if the main domain has a strict DMARC policy.
Risk description
Without a subdomain policy (sp directive) in the DMARC record, subdomains are not protected by the same DMARC enforcement as the main domain, leaving them vulnerable to spoofing attacks. This inconsistency can be exploited by attackers to send phishing emails from subdomains, undermining the organization’s overall email security.
Recommendation
To mitigate the risk, we recommend configuring the DMARC record with a subdomain policy by adding the sp=reject or sp=quarantine directive. This will extend DMARC enforcement to all subdomains, preventing spoofing attempts and maintaining consistent security across both the main domain and its subdomains.
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| _dmarc.itexa.ch | TXT | Text record | "v=DMARC1; p=none; ruf=mailto:alert@itexa.ch; rua=mailto:alert@itexa.ch" |
Vulnerability description
We found that the target uses p=none in the DMARC policy. The DMARC policy set to p=none means that the domain owner is not taking any action on emails that fail DMARC validation. This configuration effectively disables enforcement, allowing potentially spoofed or fraudulent emails to be delivered without any additional scrutiny.
Risk description
Emails that fail DMARC checks are still delivered to recipients. This leaves the domain highly vulnerable to email spoofing and phishing attacks, as malicious actors can impersonate the domain without facing any consequences from DMARC enforcement.
Recommendation
We recommend changing the DMARC policy to p=quarantine or, ideally, p=reject to actively block or quarantine emails that fail DMARC validation. This will enhance the security of your domain against spoofing and phishing attacks by ensuring that only legitimate emails are delivered.
Evidence
| DKIM selector | Key type | Key size | Value |
|---|---|---|---|
| default | rsa | 1470 | "v=DKIM1; k=rsa;" "s=email;p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAx60KYqKCE1jI5le6Ivn/nwqv2EpmQVUw7fA41L33OKpJSzWryOPCen7c6r6xBESjNOmBmja+ZcssMXLpTrOJWT+w06XxHkIblv06ZLbSWWa+iWIHbfUkFn1I51d3pFjWJqpAypB5NUs5Wcj+PpsaWFNSe6eUiMoLMXQtNBAS/od8UrK7Fwo4zr0b3N/b6ZCWxKXmmKLkz" "/laDaR87husP3s4ufXjD4qHAPTaxD4oRhVSm4ZRKxfVv/wkl7jVtjPzrsXYUlOAU49fTQ+9er1Tc2b2z3LbVrh95PGLA+jqw6cfe7wwKxTTE+o6V+GujzkyUW7W2SzYNSrLa/pUSTzr8QIDAQAB" |
Vulnerability description
We found that the DKIM record uses common selectors. The use of common DKIM selectors such as default, test, dkim, or mail may indicate a lack of proper customization or key management. Attackers often target domains using such selectors because they suggest that the domain is relying on default configurations, which could be less secure and easier to exploit. This can increase the risk of DKIM key exposure or misuse.
Risk description
Using a common DKIM selector makes it easier for attackers to predict and exploit email authentication weaknesses. Attackers may attempt to find corresponding DKIM keys or improperly managed records associated with common selectors. If a common selector is coupled with a weak key length or poor key management practices, it significantly increases the likelihood of email spoofing and phishing attacks.
Recommendation
We recommend using unique, customized selectors for each DKIM key to make it more difficult for attackers to predict and target the domain's DKIM records. Regularly rotate selectors and associated keys to further strengthen the security of your domain's email authentication infrastructure.
Evidence
We found insecure DNS cookie usage on the following nameservers: ns1.itexacloud.ch, ns2.itexacloud.ch, ns3.itexacloud.ch
Vulnerability description
We found that the server does not implement DNS Cookies or uses them insecurely. DNS Cookies help prevent DNS-based attacks, such as spoofing and amplification attacks.
Risk description
The risk exists because without DNS Cookies, the server is vulnerable to DNS spoofing and amplification attacks. Attackers can manipulate responses or use the server in distributed denial-of-service (DDoS) attacks, compromising network availability and security.
Recommendation
We recommend enabling DNS Cookies to prevent spoofed DNS responses. Ensure proper cookie validation is implemented to mitigate DNS amplification attacks. Regularly update DNS servers to support the latest DNS security features.
Evidence
We managed to detect that mariadb has reached the End-of-Life (EOL).
Version detected: 5.5.5-10.6.25-mariadb-cll-lve-log End-of-life date: 2020-04-11 Latest version for the cycle: 5.5.68 This release cycle (5.5) does have long-term-support (LTS). The cycle was released on 2012-04-11 and its latest release date was 2020-05-06.
Risk description
Using end-of-life (EOL) software poses significant security risks for organizations. EOL software no longer receives updates, including critical security patches. This creates a vulnerability landscape where known and potentially new security flaws remain unaddressed, making the software an attractive target for malicious actors. Attackers can exploit these vulnerabilities to gain unauthorized access, disrupt services, or steal sensitive data. Moreover, without updates, compatibility issues arise with newer technologies, leading to operational inefficiencies and increased potential for system failures. Additionally, regulatory and compliance risks accompany the use of EOL software. Many industries have strict data protection regulations that require up-to-date software to ensure the highest security standards. Non-compliance can result in hefty fines and legal consequences. Organizations also risk damaging their reputation if a breach occurs due to outdated software, eroding customer trust and potentially leading to a loss of business. Therefore, continuing to use EOL software undermines both security posture and business integrity, necessitating timely upgrades and proactive risk management strategies.
Recommendation
To mitigate the risks associated with end-of-life (EOL) software, it's crucial to take proactive steps. Start by identifying any EOL software currently in use within your organization. Once identified, prioritize upgrading or replacing these applications with supported versions that receive regular updates and security patches. This not only helps close security gaps but also ensures better compatibility with newer technologies, enhancing overall system efficiency and reliability.Additionally, develop a comprehensive software lifecycle management plan. This plan should include regular audits to identify upcoming EOL dates and a schedule for timely updates or replacements. Train your IT staff and users about the importance of keeping software up to date and the risks associated with using outdated versions. By maintaining a proactive approach to software management, you can significantly reduce security risks, ensure compliance with industry regulations, and protect your organization's reputation and customer trust.
Evidence
| Software / Version | Category |
|---|---|
| Joomla | CMS |
| PHP | Programming languages |
| UIKit | UI frameworks |
| HTTP/3 | 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.
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| itexa.ch | A | IPv4 address | 149.126.4.62 |
| itexa.ch | NS | Name server | ns1.itexacloud.ch |
| itexa.ch | NS | Name server | ns2.itexacloud.ch |
| itexa.ch | NS | Name server | ns3.itexacloud.ch |
| itexa.ch | MX | Mail server | 0 itexa-ch.mail.protection.outlook.com |
| itexa.ch | SOA | Start of Authority | ns1.itexacloud.ch. info.itexa.ch. 2026031097 7200 120 2419200 10800 |
| itexa.ch | TXT | Text record | "vmflw8xz7c64ckhfz6mr6kkntwdkzmqg" |
| itexa.ch | TXT | Text record | "swisssign-check=VRJK86z3h-T_qdxvxNIKs834xQo" |
| itexa.ch | TXT | Text record | "swisssign-check=bwkDOGy_GAgHT3RkgP4nY6urEXg" |
| itexa.ch | SPF | Sender Policy Framework | "v=spf1 a:secmail.itexacloud.ch a:mailprotect1.itexacloud.ch a:mailprotect2.itexacloud.ch ip4:213.221.234.75 include:spf.protection.cyon.net include:spf.protection.outlook.com -all" |
| _dmarc.itexa.ch | TXT | Text record | "v=DMARC1; p=none; ruf=mailto:alert@itexa.ch; rua=mailto:alert@itexa.ch" |
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
| Operating System | Accuracy |
|---|---|
| Linux 2.6.32 | 88% |
Vulnerability description
OS Detection
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| itexa.ch | SPF | Sender Policy Framework | "v=spf1 a:secmail.itexacloud.ch a:mailprotect1.itexacloud.ch a:mailprotect2.itexacloud.ch ip4:213.221.234.75 include:spf.protection.cyon.net include:spf.protection.outlook.com -all" |
Evidence
| DKIM selector | Key type | Key size | Value |
|---|---|---|---|
| default | rsa | 1470 | "v=DKIM1; k=rsa;" "s=email;p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAx60KYqKCE1jI5le6Ivn/nwqv2EpmQVUw7fA41L33OKpJSzWryOPCen7c6r6xBESjNOmBmja+ZcssMXLpTrOJWT+w06XxHkIblv06ZLbSWWa+iWIHbfUkFn1I51d3pFjWJqpAypB5NUs5Wcj+PpsaWFNSe6eUiMoLMXQtNBAS/od8UrK7Fwo4zr0b3N/b6ZCWxKXmmKLkz" "/laDaR87husP3s4ufXjD4qHAPTaxD4oRhVSm4ZRKxfVv/wkl7jVtjPzrsXYUlOAU49fTQ+9er1Tc2b2z3LbVrh95PGLA+jqw6cfe7wwKxTTE+o6V+GujzkyUW7W2SzYNSrLa/pUSTzr8QIDAQAB" |
| selector1 | rsa | 1296 | "v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC2l9ZbDhyJDPFrP6F5PL87nSuQlcuN3YbYGoaa5IL3tVEuKggaop7g63Okbge9NVV1SV0qaFlbWEfHKOE1wT1kr8qK+P7sq14l84L4q7GZ2H0Kfzu55o/oR1YNjYduYHl30xRT103UL8TVLCnhkI5pZLWaZqROvPPIvzFJP9c5/wIDAQAB; n=1024,1453278018,1" "469002818" |