Vulnerability Scan Result

Target:

https://www.oracle.com/security-alerts/alert-cve-2025-61884.html

Scanned target: https://www.oracle.com/security-alerts/alert-cve-2025-61884.html

Submitted: Oct 16, 2025 from NL

Public Scan

Scan mode: Passive (non-intrusive)

Summary

medium

Info

Low

Medium

High

Critical

Screenshot

Screenshot could not be taken.

Title:	Oracle Security Alerts CVE-2025-61884
Description:	No description found

IP Information

ip_address	2.18.233.166
country	IT
network_name	Akamai Technologies Inc
asn	AS16625

Open Ports

80/tcp	http	AkamaiGHost -
443/tcp	https	AkamaiGHost -

Web Technologies

Software / Version	Category
Akamai	CDN
Boomerang	JavaScript libraries, RUM
Akamai mPulse	RUM
Adobe Experience Platform Identity Service	Customer data platform
Java	Programming languages
jQuery	JavaScript libraries
Oracle Dynamic Monitoring Service	Miscellaneous
Tealium	Tag managers, Customer data platform
TrustArc	Cookie compliance
Adobe Analytics	Analytics
Akamai Bot Manager	Security
Brightcove	Video players
DigiCert	SSL/TLS certificate authorities
Oracle WebLogic Server	Web servers
HSTS	Security
ServiceNow	Miscellaneous

Web Application Vulnerabilities

Evidence

URL	Cookie Name	Evidence
https://www.oracle.com/security-alerts/alert-cve-2025-61884.html	akaas_aud-seg-ocom-prod	The server responded with Set-Cookie header(s) that does not specify the HttpOnly flag: Set-Cookie: akaas_aud-seg-ocom-prod=2147483647~~rv=39~~id=a268d2c8a8ec1fd1272f7de27afd6c0f

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	Method	Parameters	Evidence
https://www.oracle.com/security-alerts/alert-cve-2025-61884.html	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	Suspicious comment Admin found in: `<!-- www-us HeadAdminContainer -->`

Vulnerability description

We have discovered that the target application's code contains suspicious comments that may be related to potential bugs, incomplete functionality, or weaknesses. These comments often arise during development and testing phases but are inadvertently left in the code.

Risk description

The risk exists that attackers could analyze these comments to identify vulnerabilities or weaknesses in the application. While comments themselves do not directly lead to security breaches, they may guide attackers to focus their efforts on specific parts of the application, potentially uncovering and exploiting vulnerabilities.

Recommendation

Remove comments that suggest the presence of bugs, incomplete functionality, or weaknesses, before deploying the application.

Classification

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

Evidence

URL
https://www.oracle.com/robots.txt

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

URL	Evidence
https://www.oracle.com/security-alerts/alert-cve-2025-61884.html	Response headers include the HTTP Content-Security-Policy security header with the following security issues: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'. object-src: Missing object-src allows the injection of plugins which can execute JavaScript. We recommend setting it to 'none'. script-src: script-src directive is missing. default-src: The default-src directive should be set as a fall-back when other restrictions have not been specified. 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'.

https://www.oracle.com/security-alerts/alert-cve-2025-61884.html

Response headers include the HTTP Content-Security-Policy security header with the following security issues: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'. object-src: Missing object-src allows the injection of plugins which can execute JavaScript. We recommend setting it to 'none'. script-src: script-src directive is missing. default-src: The default-src directive should be set as a fall-back when other restrictions have not been specified. 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'.

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

Software / Version	Category
Akamai	CDN
Boomerang	JavaScript libraries, RUM
Akamai mPulse	RUM
Adobe Experience Platform Identity Service	Customer data platform
Java	Programming languages
jQuery	JavaScript libraries
Oracle Dynamic Monitoring Service	Miscellaneous
Tealium	Tag managers, Customer data platform
TrustArc	Cookie compliance
Adobe Analytics	Analytics
Akamai Bot Manager	Security
Brightcove	Video players
DigiCert	SSL/TLS certificate authorities
Oracle WebLogic Server	Web servers
HSTS	Security
ServiceNow	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

URL	Method	Summary
https://www.oracle.com/security-alerts/alert-cve-2025-61884.html	OPTIONS	We did a HTTP OPTIONS request. The server responded with a 200 status code and the header: `Allow: GET, HEAD, POST, TRACE, OPTIONS` Request / Response

Vulnerability description

We have noticed that the webserver responded with an Allow HTTP header when an OPTIONS HTTP request was sent. This method responds to requests by providing information about the methods available for the target resource.

Risk description

The only risk this might present nowadays is revealing debug HTTP methods that can be used on the server. This can present a danger if any of those methods can lead to sensitive information, like authentication information, secret keys.

Recommendation

We recommend that you check for unused HTTP methods or even better, disable the OPTIONS method. This can be done using your webserver configuration.

Classification

CWE	CWE-16
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL
Missing: https://www.oracle.com/.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.

Infrastructure Vulnerabilities

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

Domain Queried	DNS Record Type	Description	Value
www.oracle.com	A	IPv4 address	2.18.233.166
www.oracle.com	AAAA	IPv6 address	2a02:26f0:2d:898::a15
www.oracle.com	AAAA	IPv6 address	2a02:26f0:2d:8a2::a15
www.oracle.com	CNAME	Canonical name	ds-www.oracle.com.edgekey.net

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.