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

Website security scan results for www.123seguro.com.ar

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

At a glance

------------------
Site scanned: www.123seguro.com.ar
Date of scan: May 9, 2022, 5:11 p.m.

Risk level: HIGH
SSL Status: [!!] SSL Issues found. Traffic to site is not properly encrypted. Please address the issue immediately!

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

Server

------------------
IP: 3.132.244.161
Location: United States
Web server: istio-envoy

Open ports for www.123seguro.com.ar (Nmap scan)

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

OWASP ZAP scan results

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

Informative alerts

What does this mean?

The Content-Type header was either missing or empty.

Where exactly is this vulnerability found?
  1. https://www.123seguro.com.ar/cotizar/
How to solve this?

Ensure each page is setting the specific and appropriate content-type value for the content being delivered.

What does this mean?

Warnings:1:177: The block-all-mixed-content directive is an experimental directive that will be likely added to the CSP specification.1:884: The upgrade-insecure-requests directive is an experimental directive that will be likely added to the CSP specification.

Where exactly is this vulnerability found?
  1. https://www.123seguro.com.ar/ar/plus/solicitar-acceso/
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.zurich.com.ar/es-ar/boton-de-arrepentimiento
How to solve this?

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

What does this mean?

A WSDL File has been detected.

Where exactly is this vulnerability found?
  1. https://www.123seguro.com.ar/sitemap.xml
How to solve this?

Make your WSDL files visible only for technical issues (ex: testing purposes).

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.123seguro.com.ar/jobs/it/senior-software-engineer
  2. https://www.123seguro.com.ar/jobs/it/automation-engineer
  3. https://www.123seguro.com.ar/jobs/customer-service/asesor-atencion-cliente
  4. https://www.123seguro.com.ar/jobs/it/senior-devops-engineer
  5. https://www.123seguro.com.ar/jobs
  6. https://www.123seguro.com.ar/jobs/sales/asesor-comercial
  7. https://www.123seguro.com.ar/ar/plus/solicitar-acceso/
  8. https://www.123seguro.com.ar/jobs/it/quality-analyst
  9. https://www.123seguro.com.ar/jobs/it/senior-backend-engineer
  10. https://www.123seguro.com.ar/jobs/it/senior-front-end-engineer
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?

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

Where exactly is this vulnerability found?
  1. https://servicios.mercantilandina.com.ar/asegurados/
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 web/application server is leaking information via one or more 'X-Powered-By' HTTP response headers. Access to such information may facilitate attackers identifying other frameworks/components your web application is reliant upon and the vulnerabilities such components may be subject to.

Where exactly is this vulnerability found?
  1. https://www.123seguro.com.ar/aseguradoras/allianz
  2. https://www.123seguro.com.ar/preguntas-frecuentes/seguro-de-comercio
  3. https://www.123seguro.com.ar/jobs/customer-service/asesor-atencion-cliente
  4. https://www.123seguro.com.ar/_next/static/chunks/webpack-27dc4b3a2b1eac3a.js
  5. https://www.123seguro.com.ar/terminos-y-condiciones/undefined
  6. https://www.123seguro.com.ar/aseguradoras/mercantil-andina
  7. https://www.123seguro.com.ar/jobs/it/quality-analyst
  8. https://www.123seguro.com.ar/aseguradoras/orbis
  9. https://www.123seguro.com.ar/jobs/it/senior-front-end-engineer
  10. https://www.123seguro.com.ar/aseguradoras/galeno
  11. https://www.123seguro.com.ar/_next/static/chunks/pages/nosotros-6a0b128ca224fd5d.js
  12. https://www.123seguro.com.ar/jobs/it/senior-backend-engineer
  13. https://www.123seguro.com.ar/contacto/
  14. https://www.123seguro.com.ar/undefined
  15. https://www.123seguro.com.ar/preguntas-frecuentes/seguro-de-auto
  16. https://www.123seguro.com.ar/aseguradoras/experta
  17. https://www.123seguro.com.ar/_next/static/chunks/pages/seguros-para-autos-e1f1d2ff866baf0e.js
  18. https://www.123seguro.com.ar/static/apple-touch-icon.png
  19. https://www.123seguro.com.ar/_next/static/chunks/307-b27850c51dc321b6.js
  20. https://www.123seguro.com.ar/_next/static/chunks/790-c632ab1c39b9720c.js
How to solve this?

Ensure that your web server, application server, load balancer, etc. is configured to suppress 'X-Powered-By' headers.

What does this mean?

Server leaks information via 'X-AspNet-Version'/'X-AspNetMvc-Version' HTTP response header field(s).

Where exactly is this vulnerability found?
  1. https://asegurados.orbiseguros.com.ar/
How to solve this?

Configure the server so it will not return those headers.

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.123seguro.com.ar/aseguradoras/provincia
  2. https://www.123seguro.com.ar/seguros/comercio/cotizar/0/categoria
  3. https://www.123seguro.com.ar/aseguradoras/prudencia
  4. https://www.123seguro.com.ar/preguntas-frecuentes/seguro-de-vida
  5. https://www.123seguro.com.ar/static/favicon-32x32.png
  6. https://www.123seguro.com.ar/preguntas-frecuentes
  7. https://www.123seguro.com.ar/jobs
  8. https://www.123seguro.com.ar/aseguradoras/galeno
  9. https://www.123seguro.com.ar/autogestion/site.webmanifest
  10. https://www.123seguro.com.ar/_next/static/chunks/pages/contacto-5580968ee5a03e0e.js
  11. https://www.123seguro.com.ar/aseguradoras/sura
  12. https://www.123seguro.com.ar/seguros/auto/cotizar/0/busqueda-patente
  13. https://www.123seguro.com.ar/seguros/auto
  14. https://www.123seguro.com.ar/sitemap.xml
  15. https://www.123seguro.com.ar/static/site.webmanifest
  16. https://www.123seguro.com.ar/aseguradoras
  17. https://www.123seguro.com.ar/_next/static/-DIBOvIVlkmcqyfQDPxog/_middlewareManifest.js
  18. https://www.123seguro.com.ar/_next/static/chunks/framework-dc33c0b5493501f0.js
  19. https://www.123seguro.com.ar/_next/static/-DIBOvIVlkmcqyfQDPxog/_buildManifest.js
  20. https://www.123seguro.com.ar/autogestion/static/js/2.bebd5766.chunk.js
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://www.123seguro.com.ar/autogestion/static/js/2.bebd5766.chunk.js
  2. https://www.123seguro.com.ar/autogestion/favicon-16x16.png
  3. https://www.123seguro.com.ar/autogestion/site.webmanifest
  4. https://www.123seguro.com.ar/autogestion/favicon.ico
  5. https://www.123seguro.com.ar/autogestion/static/js/main.0695e577.chunk.js
  6. https://www.123seguro.com.ar/autogestion/
  7. https://www.123seguro.com.ar/autogestion/apple-touch-icon.png
  8. https://www.123seguro.com.ar/autogestion/safari-pinned-tab.svg
  9. https://www.123seguro.com.ar/autogestion/favicon-32x32.png
  10. https://www.123seguro.com.ar/autogestion/manifest.json
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.123seguro.com.ar/ar/plus/solicitar-acceso/
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?

style-src includes unsafe-inline.

Where exactly is this vulnerability found?
  1. https://www.123seguro.com.ar/ar/plus/solicitar-acceso/
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.123seguro.com.ar/ar/plus/solicitar-acceso/
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?

X-Frame-Options header is not included in the HTTP response to protect against 'ClickJacking' attacks.

Where exactly is this vulnerability found?
  1. https://www.123seguro.com.ar/aseguradoras/zurich
  2. https://www.123seguro.com.ar/
  3. https://www.123seguro.com.ar/plus
  4. https://www.123seguro.com.ar/jobs/sales/asesor-comercial
  5. https://www.123seguro.com.ar/jobs/it/senior-devops-engineer
  6. https://www.123seguro.com.ar/autogestion/
  7. https://www.123seguro.com.ar/aseguradoras/sancor
  8. https://www.123seguro.com.ar/seguros/comercio/cotizar/0/categoria
  9. https://www.123seguro.com.ar/aseguradoras/prudencia
  10. https://www.123seguro.com.ar/seguros/vida
  11. https://www.123seguro.com.ar/nosotros
  12. https://www.123seguro.com.ar/contacto
  13. https://www.123seguro.com.ar/aseguradoras/galeno
  14. https://www.123seguro.com.ar/aseguradoras/mapfre
  15. https://www.123seguro.com.ar/jobs/it/automation-engineer
  16. https://www.123seguro.com.ar/aseguradoras
  17. https://www.123seguro.com.ar/contacto/
  18. https://www.123seguro.com.ar/jobs/it/senior-software-engineer
  19. https://www.123seguro.com.ar/aseguradoras/meridional
  20. https://www.123seguro.com.ar/seguros/auto
How to solve this?

Most modern Web browsers support the X-Frame-Options HTTP header. Ensure it's set on all web pages returned by your site (if you expect the page to be framed only by pages on your server (e.g. it's part of a FRAMESET) then you'll want to use SAMEORIGIN, otherwise if you never expect the page to be framed, you should use DENY. ALLOW-FROM allows specific websites to frame the web page in supported web browsers).

High risk vulnerabilities

What does this mean?

*** EXPERIMENTAL ***This website uses ASP.NET's Viewstate but maybe without any MAC.

Where exactly is this vulnerability found?
  1. https://asegurados.orbiseguros.com.ar/
How to solve this?

Ensure the MAC is set for all pages on this website.

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

Script (['application/json'])
UncommonHeaders (x-envoy-upstream-service-time)
HTML5
Content-Language (ar)
Cookies (next-i18next)
X-Powered-By (Next.js)
Email (['clientes.argentina@123seguro.com'])
[ 2 more ]
See hacks, ports, leaked data and possible attack routes for www.123seguro.com.ar

Idyllum Labs is on a mission

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

Is the code hosted at www.123seguro.com.ar 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.123seguro.com.ar 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.