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

bot@idyllum:~$ Please wait, the scan will start shortly

bot@idyllum:~$ Scanning: /100

bot@idyllum:~$ Latest scan is in long queue and may take a while

bot@idyllum:~$ Web Security Optimization (WSO) scan failed! Please try again

This site redirects to

Invalid domain!

Please log in or sign up for a free account to see this report in its entirety!

# Website security scan results for www.jobsaware.co.uk

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

## At a glance

Site scanned: www.jobsaware.co.uk
Risk level: HIGH
WSO score: 57 / 100
Ranks: worse than 100.0% of tested sites
Date of scan: Jan. 14, 2022, 3:19 p.m.
SSL Status: [OK] SSL Encryption enforced
Total alerts: 505

## Verdict

Critically bad! Some serious development work is needed to keep this website and customer data safe. Please forward this report immediately to the webmaster.

# Environment info

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

## Server

IP: 35.246.6.109
Location: United States
Web server: Pepyaka/1.19.10

## CMS

Wix

## Technology

Bootstrap

## Uncategorized

RedirectLocation (https://www.jobsaware.co.uk/)
Strict-Transport-Security (['max-age=120'])
UncommonHeaders (server-timing,x-seen-by,x-wix-request-id,x-content-type-options)
HttpOnly ([['hs'], ['svSession']])
Title (JobsAware - Protecting worker rights)
Email (['605a7baede844d278b89dc95ae0a9123@sentry-next.wixpress.com', 'f1ffc0b5efe04e9eb9762cd808722520@sentry.wixpress.com'])
Cookies (hs)
X-UA-Compatible (['IE=edge'])
Frame
Content-Language (en)
HTML5
MetaGenerator (['Wix.com Website Builder'])
Script (['application/json', 'text/javascript', 'wix/htmlEmbeds'])
Open-Graph-Protocol (website)

# 2 Open ports for www.jobsaware.co.uk (Nmap scan)

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

# OWASP ZAP scan results

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

## Informative alerts

[OK] PASSED Charset Mismatch
[+]
[OK] PASSED Content-Type Header Empty
[+]
[!!] FAILED Content-Type Header Missing
[+]
What does this mean?

The Content-Type header was either missing or empty.

Where exactly is this vulnerability found?
How to solve this?

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

[OK] PASSED CSP: Notices
[+]
[OK] PASSED CSP Scanner: Notices
[+]
[OK] PASSED CSP Scanner: X-Content-Security-Policy
[+]
[OK] PASSED CSP Scanner: X-WebKit-CSP
[+]
[OK] PASSED CSP: X-Content-Security-Policy
[+]
[OK] PASSED CSP: X-WebKit-CSP
[+]
[OK] PASSED Information Disclosure - Sensitive Information in HTTP Referrer Header
[+]
[OK] PASSED Information Disclosure - Sensitive Information in URL
[+]
[!!] FAILED Information Disclosure - Suspicious Comments
[+]
What does this mean?

The response appears to contain suspicious comments which may help an attacker. Note: Matches made within script blocks or files are against the entire content not only comments.

Where exactly is this vulnerability found?
How to solve this?

Remove all comments that return information that may help an attacker and fix any underlying problems they refer to.

[!!] FAILED Loosely Scoped Cookie
[+]
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?
How to solve this?

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

[OK] PASSED Split Viewstate in Use
[+]
[!!] FAILED Timestamp Disclosure - Unix
[+]
What does this mean?

A timestamp was disclosed by the application/web server - Unix

Where exactly is this vulnerability found?
How to solve this?

Manually confirm that the timestamp data is not sensitive, and that the data cannot be aggregated to disclose exploitable patterns.

[OK] PASSED Username Hash Found
[+]
[!!] FAILED WSDL File Detection
[+]
What does this mean?

A WSDL File has been detected.

Where exactly is this vulnerability found?
How to solve this?

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

[OK] PASSED WSDL File Passive Scanner
[+]

## Low risk vulnerabilities

[!!] FAILED Absence of Anti-CSRF Tokens
[+]
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?
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.

[!!] FAILED Application Error Disclosure
[+]
What does this mean?

This page contains an error/warning message that may disclose sensitive information like the location of the file that produced the unhandled exception. This information can be used to launch further attacks against the web application. The alert could be a false positive if the error message is found inside a documentation page.

Where exactly is this vulnerability found?
How to solve this?

Review the source code of this page. Implement custom error pages. Consider implementing a mechanism to provide a unique error reference/identifier to the client (browser) while logging the details on the server side and not exposing them to the user.

[!!] FAILED Cookie No HttpOnly Flag
[+]
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?
How to solve this?

Ensure that the HttpOnly flag is set for all cookies.

[!!] FAILED Cookie Without SameSite Attribute
[+]
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?
How to solve this?

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

[!!] FAILED Cookie Without Secure Flag
[+]
What does this mean?

A cookie has been set without the secure flag, which means that the cookie can be accessed via unencrypted connections.

Where exactly is this vulnerability found?
How to solve this?

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.

[!!] FAILED Cross-Domain JavaScript Source File Inclusion
[+]
What does this mean?

The page includes one or more script files from a third-party domain.

Where exactly is this vulnerability found?
How to solve this?

Ensure JavaScript source files are loaded from only trusted sources, and the sources can't be controlled by end users of the application.

[!!] FAILED Incomplete or No Cache-control and Pragma HTTP Header Set
[+]
What does this mean?

The cache-control and pragma HTTP header have not been set properly or are missing allowing the browser and proxies to cache content.

Where exactly is this vulnerability found?
How to solve this?

Whenever possible ensure the cache-control HTTP header is set with no-cache, no-store, must-revalidate; and that the pragma HTTP header is set with no-cache.

[!!] FAILED Information Disclosure - Debug Error Messages
[+]
What does this mean?

The response appeared to contain common error messages returned by platforms such as ASP.NET, and Web-servers such as IIS and Apache. You can configure the list of common debug messages.

Where exactly is this vulnerability found?
How to solve this?

Disable debugging messages before pushing to production.

[OK] PASSED Old Asp.Net Version in Use
[+]
[!!] FAILED Private IP Disclosure
[+]
What does this mean?

A private IP (such as 10.x.x.x, 172.x.x.x, 192.168.x.x) or an Amazon EC2 private hostname (for example, ip-10-0-56-78) has been found in the HTTP response body. This information might be helpful for further attacks targeting internal systems.

Where exactly is this vulnerability found?
How to solve this?

Remove the private IP address from the HTTP response body. For comments, use JSP/ASP/PHP comment instead of HTML/JavaScript comment which can be seen by client browsers.

[OK] PASSED Referer Exposes Session ID
[+]
[OK] PASSED Secure Pages Include Mixed Content
[+]
[!!] FAILED Server Leaks Information via "X-Powered-By" HTTP Response Header Field(s)
[+]
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?
How to solve this?

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

[OK] PASSED Web Browser XSS Protection Not Enabled
[+]
[!!] FAILED X-AspNet-Version Response Header
[+]
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?
How to solve this?

Configure the server so it will not return those headers.

[!!] FAILED X-Content-Type-Options Header Missing
[+]
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?
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.

[OK] PASSED X-Debug-Token Information Leak
[+]

## Medium risk vulnerabilities

[!!] FAILED Cross-Domain Misconfiguration
[+]
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?
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.

[OK] PASSED CSP Scanner: script-src unsafe-inline
[+]
[OK] PASSED CSP Scanner: style-src unsafe-inline
[+]
[OK] PASSED CSP Scanner: Wildcard Directive
[+]
[OK] PASSED CSP: script-src unsafe-inline
[+]
[OK] PASSED CSP: style-src unsafe-inline
[+]
[!!] FAILED CSP: Wildcard Directive
[+]
What does this mean?

The following directives either allow wildcard sources (or ancestors), are not defined, or are overly broadly defined: script-src, script-src-elem, script-src-attr, style-src, style-src-elem, style-src-attr, img-src, connect-src, frame-src, font-src, media-src, object-src, manifest-src, worker-src, prefetch-src, 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?
How to solve this?

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

[OK] PASSED Emails Found in the Viewstate
[+]
[OK] PASSED HTTP Parameter Override
[+]
[OK] PASSED Insecure JSF ViewState
[+]
[OK] PASSED Multiple X-Frame-Options Header Entries
[+]
[!!] FAILED Potential IP Addresses Found in the Viewstate
[+]
What does this mean?

The following potential IP addresses were found being serialized in the viewstate field:

Where exactly is this vulnerability found?
How to solve this?

Verify the provided information isn't confidential.

[OK] PASSED Session ID in URL Rewrite
[+]
[!!] FAILED Vulnerable JS Library
[+]
What does this mean?

The identified library jquery, version 1.12.4 is vulnerable.

Where exactly is this vulnerability found?
How to solve this?

Please upgrade to the latest version of jquery.

[OK] PASSED Weak Authentication Method
[+]
[OK] PASSED X-Frame-Options Defined via META (Non-compliant with Spec)
[+]
[!!] FAILED X-Frame-Options Header Not Set
[+]
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?
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).

[OK] PASSED X-Frame-Options Setting Malformed
[+]

## High risk vulnerabilities

[OK] PASSED Viewstate without MAC Signature (Sure)
[+]
[!!] FAILED Viewstate without MAC Signature (Unsure)
[+]
What does this mean?

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

Where exactly is this vulnerability found?
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:

# Idyllum Labs is on a mission

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

Is the code hosted at www.jobsaware.co.uk 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.jobsaware.co.uk 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.

It is important to understand that we don't gather business information. We analyze used technology and are not interested in

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.

Want to scan and monitor multiple sites at once?

Create an account
Yes, generating security reports with Idyllum Labs is free!
(Just as all the best things in life..)