Vulnerability Scan Result

Target:

https://click.e.atlassian.com/?qs=64545afee29877b73e5f428c64fa19a277a2b121902cc8d35c22502fbe2c382d282a3482950281fc4142e070c8e9bc8cb5e259feef8f795787c7bedd5980406e (redirect)

Scanned target: https://www.atlassian.com/blog?utm_source=sfmc&utm_medium=email&utm_campaign=footer&jobid=107558134&subid=1905804511

Submitted: Nov 05, 2025 from BD

Public Scan

Scan mode: Passive (non-intrusive)

Summary

low

Info

Low

Medium

High

Critical

Screenshot

Screenshot could not be taken.

Title:	Work Life by Atlassian - Unleashing the potential of all teams with tips, tools, and practices
Description:	Unleashing the potential of all teams with tips, tools, and practices

IP Information

ip_address	13.227.180.4
country	US
network_name	-
asn	-

Open Ports

80/tcp	http	Amazon CloudFront httpd -
443/tcp	https	CloudFront -

Web Technologies

No technologies could be detected.

Web Application Vulnerabilities

Evidence

URL Evidence

URL	Evidence
https://www.atlassian.com/blog	Response headers include the HTTP Content-Security-Policy security header with the following security issues:`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. 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'.`

https://www.atlassian.com/blog

Response headers include the HTTP Content-Security-Policy security header with the following security issues: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. 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'.

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://www.atlassian.com/blog	GET	Query: jobid=107558134 subid=1905804511 utm_campaign=footer utm_medium=email utm_source=sfmc 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	`1 : <link rel="profile" href="http://gmpg.org/xfn/11">`

Vulnerability description

We noticed that the target application is serving mixed content. This occurs when initial HTML is loaded over a secure HTTPS connection, but other resources (such as images, videos, stylesheets, scripts) are loaded over an insecure HTTP connection. This is called mixed content because both HTTP and HTTPS content are being loaded to display the same page, and the initial request was secure over HTTPS.

Risk description

The risk is that the insecurely loaded resources (HTTP) on an otherwise secure page (HTTPS) can be intercepted or manipulated by attackers, potentially leading to eavesdropping or content tampering.

Recommendation

Ensure that all external resources the page references are loaded using HTTPS.

Classification

CWE	CWE-311
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL
https://www.atlassian.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
https://www.atlassian.com/blog	Response headers do not include the Referrer-Policy HTTP security header as well as the `<meta/>` tag with name 'referrer' is not present in the response.

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

Evidence

URL	Evidence
https://www.atlassian.com/blog/author/	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

Infrastructure Vulnerabilities

Evidence

Software / Version	Category
Magnolia CMS	CMS
Algolia	Search engines
Java	Programming languages
Amazon Web Services	PaaS
Zipkin	Analytics
HSTS	Security
Amazon CloudFront	CDN
AWS Certificate Manager	SSL/TLS certificate authorities
HTTP/3	Miscellaneous
reCAPTCHA	Security
OneTrust	Cookie compliance
jQuery	JavaScript libraries
Open Graph	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

Domain Queried	DNS Record Type	Description	Value
www.atlassian.com	A	IPv4 address	13.227.180.4

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.