Vulnerability Scan Result
| Title: | OLXTOTO - Situs Game Online Seru dengan Pilihan Game Terlengkap |
| Description: | Di OLXTOTO, kamu bisa menemukan beragam game online seru dengan tampilan yang nyaman dan modern. Semua dirancang agar kamu bisa menikmati pengalaman bermain yang lebih asik setiap hari. Cocok untuk yang cari game dengan kualitas terbaik. |
| ip_address | 132.148.72.249 |
| country | US  |
| network_name | GoDaddy.com, LLC |
| asn | AS398101 |
21/tcp | ftp | Pure-FTPd - |
22/tcp | ssh | OpenSSH 8 |
25/tcp | smtp | - - |
53/tcp | domain | - - |
80/tcp | http | nginx - |
81/tcp | http | Apache httpd - |
110/tcp | pop3 | Dovecot pop3d - |
111/tcp | rpcbind | - - |
143/tcp | imap | Dovecot imapd - |
443/tcp | https | nginx - |
444/tcp | https | Apache httpd - |
465/tcp | smtp | Exim smtpd 4.99.1 |
587/tcp | smtp | Exim smtpd 4.99.1 |
993/tcp | imap | Dovecot imapd - |
995/tcp | pop3 | Dovecot pop3d - |
2078/tcp | https | cPanel httpd - |
2080/tcp | https | cPanel httpd - |
2082/tcp | http | - - |
2083/tcp | https | - - |
2086/tcp | http | - - |
2087/tcp | https | - - |
3306/tcp | mysql | MariaDB - |
No technologies could be detected.
Web Application Vulnerabilities
No vulnerabilities were found.
Infrastructure Vulnerabilities
Evidence
| CVE | CVSS | EPSS Score | EPSS Percentile | CISA KEV | Summary |
|---|---|---|---|---|---|
| CVE-2023-38408 | 9.8 | 0.69186 | 0.98594 | 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.00199 | 0.42005 | 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.60971 | 0.98245 | 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.00281 | 0.51095 | 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.64393 | 0.98394 | 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
We managed to detect a publicly accessible SSH service. Starting Nmap ( https://nmap.org ) at 2026-01-27 23:35 EET Nmap scan report for smithfieldal.com (132.148.72.249) Host is up (0.14s latency). rDNS record for 132.148.72.249: 249.72.148.132.host.secureserver.net
PORT STATE SERVICE VERSION 22/tcp open ssh OpenSSH 8.0 (protocol 2.0) | ssh-auth-methods: | Supported authentication methods: | publickey | gssapi-keyex | gssapi-with-mic |_ password
Service detection performed. Please report any incorrect results at https://nmap.org/submit/ . Nmap done: 1 IP address (1 host up) scanned in 2.07 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 MariaDB
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.smithfieldal.com | TXT | Text record | "v=DMARC1; p=quarantine; sp=reject; rua=mailto:dmarc@algsenior.com; aspf=s; adkim=s;" |
Vulnerability description
We found that the target uses p=quarantine in the DMARC policy. When a DMARC policy is set to p=quarantine, emails that fail DMARC validation are delivered but placed in the recipient’s spam or junk folder. Although it offers some protection, this policy is less strict than p=reject, which blocks such emails entirely.
Risk description
While emails failing DMARC validation are sent to the spam folder, users may still retrieve them from there, leading to a higher risk of phishing and spoofing attacks succeeding. Moreover, less strict enforcement may allow more fraudulent emails to reach user inboxes if misclassified.
Recommendation
We recommend considering moving to a stricter policy, such as p=reject, where emails that fail DMARC validation are completely rejected rather than delivered to spam folders. This reduces the risk of users interacting with potentially malicious emails.
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| _dmarc.smithfieldal.com | TXT | Text record | "v=DMARC1; p=quarantine; sp=reject; rua=mailto:dmarc@algsenior.com; aspf=s; adkim=s;" |
Vulnerability description
We found that the DMARC record for the domain is not configured with ruf tag. A missing ruf (forensic reporting) tag in a DMARC record indicates that the domain owner has not enabled the collection of detailed failure reports. Forensic reports provide valuable insights into specific instances where emails fail DMARC authentication. Without the ruf tag, the domain administrator loses the ability to receive and analyze these reports, making it difficult to investigate individual email failures or identify targeted phishing or spoofing attacks that may be exploiting weaknesses in the email authentication setup.
Risk description
Without forensic reports (ruf), domain owners have limited visibility into the specifics of failed DMARC validation. This means potential malicious activity, such as email spoofing or phishing attempts, might go unnoticed until they result in more significant security breaches or reputational damage. Forensic reports allow for quick response to email abuses by providing detailed information about the failure, including the header information of the emails involved. The absence of this data hampers an organization's ability to identify and mitigate threats targeting its domain, increasing the risk of ongoing spoofing and fraud.
Recommendation
We recommend configuring the ruf tag in the DMARC record. This tag specifies where forensic reports should be sent, providing the domain owner with detailed data on DMARC validation failures. Forensic reports allow administrators to analyze why certain emails failed authentication, making it easier to fine-tune DMARC policies or address potential vulnerabilities. Ensure that the ruf email address belongs to a secure and trusted location capable of handling sensitive email data.
Evidence
We found insecure DNS cookie usage on the following nameservers: ns49.domaincontrol.com, ns50.domaincontrol.com
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 a publicly accessible Post Office Protocol (POP3) service. Starting Nmap ( https://nmap.org ) at 2026-01-27 23:35 EET Nmap scan report for smithfieldal.com (132.148.72.249) Host is up (0.14s latency). rDNS record for 132.148.72.249: 249.72.148.132.host.secureserver.net
PORT STATE SERVICE VERSION 995/tcp open ssl/pop3 Dovecot pop3d |_pop3-capabilities: UIDL USER SASL(PLAIN LOGIN) RESP-CODES AUTH-RESP-CODE PIPELINING CAPA TOP
Service detection performed. Please report any incorrect results at https://nmap.org/submit/ . Nmap done: 1 IP address (1 host up) scanned in 7.86 seconds
Vulnerability description
We found that the Post Office Protocol (POP3) service is publicly accessible and doesn’t include STARTTLS capability. Email clients use the Post Office Protocol (POP) to download emails for user accounts. Some POP servers are initially set up to operate over an unsecured protocol. When email clients download email content through this plaintext protocol, it can pose a substantial risk to the organization's network, especially depending on which user account is set to receive the emails.
Risk description
Exposing this service online can enable attackers to conduct man-in-the-middle attacks, thereby gaining access to sensitive user credentials and the contents of emails. Given that POP3 operates via a plaintext protocol, the entirety of the data exchanged between the client and server is left unencrypted. This critical information could then be leveraged in further attacks on the organization's network.
Recommendation
We recommend turning off POP3 access over the Internet and instead using a Virtual Private Network (VPN) that mandates two-factor authentication (2FA). If the POP3 service is essential for business purposes, we recommend limiting access only from designated IP addresses using a firewall. Furthermore, activating STARTTLS capability (switching the connection to a secure communication) or utilizing Secure POP3 (POP3S) is recommended, as this protocol employs encryption.
Evidence
| Software / Version | Category |
|---|---|
| cPanel | Hosting panels |
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 |
|---|---|
| WordPress 6.9 | CMS, Blogs |
| MySQL | Databases |
| PHP | Programming languages |
| ZURB Foundation | UI frameworks |
| Nginx | Web servers, Reverse proxies |
| FitVids.JS 1.2 | Widgets, Video players |
| Animate.css | UI frameworks |
| Astra 4.12.1 | WordPress themes |
| Beaver Builder | WordPress plugins |
| All in One SEO Pack 4.9.3 | SEO, WordPress plugins |
| Site Kit 1.171.0 | Analytics, WordPress plugins |
| UserWay | Accessibility |
| Typekit | Font scripts |
| jQuery Migrate 3.4.1 | JavaScript libraries |
| jQuery | JavaScript libraries |
| imagesLoaded 2.10.0.5 | JavaScript libraries |
| Google Tag Manager | Tag managers |
| Google Hosted Libraries | CDN |
| Google Font API | Font scripts |
| Google Analytics | Analytics |
| Adobe Fonts | Font scripts |
| Cloudflare | CDN |
| cdnjs | CDN |
| RSS | 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
| DKIM selector | Key type | Key size | Value |
|---|---|---|---|
| selector1 | rsa | 1422 | "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAtksIHeAbyfK7n0D68PqoXNV+nV3HQar9MIsmjeXoA/FbXuwcrjz9NsUB2HQp7mIO+gW0BqvpENiZwTob2U+/sb3OrKneT4vWEdP0P1/ashMNvoPhZGkykmyDCetvyN/Q1CLfiBGMa6yQpJ+IPf2VLrQPOR3mDRMiTjIyNYeGLmHY0tvoYnxeRwwWsA6eGSVvB" "NPBxwxVZPno5OyNNgZcsi2xwF5fjaQUlr3ZJMIXpFRTueyB1qTEOXVcp5fLezwskY8wTd4Nie0RwMFgsz2xgiBO/bvYAyHj2ickbNnCtKOjrlfKC/xLM8545Jz1Z70EMUkM7NVc6jss/W34mb4iQQIDAQAB;" |
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| smithfieldal.com | A | IPv4 address | 132.148.72.249 |
| smithfieldal.com | NS | Name server | ns49.domaincontrol.com |
| smithfieldal.com | NS | Name server | ns50.domaincontrol.com |
| smithfieldal.com | MX | Mail server | 0 smithfieldal-com.mail.protection.outlook.com |
| smithfieldal.com | SOA | Start of Authority | ns49.domaincontrol.com. dns.jomax.net. 2025120800 28800 7200 604800 600 |
| smithfieldal.com | TXT | Text record | "MS=ms15832778" |
| smithfieldal.com | TXT | Text record | "facebook-domain-verification=7cipl6b8wnwwpk6swxng5l1pjr5p7n" |
| smithfieldal.com | SPF | Sender Policy Framework | "v=spf1 include:spf.protection.outlook.com -all" |
| _dmarc.smithfieldal.com | TXT | Text record | "v=DMARC1; p=quarantine; sp=reject; rua=mailto:dmarc@algsenior.com; aspf=s; adkim=s;" |
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 5.1 | 97% |
Vulnerability description
OS Detection
Evidence
| Software / Version | Category |
|---|---|
| WordPress 6.9 | CMS, Blogs |
| MySQL | Databases |
| PHP | Programming languages |
| ZURB Foundation | UI frameworks |
| Nginx | Web servers, Reverse proxies |
| FitVids.JS 1.2 | Widgets, Video players |
| Animate.css | UI frameworks |
| Astra 4.12.1 | WordPress themes |
| Beaver Builder | WordPress plugins |
| All in One SEO Pack 4.9.3 | SEO, WordPress plugins |
| Site Kit 1.171.0 | Analytics, WordPress plugins |
| UserWay | Accessibility |
| Typekit | Font scripts |
| jQuery Migrate 3.4.1 | JavaScript libraries |
| jQuery | JavaScript libraries |
| imagesLoaded 2.10.0.5 | JavaScript libraries |
| Google Tag Manager | Tag managers |
| Google Hosted Libraries | CDN |
| Google Font API | Font scripts |
| Google Analytics | Analytics |
| Adobe Fonts | Font scripts |
| Cloudflare | CDN |
| cdnjs | CDN |
| RSS | 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 |
|---|---|---|---|
| smithfieldal.com | SPF | Sender Policy Framework | "v=spf1 include:spf.protection.outlook.com -all" |
Evidence
| Software / Version | Category |
|---|---|
| WordPress 6.9 | CMS, Blogs |
| MySQL | Databases |
| PHP | Programming languages |
| ZURB Foundation | UI frameworks |
| Nginx | Web servers, Reverse proxies |
| FitVids.JS 1.2 | Widgets, Video players |
| Animate.css | UI frameworks |
| Astra 4.12.1 | WordPress themes |
| Beaver Builder | WordPress plugins |
| All in One SEO Pack 4.9.3 | SEO, WordPress plugins |
| Site Kit 1.171.0 | Analytics, WordPress plugins |
| imagesLoaded 2.10.0.5 | JavaScript libraries |
| Google Hosted Libraries | CDN |
| Google Font API | Font scripts |
| UserWay | Accessibility |
| Typekit | Font scripts |
| jQuery Migrate 3.4.1 | JavaScript libraries |
| jQuery | JavaScript libraries |
| Google Tag Manager | Tag managers |
| Google Analytics | Analytics |
| Adobe Fonts | Font scripts |
| Cloudflare | CDN |
| cdnjs | CDN |
| RSS | 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
| Software / Version | Category |
|---|---|
| Basic | 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 |
|---|---|
| Basic | 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.