Vulnerability Scan Result

Target:

https://jss.jogjakota.go.id/

Scanned target: https://jss.jogjakota.go.id/

Submitted: Feb 03, 2026 from YE

Public Scan

Scan mode: Passive (non-intrusive)

Summary

medium

Info

Low

Medium

High

Critical

Screenshot

Screenshot could not be taken.

Title:	Jogja Smart Service
Description:	Jogja Smart Service

IP Information

ip_address	103.210.193.133
country	ID
network_name	Dinas Komunikasi Informatika dan Persandian Kota Yogyakarta
asn	AS38526

Open Ports

80/tcp	http	Mbuh -
443/tcp	https	XXXXX -

Web Technologies

Software / Version	Category
Firebase 9.8.1	Databases, Development
Google Analytics GA4	Analytics
Google Font API	Font scripts
DigiCert	SSL/TLS certificate authorities
Google Tag Manager	Tag managers
HSTS	Security

Web Application Vulnerabilities

Evidence

URL	Cookie Name	Evidence
https://jss.jogjakota.go.id/	jss_pemerintah_kota_yogyakarta_session, cookiesession1	Set-Cookie: jss_pemerintah_kota_yogyakarta_session=eyJpdiI6ImpEaStxa2oydk5NM1p4RlFaSnVORFE9PSIsInZhbHVlIjoic1FYajZMRTBNYVE5cXI0Zlp6TTlRUllLRWI1aTYrYURRRjdEREdkY0t5dndUQlRtTTFINnlmcXNjT2RiZlF6dUlyUFRCUGE2eGVCZFZ2ZnlVeWpJZCswcDU4QnBXYzBrS25QN0RpTFJjd0doNkpNLzM5c1V4cnA1ZjZnNEZudjYiLCJtYWMiOiIzMmMwMzVmYzU5NTczNjFlZmQ2ZDM5YTRmNjMwYWVlNzUxOGM4ZTI2MDNkYjhjYmNmODg1ZmVlNDNlMTZiNGExIiwidGFnIjoiIn0%3D Set-Cookie: cookiesession1=678B289AA03566A05C6A3354F2477D99

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://jss.jogjakota.go.id/v6/sso	KC_AUTH_SESSION_HASH	The server responded with Set-Cookie header(s) that does not specify the HttpOnly flag: Set-Cookie: KC_AUTH_SESSION_HASH=1IcebWXElgFtp1pa4UZ8py0Hrl9Yn24z5cEUcZBR0Xc

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

URL	Evidence
https://jss.jogjakota.go.id/v6/sso	Response headers include the HTTP Content-Security-Policy security header with the following security issues:frame-src: frame-src directive allows localhost as source. Please make sure to remove this in production environments. frame-ancestors: frame-ancestors directive allows localhost as source. Please make sure to remove this in production environments. default-src: The default-src directive should be set as a fall-back when other restrictions have not been specified. frame-src: 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'. frame-ancestors: Allow only resources downloaded over HTTPS. 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.

https://jss.jogjakota.go.id/v6/sso

Response headers include the HTTP Content-Security-Policy security header with the following security issues:frame-src: frame-src directive allows localhost as source. Please make sure to remove this in production environments. frame-ancestors: frame-ancestors directive allows localhost as source. Please make sure to remove this in production environments. default-src: The default-src directive should be set as a fall-back when other restrictions have not been specified. frame-src: 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'. frame-ancestors: Allow only resources downloaded over HTTPS. 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.

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	Method	Parameters	Evidence
https://jss.jogjakota.go.id/v6/event	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 Cookies: XSRF-TOKEN=eyJpdiI6InZzWVp0dWx6MDlMd3BXb3RxVXFmZ0E9PSIsInZhbHVlIjoibnhHOHUxM0IyZjVHYTZOdVVnUVZZK3Y0WHhPYjRZQyswNlRUU1R5VDVEZ0ZUcVNIZWs0QXpzSjl...	Response has an internal server error status code: 500

Vulnerability description

We noticed that the target application's website does not properly handle or incorrectly manages exceptional conditions like Internal Server Errors. These errors can reveal sensitive information through their error messages. For instance, an error message could inadvertently disclose system paths or private application details.

Risk description

The risk exists that attackers could utilize information revealed in Internal Server Error messages to mount more targeted and effective attacks. Detailed error messages could, for example, expose a path traversal weakness (CWE-22) or other exploitable system vulnerabilities.

Recommendation

Ensure that error messages only contain minimal details that are useful to the intended audience, and nobody else. The messages need to strike the balance between being too cryptic and not being cryptic enough. They should not necessarily reveal the methods that were used to determine the error. Such detailed information can be used to refine the original attack to increase the chances of success. If errors must be tracked in some detail, capture them in log messages - but consider what could occur if the log messages can be viewed by attackers. Avoid recording highly sensitive information such as passwords in any form. Avoid inconsistent messaging that might accidentally tip off an attacker about internal state, such as whether a username is valid or not.

Classification

CWE	CWE-209
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL	Evidence
https://jss.jogjakota.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
Firebase 9.8.1	Databases, Development
Google Analytics GA4	Analytics
Google Font API	Font scripts
DigiCert	SSL/TLS certificate authorities
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	Method	Parameters	Evidence
https://jss.jogjakota.go.id/v6/event	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 Cookies: XSRF-TOKEN=eyJpdiI6InZzWVp0dWx6MDlMd3BXb3RxVXFmZ0E9PSIsInZhbHVlIjoibnhHOHUxM0IyZjVHYTZOdVVnUVZZK3Y0WHhPYjRZQyswNlRUU1R5VDVEZ0ZUcVNIZWs0QXpzSjl...	Error message internal server error found in: `ame="googlebot" content="noindex"> <title>500 internal server error</title> <meta name="description" content="jog`

Vulnerability description

We noticed that the target application does not properly handle exceptional conditions, leading to error messages that reveal sensitive information.

Risk description

The risk is that an attacker may use the contents of error messages to help launch another, more focused attack. For example, an attempt to exploit a path traversal weakness (CWE-22) might yield the full pathname of the installed application.

Recommendation

It is recommended treating all exceptions of the application flow. Ensure that error messages only contain minimal details.

Classification

CWE	CWE-209
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL
Missing: https://jss.jogjakota.go.id/.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://jss.jogjakota.go.id/v6/syarat-dan-ketentuan	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 Cookies: XSRF-TOKEN=eyJpdiI6Iks1cVBmdDZpYllkT2E5YzNSakFMcGc9PSIsInZhbHVlIjoiRDFWTy9MYUk3WjVFdkUxdkFGOFBJY1g3UmV0OTJYK3YwOUZUL0xCK3Yybnp3RmZBV0hLQS9xdjZ...	Email Address: kominfosandi@jogjakota.go.id

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

Infrastructure Vulnerabilities

Operating System	Accuracy
Linux 3.2	89%

Evidence

Software / Version	Category
Firebase 9.8.1	Databases, Development
Google Tag Manager	Tag managers
Google Analytics GA4	Analytics
HSTS	Security
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

Domain Queried	DNS Record Type	Description	Value
jss.jogjakota.go.id	A	IPv4 address	103.210.193.133
jss.jogjakota.go.id	AAAA	IPv6 address	2405:3740:8008:10::202

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
Firebase 9.8.1	Databases, Development
Google Tag Manager	Tag managers
Google Analytics GA4	Analytics
HSTS	Security
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.