Is www.flickr.com secure and safe to use? | Web Security Optimization (WSO) report by Idyllum Labs.

Website security scan results for www.flickr.com

Safe mode. Please [ log in ] to see the full report!

At a glance

------------------
Site scanned: www.flickr.com
Date of scan: Nov. 29, 2022, 3:13 a.m.

Risk level: HIGH
SSL Status: [OK] SSL Encryption enforced

Total OWASP ZAP alerts: 226
Nmap open ports found: 2

Server

------------------
IP: 54.192.86.140
Location: United States
Web server: CloudFront

Open ports for www.flickr.com (Nmap scan)

------------------
Port 80 (tcp) - http
Port 443 (tcp) - https

OWASP ZAP scan results

------------------

Informative alerts

What does this mean?

Warnings:1:1832: Source list contains duplicate source expression 'https://*.googleadservices.com'. All but the first instance will be ignored.1:1863: Source list contains duplicate source expression 'https://*.googlesyndication.com'. All but the first instance will be ignored.1:2920: Source list contains duplicate source expression 'https://*.googleadservices.com'. All but the first instance will be ignored.1:2951: Source list contains duplicate source expression 'https://*.googlesyndication.com'. All but the first instance will be ignored.Info Items:1:2128: The ''unsafe-inline'' keyword-source has no effect in source lists that contain hash-source or nonce-source in CSP2 and later. Ensure that this pattern is only used for backwards compatibility with older CSP implementations and is not an oversight.

Where exactly is this vulnerability found?
  1. https://www.flickr.com/faves-i_love_u_get_away_from_me/
  2. https://www.flickr.com/%7Bfaq%7D
  3. https://www.flickr.com/gp/%7Bfaq%7D
  4. https://www.flickr.com/sitemap.xml
  5. https://www.flickr.com/photos/youpy/%7Burl%7D
  6. https://www.flickr.com/photos/tags/*/page
  7. https://www.flickr.com/groups/10millionphotos/%7Bfaq%7D
  8. https://www.flickr.com/change_language.gne?lang=zh-hk&magic_cookie=1f7e55c4983bb069c04be7dee7e5a48e
  9. https://www.flickr.com/photos/archivesact/6011019532/nearby/
  10. https://www.flickr.com/upload
  11. https://www.flickr.com/signin/
  12. https://www.flickr.com/change_language.gne?lang=es-us&magic_cookie=1f7e55c4983bb069c04be7dee7e5a48e
  13. https://www.flickr.com/gp/%7Burl%7D
  14. https://www.flickr.com/change_language.gne?csrf&lang=en-US
  15. https://www.flickr.com/change_language.gne?lang=ko-kr&magic_cookie=1f7e55c4983bb069c04be7dee7e5a48e
  16. https://www.flickr.com/services/oauth/
  17. https://www.flickr.com/photos/*/lightbox/
  18. https://www.flickr.com/change_language.gne?lang=id-id&magic_cookie=1f7e55c4983bb069c04be7dee7e5a48e
  19. https://www.flickr.com/people/youpy/contacts
  20. https://www.flickr.com/groups/*/lightbox/
How to solve this?

Ensure that your web server, application server, load balancer, etc. is properly configured to set the Content-Security-Policy header.

What does this mean?

Cookies can be scoped by domain or path. This check is only concerned with domain scope.The domain scope applied to a cookie determines which domains can access it. For example, a cookie can be scoped strictly to a subdomain e.g. www.nottrusted.com, or loosely scoped to a parent domain e.g. nottrusted.com. In the latter case, any subdomain of nottrusted.com can access the cookie. Loosely scoped cookies are common in mega-applications like google.com and live.com. Cookies set from a subdomain like app.foo.bar are transmitted only to that domain by the browser. However, cookies scoped to a parent-level domain may be transmitted to the parent, or any subdomain of the parent.

Where exactly is this vulnerability found?
  1. https://www.flickr.com/tools/demos/%7Burl%7D
  2. https://www.flickr.com/explore
  3. https://www.flickr.com/search/?text=ZAP
  4. https://www.flickr.com/photos/tags
  5. https://www.flickr.com/change_language.gne?lang=zh-hk&magic_cookie=1f7e55c4983bb069c04be7dee7e5a48e
  6. https://www.flickr.com/cameras
  7. https://www.flickr.com/tools/demos/%7Bfaq%7D
  8. https://www.flickr.com/groups/10millionphotos/pool/
  9. https://www.flickr.com/create
  10. https://www.flickr.com/services/oembed/?format=json&url=https://www.flickr.com/photos/youpy/
  11. https://www.flickr.com/people/youpy/groups/
  12. https://www.flickr.com/robots.txt
  13. https://www.flickr.com/
  14. https://www.flickr.com/groups/10millionphotos/%7Burl%7D
  15. https://www.flickr.com/photos/youpy/albums
  16. https://www.flickr.com/help/contact/
  17. https://www.flickr.com/change_language.gne?lang=en-us&magic_cookie=1f7e55c4983bb069c04be7dee7e5a48e
  18. https://www.flickr.com/sitemap.xml
  19. https://www.flickr.com/photos/*/lightbox/
  20. https://www.flickr.com/change_language.gne?lang=id-id&magic_cookie=1f7e55c4983bb069c04be7dee7e5a48e
How to solve this?

Always scope cookies to a FQDN (Fully Qualified Domain Name).

Low risk vulnerabilities

What does this mean?

No Anti-CSRF tokens were found in a HTML submission form.A cross-site request forgery is an attack that involves forcing a victim to send an HTTP request to a target destination without their knowledge or intent in order to perform an action as the victim. The underlying cause is application functionality using predictable URL/form actions in a repeatable way. The nature of the attack is that CSRF exploits the trust that a web site has for a user. By contrast, cross-site scripting (XSS) exploits the trust that a user has for a web site. Like XSS, CSRF attacks are not necessarily cross-site, but they can be. Cross-site request forgery is also known as CSRF, XSRF, one-click attack, session riding, confused deputy, and sea surf.CSRF attacks are effective in a number of situations, including: * The victim has an active session on the target site. * The victim is authenticated via HTTP auth on the target site. * The victim is on the same local network as the target site.CSRF has primarily been used to perform an action against a target site using the victim's privileges, but recent techniques have been discovered to disclose information by gaining access to the response. The risk of information disclosure is dramatically increased when the target site is vulnerable to XSS, because XSS can be used as a platform for CSRF, allowing the attack to operate within the bounds of the same-origin policy.

Where exactly is this vulnerability found?
  1. https://www.flickr.com/groups/*/lightbox/
  2. https://www.flickr.com/photos/tags
  3. https://www.flickr.com/abuse
  4. https://www.flickr.com/explore
  5. https://www.flickr.com/photos/*/lightbox/
  6. https://www.flickr.com/yss_fragment.gne
  7. https://www.flickr.com/tools/demos/
  8. https://www.flickr.com/search/?text=ZAP
  9. https://www.flickr.com/report_abuse.gne
  10. https://www.flickr.com/search/
  11. https://www.flickr.com/tools/demos/%7Bfaq%7D
  12. https://www.flickr.com/photos/youpy/albums
  13. https://www.flickr.com/services/developer
  14. https://www.flickr.com/photos/youpy/page2/
  15. https://www.flickr.com/cameras
  16. https://www.flickr.com/about
  17. https://www.flickr.com/people/youpy/
  18. https://www.flickr.com/events
  19. https://www.flickr.com/groups/10millionphotos/%7Bfaq%7D
  20. https://www.flickr.com/photos/i_love_u_get_away_from_me/
How to solve this?

Phase: Architecture and DesignUse a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.For example, use anti-CSRF packages such as the OWASP CSRFGuard.Phase: ImplementationEnsure that your application is free of cross-site scripting issues, because most CSRF defenses can be bypassed using attacker-controlled script.Phase: Architecture and DesignGenerate a unique nonce for each form, place the nonce into the form, and verify the nonce upon receipt of the form. Be sure that the nonce is not predictable (CWE-330).Note that this can be bypassed using XSS.Identify especially dangerous operations. When the user performs a dangerous operation, send a separate confirmation request to ensure that the user intended to perform that operation.Note that this can be bypassed using XSS.Use the ESAPI Session Management control.This control includes a component for CSRF.Do not use the GET method for any request that triggers a state change.Phase: ImplementationCheck the HTTP Referer header to see if the request originated from an expected page. This could break legitimate functionality, because users or proxies may have disabled sending the Referer for privacy reasons.

What does this mean?

A cookie has been set without the HttpOnly flag, which means that the cookie can be accessed by JavaScript. If a malicious script can be run on this page then the cookie will be accessible and can be transmitted to another site. If this is a session cookie then session hijacking may be possible.

Where exactly is this vulnerability found?
  1. https://www.flickr.com/change_language.gne?lang=id-id&magic_cookie=1f7e55c4983bb069c04be7dee7e5a48e
  2. https://www.flickr.com/
  3. https://www.flickr.com/help/terms
  4. https://www.flickr.com/tools/demos/%7Burl%7D
  5. https://www.flickr.com/people/youpy/contacts
  6. https://www.flickr.com/help/guidelines
  7. https://www.flickr.com/events
  8. https://www.flickr.com/faves-i_love_u_get_away_from_me/
  9. https://www.flickr.com/photos/i_love_u_get_away_from_me/
  10. https://www.flickr.com/change_language.gne?lang=vn-vn&magic_cookie=1f7e55c4983bb069c04be7dee7e5a48e
  11. https://www.flickr.com/signup
  12. https://www.flickr.com/change_language.gne?lang=de-de&magic_cookie=1f7e55c4983bb069c04be7dee7e5a48e
  13. https://www.flickr.com/change_language.gne?lang=id-id&magic_cookie=1f7e55c4983bb069c04be7dee7e5a48e
  14. https://www.flickr.com/people/youpy/groups/
  15. https://www.flickr.com/change_language.gne?lang=pt-br&magic_cookie=1f7e55c4983bb069c04be7dee7e5a48e
  16. https://www.flickr.com/groups/10millionphotos/%7Bfaq%7D
  17. https://www.flickr.com/about
  18. https://www.flickr.com/account/upgrade/pro
  19. https://www.flickr.com/change_language.gne?lang=de-de&magic_cookie=1f7e55c4983bb069c04be7dee7e5a48e
  20. https://www.flickr.com/groups/*/lightbox/
How to solve this?

Ensure that the HttpOnly flag is set for all cookies.

What does this mean?

A cookie has been set without the SameSite attribute, which means that the cookie can be sent as a result of a 'cross-site' request. The SameSite attribute is an effective counter measure to cross-site request forgery, cross-site script inclusion, and timing attacks.

Where exactly is this vulnerability found?
  1. https://www.flickr.com/yss_fragment.gne
  2. https://www.flickr.com/change_language.gne?lang=ko-kr&magic_cookie=1f7e55c4983bb069c04be7dee7e5a48e
  3. https://www.flickr.com/change_language.gne?lang=de-de&magic_cookie=1f7e55c4983bb069c04be7dee7e5a48e
  4. https://www.flickr.com/groups/10millionphotos/%7Burl%7D
  5. https://www.flickr.com/change_language.gne?lang=es-us&magic_cookie=1f7e55c4983bb069c04be7dee7e5a48e
  6. https://www.flickr.com/services/oembed/?format=json&url=https://www.flickr.com/photos/youpy/
  7. https://www.flickr.com/people/youpy/contacts
  8. https://www.flickr.com/photos/youpy/albums
  9. https://www.flickr.com/search/
  10. https://www.flickr.com/robots.txt
  11. https://www.flickr.com/faves-i_love_u_get_away_from_me/
  12. https://www.flickr.com/photos/youpy/%7Burl%7D
  13. https://www.flickr.com/groups/10millionphotos/%7Burl%7D
  14. https://www.flickr.com/robots.txt
  15. https://www.flickr.com/change_language.gne?lang=ko-kr&magic_cookie=1f7e55c4983bb069c04be7dee7e5a48e
  16. https://www.flickr.com/groups/10millionphotos/%7Bfaq%7D
  17. https://www.flickr.com/create
  18. https://www.flickr.com/services/oembed/?format=json&url=https://www.flickr.com/photos/youpy/
  19. https://www.flickr.com/groups/10millionphotos/%7Bfaq%7D
  20. https://www.flickr.com/photos/youpy/%7Bfaq%7D
How to solve this?

Ensure that the SameSite attribute is set to either 'lax' or ideally 'strict' for all cookies.

What does this mean?

The page includes mixed content, that is content accessed via HTTP instead of HTTPS.

Where exactly is this vulnerability found?
  1. https://www.flickr.com/yss_fragment.gne
How to solve this?

A page that is available over SSL/TLS must be comprised completely of content which is transmitted over SSL/TLS.The page must not contain any content that is transmitted over unencrypted HTTP. This includes content from third party sites.

What does this mean?

The Anti-MIME-Sniffing header X-Content-Type-Options was not set to 'nosniff'. This allows older versions of Internet Explorer and Chrome to perform MIME-sniffing on the response body, potentially causing the response body to be interpreted and displayed as a content type other than the declared content type. Current (early 2014) and legacy versions of Firefox will use the declared content type (if one is set), rather than performing MIME-sniffing.

Where exactly is this vulnerability found?
  1. https://www.flickr.com/services/developer
  2. https://www.flickr.com/tools/
  3. https://www.flickr.com/report_abuse.gne
  4. https://www.flickr.com/services/oembed/?format=xml&url=https://www.flickr.com/photos/youpy/
  5. https://www.flickr.com/abuse
  6. https://www.flickr.com/about
  7. https://www.flickr.com/services/oembed/?format=json&url=https://www.flickr.com/photos/youpy/
  8. https://www.flickr.com/services/feeds/photos_public.gne?format=atom&id=53005683@N00&lang=en-us
  9. https://www.flickr.com/photos/archivesact/6011019532/nearby/
  10. https://www.flickr.com/yss_fragment.gne
  11. https://www.flickr.com/opensearch.xml
  12. https://www.flickr.com/map
  13. https://www.flickr.com/people/youpy/contacts
  14. https://www.flickr.com/commons
  15. https://www.flickr.com/robots.txt
  16. https://www.flickr.com/cameras
How to solve this?

Ensure that the application/web server sets the Content-Type header appropriately, and that it sets the X-Content-Type-Options header to 'nosniff' for all web pages.If possible, ensure that the end user uses a standards-compliant and modern web browser that does not perform MIME-sniffing at all, or that can be directed by the web application/web server to not perform MIME-sniffing.

Medium risk vulnerabilities

What does this mean?

Web browser data loading may be possible, due to a Cross Origin Resource Sharing (CORS) misconfiguration on the web server

Where exactly is this vulnerability found?
  1. https://combo.staticflickr.com/ap/build/stylesheets/rollup-d96ec0eb.css
How to solve this?

Ensure that sensitive data is not available in an unauthenticated manner (using IP address white-listing, for instance).Configure the 'Access-Control-Allow-Origin' HTTP header to a more restrictive set of domains, or remove all CORS headers entirely, to allow the web browser to enforce the Same Origin Policy (SOP) in a more restrictive manner.

What does this mean?

script-src includes unsafe-inline.

Where exactly is this vulnerability found?
  1. https://www.flickr.com/signin/
  2. https://www.flickr.com/report_abuse.gne
  3. https://www.flickr.com/abuse
  4. https://www.flickr.com/change_language.gne?lang=it-it&magic_cookie=1f7e55c4983bb069c04be7dee7e5a48e
  5. https://www.flickr.com/change_language.gne?lang=pt-br&magic_cookie=1f7e55c4983bb069c04be7dee7e5a48e
  6. https://www.flickr.com/signin
  7. https://www.flickr.com/tools/
  8. https://www.flickr.com/change_language.gne?lang=vn-vn&magic_cookie=1f7e55c4983bb069c04be7dee7e5a48e
  9. https://www.flickr.com/change_language.gne?lang=es-us&magic_cookie=1f7e55c4983bb069c04be7dee7e5a48e
  10. https://www.flickr.com/change_language.gne?csrf&lang=en-US
  11. https://www.flickr.com/change_language.gne?lang=de-de&magic_cookie=1f7e55c4983bb069c04be7dee7e5a48e
  12. https://www.flickr.com/change_language.gne?lang=ko-kr&magic_cookie=1f7e55c4983bb069c04be7dee7e5a48e
  13. https://www.flickr.com/map
  14. https://www.flickr.com/upload
  15. https://www.flickr.com/yss_fragment.gne
  16. https://www.flickr.com/change_language.gne?lang=fr-fr&magic_cookie=1f7e55c4983bb069c04be7dee7e5a48e
  17. https://www.flickr.com/change_language.gne?lang=zh-hk&magic_cookie=1f7e55c4983bb069c04be7dee7e5a48e
  18. https://www.flickr.com/change_language.gne?lang=id-id&magic_cookie=1f7e55c4983bb069c04be7dee7e5a48e
  19. https://www.flickr.com/change_language.gne?lang=en-us&magic_cookie=1f7e55c4983bb069c04be7dee7e5a48e
  20. https://www.flickr.com/signup
How to solve this?

Ensure that your web server, application server, load balancer, etc. is properly configured to set the Content-Security-Policy header.

What does this mean?

The following directives either allow wildcard sources (or ancestors), are not defined, or are overly broadly defined: form-actionThe directive(s): form-action are among the directives that do not fallback to default-src, missing/excluding them is the same as allowing anything.

Where exactly is this vulnerability found?
  1. https://www.flickr.com/photos/archivesact/6011019532/nearby/
  2. https://www.flickr.com/map
  3. https://www.flickr.com/%7Burl%7D
  4. https://www.flickr.com/services/oauth/
  5. https://www.flickr.com/cameras
  6. https://www.flickr.com/photos/youpy/%7Bfaq%7D
  7. https://www.flickr.com/change_language.gne?lang=zh-hk&magic_cookie=1f7e55c4983bb069c04be7dee7e5a48e
  8. https://www.flickr.com/change_language.gne?lang=es-us&magic_cookie=1f7e55c4983bb069c04be7dee7e5a48e
  9. https://www.flickr.com/change_language.gne?lang=fr-fr&magic_cookie=1f7e55c4983bb069c04be7dee7e5a48e
  10. https://www.flickr.com/upload
  11. https://www.flickr.com/signup
  12. https://www.flickr.com/faves-i_love_u_get_away_from_me/
  13. https://www.flickr.com/tools/demos/%7Bfaq%7D
  14. https://www.flickr.com/change_language.gne?lang=id-id&magic_cookie=1f7e55c4983bb069c04be7dee7e5a48e
  15. https://www.flickr.com/help/forum
  16. https://www.flickr.com/people/youpy/contacts
  17. https://www.flickr.com/groups/10millionphotos/%7Burl%7D
  18. https://www.flickr.com/about
  19. https://www.flickr.com/change_language.gne?lang=en-us&magic_cookie=1f7e55c4983bb069c04be7dee7e5a48e
  20. https://www.flickr.com/change_language.gne?lang=pt-br&magic_cookie=1f7e55c4983bb069c04be7dee7e5a48e
How to solve this?

Ensure that your web server, application server, load balancer, etc. is properly configured to set the Content-Security-Policy header.

What does this mean?

The identified library YUI, version 2.5.1 is vulnerable.

Where exactly is this vulnerability found?
  1. https://combo.staticflickr.com/pw/javascript/fold_main.js.v23.1669684430.64
  2. https://combo.staticflickr.com/pw/javascript/fold_main.js.v23.1669684429.64
How to solve this?

Please upgrade to the latest version of YUI.

High risk vulnerabilities

Manual inspection results

This site has not been manually inspected yet. Please apply for an inspection here

Find this WSO report online:

Environment info

------------------

Other

OpenSearch (['/opensearch.xml'])
Open-Graph-Protocol (website)
Script (['application/ld+json', 'text/javascript'])
HTML5
X-XSS-Protection (1; mode=block)
Cookies (xb)
Email (['general@2x-19baca12.png', 'icons@2x-0fdea6e9.png', 'scrappy@2x-40d69d9a.png', 'u002F802d7a4fd3f743ec907da8badf47bec3@o1378064.ingest.sentry.io'])
[ 6 more ]
See hacks, ports, leaked data and possible attack routes for www.flickr.com

Idyllum Labs is on a mission

------------------

Is the code hosted at www.flickr.com vulnerable to cybersecurity attacks? Are the used systems up to date and respecting the security standards of 2022?

We at Idyllum Labs wanted to find out! That is why we built this automated website security scanner and generated this report.

Please note

This is an automated and unbiased website vulnerability scan for the domain www.flickr.com and has nothing to do with human subjectivity, thoughts, opinions, or relationships.

Our cloud-based infrastructure crawls the internet using a mixture of OWASP ZAP, Nmap, Whatweb, and other great software to detect website security issues. We display this data for educational purposes - to give security guidelines for anyone interested in building a safer web environment.

If you have comments, don't agree with the results, or want to submit a site for manual examination, don't hesitate to contact us.


Run a free OWASP ZAP scan for any website at Idyllum.com!

What next?

------------------

Dig deeper

  1. Log in or create a free account to gain access to this report in its entirety.
  2. Use our dashboard to automate security testing and set up automatic monitoring for your website portfolio.
  3. Scan a new domain or initiate a rescan for this domain.

Join our ranks

  1. Use these insights to build your systems bullet-proof.
  2. Explore our datasets and compare your results.
  3. Drop us a line! Help us expand our code or cloud or just say hi!
  4. Support the cause - your donation helps to keep this service free and unbiased.