Security - https://bitbucket.org BeaverCheck Audit

F

Subresource Integrity

Action

0 of 10 external resources have SRI

FIX

0 of 10 external resources have SRI

External script from www.youtube.com lacks integrity attribute

Without SRI, if this CDN is compromised, attackers could inject malicious code.

Got: https://www.youtube.com/s/player/218d9d92/www-widgetapi.vflset/www-widgetapi.js

External script from www.youtube.com lacks integrity attribute

Without SRI, if this CDN is compromised, attackers could inject malicious code.

Got: https://www.youtube.com/iframe_api

External link from wac-cdn.atlassian.com lacks integrity attribute

Without SRI, if this CDN is compromised, attackers could inject malicious code.

Got: https://wac-cdn.atlassian.com/static/master/10783/assets/build/css/wpl-main.css?cdnVersion=3343

External link from wac-cdn.atlassian.com lacks integrity attribute

Without SRI, if this CDN is compromised, attackers could inject malicious code.

Got: https://wac-cdn.atlassian.com/static/master/10783/assets/build/css/bitbucket.css?cdnVersion=3343

External script from wac-cdn.atlassian.com lacks integrity attribute

Without SRI, if this CDN is compromised, attackers could inject malicious code.

Got: https://wac-cdn.atlassian.com/static/master/10783/assets/build/js/head.js?cdnVersion=3343

External script from wac-cdn.atlassian.com lacks integrity attribute

Without SRI, if this CDN is compromised, attackers could inject malicious code.

Got: https://wac-cdn.atlassian.com/static/master/10783/assets/build/js/jquery.js?cdnVersion=3343

External script from atl-onetrust-wrapper.atlassian.com lacks integrity attribute

Without SRI, if this CDN is compromised, attackers could inject malicious code.

Got: https://atl-onetrust-wrapper.atlassian.com/assets/atl-onetrust-wrapper.min.js

External script from cdn.cookielaw.org lacks integrity attribute

Without SRI, if this CDN is compromised, attackers could inject malicious code.

Got: https://cdn.cookielaw.org/consent/9cf1b0a8-9eed-4564-bbcf-588e96662537/otSDKStub.js

External script from wac-cdn.atlassian.com lacks integrity attribute

Without SRI, if this CDN is compromised, attackers could inject malicious code.

Got: https://wac-cdn.atlassian.com/static/master/10783/assets/build/js/main.js?cdnVersion=3343

External script from wac-cdn.atlassian.com lacks integrity attribute

Without SRI, if this CDN is compromised, attackers could inject malicious code.

Got: https://wac-cdn.atlassian.com/static/master/10783/assets/build/js/ad-hoc/bitbucket/bitbucket.js?cdnVersion=3343

SRI Coverage 0 / 10 of external resources have integrity hashes

Tag	Domain	Integrity
<script>	www.youtube.com	✗ Missing
<script>	www.youtube.com	✗ Missing
<link>	wac-cdn.atlassian.com	✗ Missing
<link>	wac-cdn.atlassian.com	✗ Missing
<script>	wac-cdn.atlassian.com	✗ Missing
<script>	wac-cdn.atlassian.com	✗ Missing
<script>	atl-onetrust-wrapper.atlassian.com	✗ Missing
<script>	cdn.cookielaw.org	✗ Missing
<script>	wac-cdn.atlassian.com	✗ Missing
<script>	wac-cdn.atlassian.com	✗ Missing

D

Permissions-Policy

Action

No header set

FIX

No header set

No Permissions-Policy header

Consider adding a Permissions-Policy header to restrict browser feature access from embedded content.

No Permissions-Policy header set.

Without this header, embedded iframes can request access to sensitive device features.

Suggested header

Permissions-Policy: camera=(), microphone=(), geolocation=(), payment=(), usb=()

C

Security Headers

Action

6 of 10 headers properly configured

REVIEW

6 of 10 headers properly configured

Strict-Transport-Security is properly configured

Got: max-age=63072000; includeSubDomains; preload

X-Content-Type-Options is properly configured

Got: nosniff

X-Frame-Options is properly configured

Got: deny

Referrer-Policy header is missing

Controls how much referrer information is sent with requests. Set to 'strict-origin-when-cross-origin' or stricter.

Expected: strict-origin-when-cross-origin

Permissions-Policy header is missing

Controls which browser features (camera, microphone, geolocation) are allowed. Set it to restrict unused features.

Expected: geolocation=(), camera=(), microphone=()

Content-Security-Policy is present

Got: frame-ancestors 'none';

Cross-Origin-Opener-Policy header is missing

COOP isolates your browsing context, preventing cross-origin side-channel attacks. Set to 'same-origin'.

Expected: same-origin

Cross-Origin-Embedder-Policy header is missing

COEP prevents loading cross-origin resources without explicit permission. Required for SharedArrayBuffer and high-resolution timers.

Expected: require-corp

X-Powered-By header is not present

Server header is present without version info

Got: AtlassianEdge

Controls how much referrer information is sent with requests. Set to 'strict-origin-when-cross-origin' or stricter.

Expected: strict-origin-when-cross-origin

Why this matters

Default browser behavior leaks full URLs (including query params and tokens) to every third-party resource — set a strict policy.

Learn more ▾

Without a Referrer-Policy header, browsers send the full referring URL with images, scripts, and fonts loaded from third-party origins. URLs containing tokens, user IDs, or session params end up in third-party logs. Set `Referrer-Policy: strict-origin-when-cross-origin` (or stricter) to limit leakage.

Source: MDN / W3C

Controls which browser features (camera, microphone, geolocation) are allowed. Set it to restrict unused features.

Expected: geolocation=(), camera=(), microphone=()

Why this matters

Permissions-Policy locks down browser APIs you don't use — without it, every page can request camera/mic/geolocation if XSS lands.

Learn more ▾

By default every page can request the camera, microphone, geolocation, payment APIs, and dozens more. Permissions-Policy turns off the ones you don't need so a future bug can't quietly start using them. It's a defense-in-depth header — one line, big surface reduction.

Source: MDN / W3C

COOP isolates your browsing context, preventing cross-origin side-channel attacks. Set to 'same-origin'.

Expected: same-origin

Why this matters

COOP isolates your top-level browsing context from cross-origin windows — without it, popup-based side-channel attacks remain possible.

Learn more ▾

Cross-Origin-Opener-Policy: same-origin prevents cross-origin pages from sharing a browsing-context group with yours. This blocks cross-window references that enable Spectre-style timing attacks and tab-nabbing. Required if you want to enable SharedArrayBuffer.

Source: MDN / web.dev

COEP prevents loading cross-origin resources without explicit permission. Required for SharedArrayBuffer and high-resolution timers.

Expected: require-corp

Why this matters

COEP enforces that all embedded resources opt-in to cross-origin embedding — required for cross-origin isolation features.

Learn more ▾

Cross-Origin-Embedder-Policy: require-corp ensures every embedded resource (script, iframe, image) explicitly allows being loaded cross-origin. Combined with COOP, this enables the cross-origin-isolated context that unlocks SharedArrayBuffer, high-resolution timers, and other powerful APIs.

Source: MDN / web.dev

B

Content Security Policy

2 of 10 CSP checks passed

REVIEW

2 of 10 CSP checks passed

Raw CSP policy

Got: frame-ancestors 'none';

default-src directive is missing

default-src provides a fallback for other directives. Set it to restrict default resource loading.

Expected: default-src 'self'

No script-src or default-src to check for 'unsafe-inline'

No script-src or default-src to check for 'unsafe-eval'

No script-src or default-src to check for wildcard

object-src falls back to default-src

base-uri directive is missing

Without base-uri, attackers can inject a <base> tag to hijack relative URLs. Set it to 'self' or 'none'.

Expected: base-uri 'self'

frame-ancestors directive is set

Got: frame-ancestors 'none'

form-action directive is missing

form-action restricts where forms can submit data, preventing form hijacking.

Expected: form-action 'self'

upgrade-insecure-requests is not set

This directive upgrades HTTP resources to HTTPS automatically, preventing mixed content.

Expected: upgrade-insecure-requests

default-src provides a fallback for other directives. Set it to restrict default resource loading.

Expected: default-src 'self'

Why this matters

Security gaps expose your site and users to attacks, eroding trust.

Without base-uri, attackers can inject a <base> tag to hijack relative URLs. Set it to 'self' or 'none'.

Expected: base-uri 'self'

Why this matters

Missing base-uri in CSP leaves a base-tag injection attack path open even on otherwise strict policies.

Learn more ▾

A common omission: developers add CSP for script-src and frame-ancestors but forget base-uri. The result is a CSP that looks strict but lets an attacker rewrite every URL on the page via <base href>. Add `base-uri 'self'` to close the gap.

Source: MDN CSP

form-action restricts where forms can submit data, preventing form hijacking.

Expected: form-action 'self'

Why this matters

Security gaps expose your site and users to attacks, eroding trust.

This directive upgrades HTTP resources to HTTPS automatically, preventing mixed content.

Expected: upgrade-insecure-requests

Why this matters

Without upgrade-insecure-requests, any HTTP subresource link survives as a mixed-content warning instead of auto-upgrading.

Learn more ▾

Adding `upgrade-insecure-requests` to your CSP turns every http:// subresource fetch into https:// at the browser layer. One-line defense against accidental mixed content from legacy links or third-party widgets.

Source: MDN CSP

Parsed Policy

frame-ancestors 'none'

C

Cookie Security

Action

2 cookies analyzed, 1 checks passed

REVIEW

2 cookies analyzed, 1 checks passed

Cookie 'ajs_anonymous_id' is missing the Secure flag

Without the Secure flag, this cookie can be sent over unencrypted HTTP, exposing it to interception.

Cookie 'ajs_anonymous_id' is missing the HttpOnly flag

Without HttpOnly, this cookie can be accessed by JavaScript, making it vulnerable to XSS-based theft.

Cookie 'ajs_anonymous_id' has no SameSite attribute

Without an explicit SameSite attribute, browser default behavior varies. Set SameSite=Lax or Strict.

Cookie 'bxp_gateway_request_id' has the Secure flag

Cookie 'bxp_gateway_request_id' is missing the HttpOnly flag

Without HttpOnly, this cookie can be accessed by JavaScript, making it vulnerable to XSS-based theft.

Cookie 'bxp_gateway_request_id' has no SameSite attribute

Without an explicit SameSite attribute, browser default behavior varies. Set SameSite=Lax or Strict.

2 cookies analyzed 1 critical 4 warnings

Name	Secure	HttpOnly	SameSite	Size	Issues
ajs_anonymous_id	✗	✗	—	58 B	3
bxp_gateway_request_id	✓	✗	—	58 B	2

B

CORS Configuration

No CORS headers

REVIEW

No CORS headers

No CORS headers present — secure default

CORS Configuration ✓ Secure

No CORS headers detected.

Cross-origin requests are blocked by browser same-origin policy.

Origin reflection test

Some servers mirror the request Origin header, which can be exploited. Test manually:

curl -sI -H "Origin: https://evil.com" <url> | grep -i access-control

A+

TLS & Certificates

TLS 1.3, 7 checks passed

PASS

TLS 1.3, 7 checks passed

TLS 1.3 is used

Got: TLS 1.3

Strong cipher suite is used

Got: TLS_AES_128_GCM_SHA256

HTTP/2 is not negotiated

HTTP/2 provides multiplexing and header compression for better performance.

Got: http/1.1

Certificate is valid (expires in 186 days)

Got: 2026-10-24T23:59:59Z

Certificate chain has 2 certificates

Certificate uses modern signature algorithm

Got: SHA256-RSA

Certificate covers 2 domain(s)

Got: *.bitbucket.org, bitbucket.org

Certificate is issued by a trusted CA

Got: CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1,O=DigiCert Inc,C=US

HTTP/2 provides multiplexing and header compression for better performance.

Why this matters

HTTP/1.1 forces the browser to make sequential requests, multiplying latency on every page.

Learn more ▾

HTTP/2 (and HTTP/3) multiplex many requests over a single connection, eliminating head-of-line blocking. HTTP/1.1 forces the browser to either queue requests or open many parallel connections — both worse. Most modern web servers support HTTP/2 with one config line.

Source: MDN Web Docs

Connection

Protocol

TLS 1.3

Cipher Suite

TLS_AES_128_GCM_SHA256

HTTP Version

HTTP/1.1

Certificate Chain

Leaf Certificate

Subject CN=*.bitbucket.org,O=Atlassian US\, Inc.,L=San Francisco,ST=California,C=USIssuer CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1,O=DigiCert Inc,C=USValid 2026-04-09T00:00:00Z → 2026-10-24T23:59:59ZExpires in 186 days SANs *.bitbucket.org, bitbucket.orgSignature SHA256-RSASerial c290f3253e6089f915203826bbf1eee

Intermediate (CA Certificate)

Subject CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1,O=DigiCert Inc,C=USIssuer CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=USValid 2021-03-30T00:00:00Z → 2031-03-29T23:59:59ZExpires in 1803 days Signature SHA256-RSASerial cf5bd062b5602f47ab8502c23ccf066

A+

JS Library Vulnerabilities

No known vulnerabilities

PASS

No known vulnerabilities

No known JavaScript library vulnerabilities detected

No known JavaScript library vulnerabilities detected.

A+

Information Leakage

No exposures

PASS

No exposures

security.txt is present — good practice

No sensitive files exposed

No sensitive files exposed — all paths returned 404.

Path	Status	Category	Risk
/.git/HEAD	✓ Not found	Version Control	—
/.git/config	✓ Not found	Version Control	—
/.svn/entries	✓ Not found	Version Control	—
/.env	✓ Not found	Configuration	—
/.env.local	✓ Not found	Configuration	—
/.env.production	✓ Not found	Configuration	—
/wp-config.php	✓ Not found	Configuration	—
/.htaccess	✓ Not found	Configuration	—
/phpinfo.php	✓ Not found	Debug	—
/server-status	✓ Not found	Debug	—
/server-info	✓ Not found	Debug	—
/.well-known/security.txt	✗ Exposed	Security Policy	Info

A+

Email Security

DMARC: reject

PASS

DMARC: reject

DMARC policy is reject — strongest protection

DMARC

Policy reject — strongest protection Record v=DMARC1;p=reject;sp=reject;adkim=r;aspf=r;fo=1;rua=mailto:dmarc_rua@emaildefense.proofpoint.com,mailto:dmarc-rua@abuse.atlassian.com; ruf=mailto:dmarc_ruf@emaildefense.proofpoint.com,mailto:dmarc-ruf@abuse.atlassian.com

A+

security.txt

Signed, 2 contact(s) — RFC 9116 compliant

PASS

security.txt

Contact: https://www.atlassian.com/trust/security/report-a-vulnerability, mailto:security@atlassian.com

Expires: 2027-02-04T00:00:00.000Z

Encryption: https://security-static.prod.atl-paas.net/atlassian-security-public.asc

Policy: https://www.atlassian.com/.well-known/security.txt

A

Transport Security

HTTP/3, HSTS, and TLS version analysis

PASS

HTTP/3, HSTS, and TLS version analysis

HTTP/3 (QUIC) not advertised

HTTP/3 eliminates head-of-line blocking. If your CDN supports it, consider enabling it.

HSTS enabled (includeSubDomains, preload)

HSTS preload enabled

TLS 1.3 in use (fastest handshake, 1-RTT)