Vulnerability Scan Result

| Title: | Fakultas Sastra - Universitas Pamulang |
| Description: | <p>Fakultas Sastra Universitas Pamulang (Unpam) didirikan pada 2 Agustus 2001. Hal itu mengacu pada terbitnya Surat Keputusan Menteri Pendidikan Nasional Nomor 136/D/O/2001 tentang izin penyelenggaraan pendidikan tinggi. Saat ini Fakultas sastra beroperasi di Kampus II Unpam Viktor Lt. 5 gedung B, Jalan Raya Puspitek No. 46 Buaran Kecamatan Serpong, Kota Tangerang Selatan. Fakultas Sastra berada di bawah kelola Unpam. Yayasan yang menaungi Unpam awalnya Yayasan Prima Jaya, namun pada tahun 2004 dialih ma... |
| ip_address | 27.50.17.2 |
| country | ID |
| network_name | Pt MORA Telematika Indonesia |
| asn | AS131111 |
80/tcp | http | Apache httpd - |
443/tcp | https | Apache httpd - |
| Software / Version | Category |
|---|---|
| Centminmod | Web servers |
| CentOS | Operating systems |
| Apache HTTP Server | Web servers |
| Nginx | Web servers, Reverse proxies |
| Nuxt.js | JavaScript frameworks, Web frameworks, Static site generator |
| PHP | Programming languages |
| Sectigo | SSL/TLS certificate authorities |
| Vue.js | JavaScript frameworks |
| HSTS | Security |
Web Application Vulnerabilities
Evidence
| URL | Cookie Name | Evidence |
|---|---|---|
| https://fs.unpam.ac.id/berita/posts/sukses-menjadi-penulis-novel-best-seller-wawancara-eksklusif-dengan-radja | uniqueVisitId_unpam_sukses-menjadi-penulis-novel-best-seller-wawancara-eksklusif-dengan-radja | The server responded with Set-Cookie header(s) that does not specify the HttpOnly flag: Set-Cookie: uniqueVisitId_unpam_sukses-menjadi-penulis-novel-best-seller-wawancara-eksklusif-dengan-radja=uniqueVisitId_unpam_sukses-menjadi-penulis-novel-best-seller-wawancara-eksklusif-dengan-radja_1761953995427 |
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 | Cookie Name | Evidence |
|---|---|---|
| https://fs.unpam.ac.id/berita/posts/sukses-menjadi-penulis-novel-best-seller-wawancara-eksklusif-dengan-radja | uniqueVisitId_unpam_sukses-menjadi-penulis-novel-best-seller-wawancara-eksklusif-dengan-radja | Set-Cookie: uniqueVisitId_unpam_sukses-menjadi-penulis-novel-best-seller-wawancara-eksklusif-dengan-radja=uniqueVisitId_unpam_sukses-menjadi-penulis-novel-best-seller-wawancara-eksklusif-dengan-radja_1761953995427 |
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
| Software / Version | Category |
|---|---|
| Centminmod | Web servers |
| CentOS | Operating systems |
| Apache HTTP Server | Web servers |
| Nginx | Web servers, Reverse proxies |
| Nuxt.js | JavaScript frameworks, Web frameworks, Static site generator |
| PHP | Programming languages |
| Sectigo | SSL/TLS certificate authorities |
| Vue.js | JavaScript frameworks |
| 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://fs.unpam.ac.id/ | Response headers include the HTTP Content-Security-Policy security header with the following security issues: |
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://fs.unpam.ac.id/berita/posts/sastrapreneur-activities-2023 | 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: uniqueVisitId_unpam_sastrapreneur-activities-2023=uniqueVisitId_unpam_sastrapreneur-activities-2023_1761954001735 uniqueVisitId_unpam_sukses-m... | Operating system paths found in the HTTP response: |
Vulnerability description
We found operating system paths returned in a HTTP response.
Risk description
The risk is that path disclosure may help an attacker learn more about the remote server's file system, thus increasing the effectiveness and precision of any future attacks.
Recommendation
Configure the web server to avoid leaking path information by using generic error messages that do not reveal any internal file paths. Make sure no server file is referred with its absolute path in the website code.
Classification
| CWE | CWE-200 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Method | Parameters | Evidence |
|---|---|---|---|
| https://fs.unpam.ac.id/ | GET | Query: berita=AGENOLX 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 |
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 |
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
Vulnerability description
Website is accessible.
Infrastructure Vulnerabilities
Evidence
| Operating System | Accuracy |
|---|---|
| Android 7.1.2 (Linux 3.10) | 100% |
Vulnerability description
OS Detection
Evidence
| Software / Version | Category |
|---|---|
| Nuxt.js | JavaScript frameworks, Web frameworks, Static site generator |
| PHP | Programming languages |
| CentOS | Operating systems |
| Nginx | Web servers, Reverse proxies |
| Vue.js | JavaScript frameworks |
| Centminmod | Web servers |
| Apache HTTP Server | Web servers |
| Sectigo | SSL/TLS certificate authorities |
| 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
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| fs.unpam.ac.id | A | IPv4 address | 27.50.17.2 |
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.
