Vulnerability Scan Result
| Title: | Request Rejected |
| Description: | No description found |
| ip_address | 103.107.245.249 |
| country | ID  |
| network_name | Diskominfo PROV JAWA Tengah |
| asn | AS131724 |
80/tcp | http | F5 BIG-IP load balancer http proxy - |
443/tcp | https | - - |
| Software / Version | Category |
|---|---|
| DigiCert | SSL/TLS certificate authorities |
Web Application Vulnerabilities
Evidence
| URL | Cookie Name | Evidence |
|---|---|---|
| https://bpusdataru-probolo.jatengprov.go.id/ | TS1e6c9646029, TS1e6c9646078, TS133faa19027 | Set-Cookie: TS1e6c9646029=0817188341ab280011b21f78e80540f92e7566de20af646da3f8ae6c9c41a79d74bdef21aa7dd89ba7f74e9e65862c0d Set-Cookie: TS1e6c9646078=0817188341ab2000b24fa7a2768d55e883d05d70079410a48dbad7f4e5151248203ba5051f0b08aa0867eef6ef18b0018885ee50ff5696a38f5f2ab0fdc2c53847958d73aed9a887c81ae4bb823015fa00a4c6ee31bbca2d6907b4ef3034333274a20fd09ee165f30b2850e9fac6ed5d08124e80d0594f7ad4f21ca4acd9c4098d8105acaad12732ce34c62e05e91de45f16ca9771c38a034992ca960fde8e6f7b05f993366265811989f1228d05b139ffebb7bbea5e2a0f5f7e3c74c8ad5f94a0715cf61b1109fc8c593c31ed62788490381d16504216c6b25823f231e2ad0b43a45338bec4d9ad9b75cdcabd7fa00a30d53569136b373e0024e4475a3becad4ec293d20204c20d107f3cc75519c88bbb23058f893e0febf16d3ef7cb25e1abc5087bab147e6c01100526e101e433ddb5bb873e3c72afd2a718eed7e8856029ba380674f8b468ee80d2b31860eceb8ee0c9fd9b56aa83910092a94740c698aa942565074d6a1dc6256d5da2d99a0d79812cccaa7604ef6c6184ee557933560e9c2d1c000993937f3d39858cd2d543edf8f47912123091ec9517816620c2b83b15c7dca4614f042ce62ad6c5904c7d76096483ab42381fabf5f3afaa328499c81b0b58d10306bce3a91d77be932ef0bcaf8ee6534cba5207f6d99cb25fce0d8b Set-Cookie: TS133faa19027=0817188341ab2000e70394c92ada64baec467d68489d0c769d239ef56307ad267940c0c6e4e5901d084440a11d113000361cf222d9b403b8d7cd61be57850520143c2d28986ff92a76d68d73ef95c391899d906f6d4fb8e5170aefc62ce91e45 |
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 | Cookie Name | Evidence |
|---|---|---|
| https://bpusdataru-probolo.jatengprov.go.id/ | TS1e6c9646029, TS1e6c9646078, TS133faa19027 | The server responded with Set-Cookie header(s) that does not specify the HttpOnly flag: Set-Cookie: TS1e6c9646029=0817188341ab280011b21f78e80540f92e7566de20af646da3f8ae6c9c41a79d74bdef21aa7dd89ba7f74e9e65862c0d Set-Cookie: TS1e6c9646078=0817188341ab2000b24fa7a2768d55e883d05d70079410a48dbad7f4e5151248203ba5051f0b08aa0867eef6ef18b0018885ee50ff5696a38f5f2ab0fdc2c53847958d73aed9a887c81ae4bb823015fa00a4c6ee31bbca2d6907b4ef3034333274a20fd09ee165f30b2850e9fac6ed5d08124e80d0594f7ad4f21ca4acd9c4098d8105acaad12732ce34c62e05e91de45f16ca9771c38a034992ca960fde8e6f7b05f993366265811989f1228d05b139ffebb7bbea5e2a0f5f7e3c74c8ad5f94a0715cf61b1109fc8c593c31ed62788490381d16504216c6b25823f231e2ad0b43a45338bec4d9ad9b75cdcabd7fa00a30d53569136b373e0024e4475a3becad4ec293d20204c20d107f3cc75519c88bbb23058f893e0febf16d3ef7cb25e1abc5087bab147e6c01100526e101e433ddb5bb873e3c72afd2a718eed7e8856029ba380674f8b468ee80d2b31860eceb8ee0c9fd9b56aa83910092a94740c698aa942565074d6a1dc6256d5da2d99a0d79812cccaa7604ef6c6184ee557933560e9c2d1c000993937f3d39858cd2d543edf8f47912123091ec9517816620c2b83b15c7dca4614f042ce62ad6c5904c7d76096483ab42381fabf5f3afaa328499c81b0b58d10306bce3a91d77be932ef0bcaf8ee6534cba5207f6d99cb25fce0d8b Set-Cookie: TS133faa19027=0817188341ab2000e70394c92ada64baec467d68489d0c769d239ef56307ad267940c0c6e4e5901d084440a11d113000361cf222d9b403b8d7cd61be57850520143c2d28986ff92a76d68d73ef95c391899d906f6d4fb8e5170aefc62ce91e45 |
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 | Evidence |
|---|---|
| https://bpusdataru-probolo.jatengprov.go.id/ | 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://bpusdataru-probolo.jatengprov.go.id/ | 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 |
|---|---|
| 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
| URL | Evidence |
|---|---|
| https://bpusdataru-probolo.jatengprov.go.id/ | Response headers do not include the Referrer-Policy HTTP security header as well as the |
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
Evidence
We managed to extract the zone file from the ns4.jatengprov.go.id name server.
Below are the first 5 lines of the zone file:
bpusdataru-probolo.jatengprov.go.id. 86400 IN SOA ns1.jatengprov.go.id. noc.sijoli.jatengprov.go.id. 2025111402 3600 1800 1209600 86400 bpusdataru-probolo.jatengprov.go.id. 14400 IN TXT "v=spf1 ip4:103.9.227.34 +a +mx include:jatengprov.go.id +ip4:103.9.227.36 +ip4:103.9.227.1 +ip4:103.9.227.1 +ip4:103.9.227.35 ~all" bpusdataru-probolo.jatengprov.go.id. 86400 IN NS ns1.jatengprov.go.id. bpusdataru-probolo.jatengprov.go.id. 86400 IN NS ns2.jatengprov.go.id. bpusdataru-probolo.jatengprov.go.id. 86400 IN NS ns4.jatengprov.go.id.
You can also see the entire zone file here.
Vulnerability description
The remote name server permits the execution of DNS zone transfers, a process that enables a malicious attacker to rapidly compile a list of potential targets. Furthermore, organizations frequently employ naming conventions that may inadvertently reveal a server's primary purpose, such as dev.example.com, staging.example.com, prod.example.com, and so forth.
Risk description
This data can be used by an attacker to gain insights about the network's structure and to find new potential targets.
Recommendation
Reconfigure the DNS server to only allow zone transfers from trusted IP addresses.
Evidence
We found insecure DNS cookie usage on the following nameservers: ns4.jatengprov.go.id
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
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| bpusdataru-probolo.jatengprov.go.id | A | IPv4 address | 103.107.245.249 |
| bpusdataru-probolo.jatengprov.go.id | NS | Name server | ns1.jatengprov.go.id |
| bpusdataru-probolo.jatengprov.go.id | NS | Name server | ns2.jatengprov.go.id |
| bpusdataru-probolo.jatengprov.go.id | NS | Name server | ns4.jatengprov.go.id |
| bpusdataru-probolo.jatengprov.go.id | MX | Mail server | 0 bpusdataru-probolo.jatengprov.go.id |
| bpusdataru-probolo.jatengprov.go.id | SOA | Start of Authority | ns1.jatengprov.go.id. noc.sijoli.jatengprov.go.id. 2025111402 3600 1800 1209600 86400 |
| bpusdataru-probolo.jatengprov.go.id | SPF | Sender Policy Framework | "v=spf1 ip4:103.9.227.34 +a +mx include:jatengprov.go.id +ip4:103.9.227.36 +ip4:103.9.227.1 +ip4:103.9.227.1 +ip4:103.9.227.35 ~all" |
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 |
|---|---|
| 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.