Vulnerability Scan Result

Target:

https://www.sas.com/en_us/home.html

Scanned target: https://www.sas.com/en_us/home.html

Submitted: Dec 05, 2025 from GQ

Public Scan

Scan mode: Passive (non-intrusive)

Summary

medium

Info

Low

Medium

High

Critical

Screenshot

Screenshot could not be taken.

Title:	SAS: Data and AI Solutions \| SAS
Description:	SAS is the leader in analytics. Through innovative Analytics, Artificial Intelligence and Data Management software and services, SAS helps turn your data into better decisions.

IP Information

ip_address	23.62.193.246
country	GB
network_name	Akamai Technologies, Inc.
asn	AS16625

Open Ports

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

Web Technologies

Software / Version	Category
Microsoft Advertising	Advertising
Linkedin Ads	Advertising
Linkedin Insight Tag	Analytics
Okta 6.3.0	Authentication
core-js 3.6.4	JavaScript libraries
Apache HTTP Server	Web servers
Java	Programming languages
jQuery	JavaScript libraries
Open Graph	Miscellaneous
TrustArc	Cookie compliance
Priority Hints	Performance
Adobe Experience Manager	CMS
Brightcove	Video players
DigiCert	SSL/TLS certificate authorities
Google Tag Manager	Tag managers
iCIMS	Recruitment & staffing
HSTS	Security

Web Application Vulnerabilities

Evidence

URL	Cookie Name	Evidence
https://www.sas.com/en_us/learn/academic-programs/educators.html	TSb4656705027	Set-Cookie: TSb4656705027=0863bad25bab2000154fe7403537453bfa77eb6fbac2b0792252bda3a1bf3ddf149e52568b5121b8084f933bfa113000fa3c973295f5fd869c1199921cd3cead244eaf01efc8a278aa085916c61cebe468352d3618f2e8c997971f60df3ec987

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://www.sas.com/en_us/learn/academic-programs/educators.html	TSb4656705027	The server responded with Set-Cookie header(s) that does not specify the HttpOnly flag: Set-Cookie: TSb4656705027=0863bad25bab2000154fe7403537453bfa77eb6fbac2b0792252bda3a1bf3ddf149e52568b5121b8084f933bfa113000fa3c973295f5fd869c1199921cd3cead244eaf01efc8a278aa085916c61cebe468352d3618f2e8c997971f60df3ec987

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

Software / Version	Category
Microsoft Advertising	Advertising
Linkedin Ads	Advertising
Linkedin Insight Tag	Analytics
Okta 6.3.0	Authentication
core-js 3.6.4	JavaScript libraries
Apache HTTP Server	Web servers
Java	Programming languages
jQuery	JavaScript libraries
Open Graph	Miscellaneous
TrustArc	Cookie compliance
Priority Hints	Performance
Adobe Experience Manager	CMS
Brightcove	Video players
DigiCert	SSL/TLS certificate authorities
Google Tag Manager	Tag managers
iCIMS	Recruitment & staffing
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

URL	Evidence
https://www.sas.com/en_us/home.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'. script-src: script-src should not allow '*' as source. This may enable execution of malicious JavaScript. 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: ''unsafe-inline'' allows the execution of unsafe in-page scripts and event handlers. script-src: 'unsafe-eval' allows the execution of code injected into DOM APIs such as eval(). script-src: data: URI in script-src allows the execution of unsafe scripts. script-src: 'self' can be problematic if you host JSONP, Angular or user uploaded files.

https://www.sas.com/en_us/home.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'. script-src: script-src should not allow '*' as source. This may enable execution of malicious JavaScript. 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: ''unsafe-inline'' allows the execution of unsafe in-page scripts and event handlers. script-src: 'unsafe-eval' allows the execution of code injected into DOM APIs such as eval(). script-src: data: URI in script-src allows the execution of unsafe scripts. script-src: 'self' can be problematic if you host JSONP, Angular or user uploaded files.

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
https://www.sas.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	Method	Parameters	Evidence
https://www.sas.com/en_us/home.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	Operating system paths found in the HTTP response: `/content/sascom/en_us/home/refs/cloud/jcr` `/content/sascom/en_us/home/refs/models/jcr` `/content/sascom/en_us/home/jcr` `/content/sascom/en_us/home/refs/featured-topics-from-sas/jcr` `/home/users/7` `/content/sascom/en_us/home/refs/promo-banner/jcr` `/content/sascom/en_us/home/refs/solutions/jcr` `/en_us/home/_jcr_content/par/styledcontainer_7329/par/imageajax.ajaxcontext.html`

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
Missing: https://www.sas.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.

Evidence

URL	Method	Summary
https://www.sas.com/en_us/home.html	OPTIONS	We did a HTTP OPTIONS request. The server responded with a 405 status code and the header: `Allow: ` 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	Method	Parameters	Evidence
https://www.sas.com/en_us/learn/academic-programs/educators.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 Cookies: BIGipServer~WEB~www.sas.com-443-pool=1761979797.47873.0000 TSb4656705027=0863bad25bab2000154fe7403537453bfa77eb6fbac2b0792252bda3a1bf3ddf149e5...	Email Address: twnedu@sas.com academic@sas.com sasindiatraining@sas.com CHN.Education@sas.com

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 5.0 - 5.4	93%

Evidence

Domain Queried	DNS Record Type	Description	Value
www.sas.com	A	IPv4 address	23.62.193.246
www.sas.com	CNAME	Canonical name	www.sas.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.

Evidence

Software / Version	Category
Adobe Experience Manager	CMS
Java	Programming languages
Brightcove	Video players
iCIMS	Recruitment & staffing
Okta 5.0.0	Authentication
Apache HTTP Server	Web servers
Linkedin Insight Tag	Analytics
Linkedin Ads	Advertising
DigiCert	SSL/TLS certificate authorities
Microsoft Advertising	Advertising
Google Tag Manager	Tag managers
Modernizr	JavaScript libraries
jQuery	JavaScript libraries
HSTS	Security
core-js 3.6.4	JavaScript libraries

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.