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

Web Security Optimization (WSO) report for damaaas.com

Your risk level is

HIGH

Score: 76 / 100
SSL Encryption enforced

The WSO verdict

Below average. The site is generally OK, but either the code is outdated or some essential security measures have been ignored. Please forward this report to your development team. We are sure they can find ways to make it better.

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

bot@idyllum:~$ Scanning: /100

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

This site redirects to

Invalid domain!

Scan results

At a glance
Site scanned: damaaas.com
Risk level: HIGH
WSO score: 76 / 100
Ranks: better than 50.8% of tested sites
Date of scan: April 28, 2021, 12:48 p.m.
SSL Status: SSL Encryption enforced
Total alerts: 282
Verdict
Below average. The site is generally OK, but either the code is outdated or some essential security measures have been ignored. Please forward this report to your development team. We are sure they can find ways to make it better.

Environment info

Server
IP: 147.135.230.33
Location: UNITED STATES
Web server: Apache
CMS
WordPress (5.5.4)
Technology
JQuery
Bootstrap

OWASP ZAP vulnerabilities

Critical vulnerabilities
PASSED All content served over SSL. Including scripts
DETAILS
Why is this important?

Because of this some data might be transferred without encryption.

What does this mean?

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

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.

PASSED Authentication methods are secure!
DETAILS
Why is this important?

Because of this hackers could simply access your system by trying all existing password combinations.

What does this mean?

HTTP basic or digest authentication has been used over an unsecured connection. The credentials can be read and then reused by someone with access to the network.

How to solve this?

Protect the connection using HTTPS or use a stronger authentication mechanism

High risk vulnerabilities
FAILED Absence of Anti-CSRF Tokens

By ignoring this a user of your website could have their accounts completely taken over by clicking on a malicious link and doing nothing else

DETAILS

By ignoring this a user of your website could have their accounts completely taken over by clicking on a malicious link and doing nothing else

What does this mean?

"In a Cross-site request forgery (CSRF) attack, an innocent end user is tricked by an attacker into submitting a web request that they did not intend. This may cause actions to be performed on the website that can include client or server data leakage, change of session state, or manipulation of an end user's account. A cross-site request forgery (CSRF) ( often pronounces sea surf) Without Anti-CSRF (often pronounces sea surf) tokens a malicious site may be able to completely take over your users account. Actions that the malicious site may be able to do can include changing the password or email address of the user, making a purchase or any other user controllable action. This attack can ba launched when a user clicks on a malicious link while logged in to your website in the same web browser."

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://damaaas.com/category/reseau-de-franchises/
  2. https://damaaas.com/mentions-legales/
  3. https://damaaas.com/wp-login.php?reauth=1&redirect_to=https%3A%2F%2Fdamaaas.com%2Fwp-admin%2F
  4. https://damaaas.com/usages/
  5. https://damaaas.com/v1/auth/register
  6. https://damaaas.com/cgu/
  7. https://damaaas.com/relation-franchiseur-franchise-comment-mieux-collaborer/
  8. https://damaaas.com/contact/
  9. https://damaaas.com/ressources-2/
  10. https://damaaas.com/securite/
  11. https://damaaas.com/tarifs/
  12. https://damaaas.com/recrutement/consultant-operationnel-et-fonctionnel-h-f/
  13. https://damaaas.com/
  14. https://damaaas.com/blog/
  15. https://damaaas.com/accueil/la-societe-inagua/
  16. https://damaaas.com/blog/
  17. https://damaaas.com/recrutement/
  18. https://damaaas.com/category/collaboration/
  19. https://www.damaaas.com/v1/index.php/auth/login
  20. https://www.damaaas.com/v1/index.php/auth/login
  21. https://www.damaaas.com/v1/index.php/auth/register
  22. https://www.damaaas.com/v1/index.php/auth/forgot_password/
  23. https://contact.damaaas.com/success-story-ministere-des-armees
  24. https://contact.damaaas.com/demande-de-demo2
  25. https://contact.damaaas.com/inscription-newsletter2
  26. https://contact.damaaas.com/livre-blanc-processus-metier-transformation-digitale
  27. https://contact.damaaas.com/livre-blanc-collaboration
  28. https://contact.damaaas.com/livre-blanc-digitalisation-administrations
  29. https://contact.damaaas.com/success-story-haas-avocats2
  30. https://contact.damaaas.com/success-story-credit-agricole2
  31. https://contact.damaaas.com/livre-blanc-conformite-preventive2
  32. https://contact.damaaas.com/success-story-lagarde-autoclaves1
  33. https://contact.damaaas.com/success-story-credit-agricole-paris
  34. https://contact.damaaas.com/dsi--devenez-le-stratege-de-la-transformation-digitale-de-votre-entreprise1
  35. https://contact.damaaas.com/success-story-banque-populaire
How to solve this?

"Many modern content management systems add these automatically to all user inputs including forms available on the public site. If your site is running on an older CMS version, then simply migrating to the latest release could solve the problem. If you are implementing a custom solution, we would recommend implementing anti-CSRF tokens using a well-known framework or library. As an example, the popular php framworks Laravel and Symfony both include out of the box support for anti-CSRF tokens. Additionally, make sure your application does not use GET requests for actions that change the user account or state. GET requests expose their content in the URL itself and therefore can leak your Anti-CSRF token, which should be considered secret. Therefore, GET requests are not protected by anti-CSRF tokens."

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.

Real world example

"Both Netflix and YouTube were susceptible to CSRF attacks in their early years. In both cases this allowed any attacker to perform nearly all actions of any user - change account information, user details or even fully compromise the account. In 2019 Facebook awarded $25 000 to a security expert who discovered a CSRF vulnerability in their system. According to the researcher, the exploit could have been used to immediately take over user's Facebook account the moment they clicked on a malicious link while logged into Facebook in the same browser."

PASSED No application errors found
DETAILS
Why is this important?

Some parts of code produce errors and these errors are visible.

What does this mean?

Sometimes errors in code are visible to the user. And sometimes these errors give out data about system architecture. While not directly dangerous on its own, this vulnerability can help a hacker to plan and execute an attack. Please be aware that this vulnerability can also be a false positive, if found on a documentation page.

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.

How to solve this?

Please take a look where the alert was found. If possible fix these errors or remove faulty code or pages that are no longer relevant.

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.

Real world example

Most customers find error messages on websites very disturbing. Please address this issue immediately. Fixing this can make a huge difference in customer experience and can save you money.

PASSED Cross-Domain misconfiguration not detected
DETAILS
Why is this important?

Because of this, sensitive data coming from service providers or external databases could be intercepted and stolen.

What does this mean?

Cross-Origin Request Site is an OWASP TOP 10 Security Misconfiguration vulnerability. In the process of enabling information sharing between sites, people tend to overlook the significance of CORS configuration. As developers or security experts, it's very important that you are aware of this vulnerability and how it can be exploited.

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

How to solve this?

To implement CORS securely, you need to make a validation list that identifies which specific domains can access resources. Then your application can validate against this list when a domain requests access.

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.

PASSED CSP Scanner: script-src unsafe-inline
DETAILS
Why is this important?

What does this mean?

script-src includes unsafe-inline.

How to solve this?

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

PASSED No unsafe inline styles found
DETAILS
Why is this important?

What does this mean?

style-src includes unsafe-inline.

How to solve this?

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

FAILED Information Disclosure - Suspicious Comments

The source code of the tested site contains comments which may contain sensitive data. Like parts of code, url-s or program logic. This could give valuable hints to the potential attacker.

DETAILS

The source code of the tested site contains comments which may contain sensitive data. Like parts of code, url-s or program logic. This could give valuable hints to the potential attacker.

What does this mean?

An attacker who finds these comments can map the application's structure and files, expose hidden parts of the site, and study the fragments of code to reverse engineer the application, which may help develop further attacks against the site.

The response appears to contain suspicious comments which may help an attacker.

Where exactly is this vulnerability found?
  1. https://damaaas.com/vendor/tarteaucitron/tarteaucitron.js
  2. https://damaaas.com/blog/
  3. https://damaaas.com/usages/
  4. https://damaaas.com/wp-content/themes/gtec/application/assets/bootstrap-3.3.7/dist/js/bootstrap.js
  5. https://damaaas.com/securite/
  6. https://damaaas.com/wp-content/themes/gtec/js/slick.js?ver=1
  7. https://damaaas.com/accueil/la-societe-inagua/
  8. https://damaaas.com/category/reseau-de-franchises/
  9. https://damaaas.com/
  10. https://damaaas.com/wp-content/themes/gtec/application/assets/scripts/minified/jquery.js
  11. https://damaaas.com/cgu/
  12. https://damaaas.com/wp-content/themes/gtec/application/assets/scripts/minified/validator.min.js
  13. https://damaaas.com/wp-content/plugins/monarch/js/custom.js?ver=1.4.14
  14. https://damaaas.com/mentions-legales/
  15. https://damaaas.com/wp-includes/js/jquery/jquery.js?ver=1.12.4-wp
  16. https://damaaas.com/recrutement/consultant-operationnel-et-fonctionnel-h-f/
  17. https://damaaas.com/tarifs/
  18. https://damaaas.com/wp-login.php?reauth=1&redirect_to=https%3A%2F%2Fdamaaas.com%2Fwp-admin%2F
  19. https://damaaas.com/relation-franchiseur-franchise-comment-mieux-collaborer/
  20. https://damaaas.com/wp-content/themes/gtec/application/assets/scripts/minified/jquery-ui.js
  21. https://www.damaaas.com/v1/application/assets/scripts/dist/masterJS.js?r=1619557542
  22. https://www.damaaas.com/v1/application/assets/scripts/lang/lang_en.js?r=1619293865
  23. https://www.damaaas.com/v1/application/assets/scripts/dist/uidamaaas.js?r=1619557542
  24. https://www.damaaas.com/v1/application/assets/scripts/dist/masterJSext.js?r=1618617815
How to solve this?

We recommend inspecting your source code (even with your browser). Search for words like "BUG", "HACK", "FIXME", "LATER", "TODO" etc. The issues should be clearly visible.

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

Real world example

Comments in code are not dangerous themselves. But if a comment gives an attacker hints about system architecture, SQL injections can soon follow. For Yahoo, this caused the loss of 450,000 login credentials back in 2012.

PASSED Potential IP Addresses Found in the Viewstate
DETAILS
Why is this important?

What does this mean?

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

How to solve this?

Verify the provided information isn't confidential.

FAILED X-Frame-Options Header Not Set

An attacker could add this website as an invisible layer on top of theirs or impersonate your site by showing selected parts of it in their website

DETAILS

An attacker could add this website as an invisible layer on top of theirs or impersonate your site by showing selected parts of it in their website

What does this mean?

This vulnerability may allow an attack that is known as clickjacking. Clickjacking is technique where the user thinks they are performing an action, such a clicking a link, on one site. However, in reality their click is actually used to perform some other action on a site they are logged in from the same web browser. This particular vulnerability may allow an attacker to add your site as an invisible layer over their own website. To the user it looks like they are just browsing a harmless website when in reality all their clicks are actually registered on another logged in website.

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

Where exactly is this vulnerability found?
  1. https://damaaas.com/recrutement/
  2. https://damaaas.com/blog/
  3. https://damaaas.com/usages/
  4. https://damaaas.com/accueil/la-societe-inagua/
  5. https://damaaas.com/
  6. https://damaaas.com/ressources-2/
  7. https://damaaas.com/mentions-legales/
  8. https://damaaas.com/category/collaboration/
  9. https://damaaas.com/contact/
  10. https://damaaas.com/relation-franchiseur-franchise-comment-mieux-collaborer/
  11. https://damaaas.com/securite/
  12. https://damaaas.com/cgu/
  13. https://damaaas.com/category/reseau-de-franchises/
  14. https://damaaas.com/recrutement/consultant-operationnel-et-fonctionnel-h-f/
  15. https://damaaas.com/tarifs/
  16. https://contact.damaaas.com/inscription-newsletter2
  17. https://contact.damaaas.com/success-story-credit-agricole-paris
  18. https://contact.damaaas.com/demande-de-demo2
  19. https://contact.damaaas.com/success-story-haas-avocats2
  20. https://contact.damaaas.com/success-story-banque-populaire
  21. https://contact.damaaas.com/success-story-ministere-des-armees
  22. https://contact.damaaas.com/livre-blanc-digitalisation-administrations
  23. https://contact.damaaas.com/livre-blanc-collaboration
  24. https://contact.damaaas.com/dsi--devenez-le-stratege-de-la-transformation-digitale-de-votre-entreprise1
  25. https://contact.damaaas.com/success-story-lagarde-autoclaves1
  26. https://contact.damaaas.com/success-story-credit-agricole2
  27. https://contact.damaaas.com/livre-blanc-processus-metier-transformation-digitale
  28. https://contact.damaaas.com/livre-blanc-conformite-preventive2
How to solve this?

"Please ensure that your site's content can not be embedded into other sites. If you are running Apache, then all you need to do is add the following line to your site's .htaccess file: Header append X-FRAME-OPTIONS "SAMEORIGIN" If you are running your application on a dedicated server or VPS you can instead modify the httpd.conf file by adding: Header always append X-Frame-Options SAMEORIGIN By specifying the option SAMEORIGIN, you allow the site only to be embedded in itself. If you are not planning on using this, you may also set the option to ""DENY""."

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).

Real world example

In 2010 and 2011 both Twitter and Facebook were vulnerable to a type of clickjacking attack that posted a malicious url to the users Twitter and Facebook account respectively. Friends and followers who clicked on those malicious links were subjected to the same attack. As a result, the attack spread quickly through the social media giants' user bases.

Medium risk vulnerabilities
PASSED Charset properly set
DETAILS
Why is this important?

Because of this an attacker could alter the content on your website.

What does this mean?

To display the text on a page correctly, a browser must know the character set used in the page. It seems that the page header declares a charset different from the charset defined by the body of the page. Therefore, an attacker could manipulate content on the page to be interpreted in an encoding of their choice. For example, if an attacker can control content at the beginning of the page, they could inject script using wrongly encoded text and manipulate some browsers into showing that text.

How to solve this?

Be sure to specify the proper charset in your code. And make sure the character sets used in the page header and body match. This is usually an easy fix.

Real world example

The generic replacement character ("�") is a very visible sign of a charset mismatch.

PASSED Charset Mismatch (Header Versus Meta Content-Type Charset)
DETAILS
Why is this important?

What does this mean?

This check identifies responses where the HTTP Content-Type header declares a charset different from the charset defined by the body of the HTML or XML. When there's a charset mismatch between the HTTP header and content body Web browsers can be forced into an undesirable content-sniffing mode to determine the content's correct character set.An attacker could manipulate content on the page to be interpreted in an encoding of their choice. For example, if an attacker can control content at the beginning of the page, they could inject script using UTF-7 encoded text and manipulate some browsers into interpreting that text.

How to solve this?

Force UTF-8 for all text content in both the HTTP header and meta tags in HTML or encoding declarations in XML.

FAILED Cookie No HttpOnly Flag
DETAILS

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://damaaas.com/wp-login.php?reauth=1&redirect_to=https%3A%2F%2Fdamaaas.com%2Fwp-admin%2F
  2. https://contact.damaaas.com/success-story-credit-agricole2
  3. https://contact.damaaas.com/demande-de-demo2
  4. https://contact.damaaas.com/success-story-credit-agricole-paris
  5. https://contact.damaaas.com/inscription-newsletter2
  6. https://contact.damaaas.com/livre-blanc-digitalisation-administrations
  7. https://contact.damaaas.com/inscription-newsletter2
  8. https://contact.damaaas.com/success-story-banque-populaire
  9. https://contact.damaaas.com/success-story-ministere-des-armees
  10. https://contact.damaaas.com/dsi--devenez-le-stratege-de-la-transformation-digitale-de-votre-entreprise1
  11. https://contact.damaaas.com/demande-de-demo2
  12. https://contact.damaaas.com/livre-blanc-collaboration
  13. https://contact.damaaas.com/success-story-haas-avocats2
  14. https://contact.damaaas.com/inscription-newsletter2
  15. https://contact.damaaas.com/success-story-lagarde-autoclaves1
  16. https://contact.damaaas.com/inscription-newsletter2
  17. https://contact.damaaas.com/demande-de-demo2
  18. https://contact.damaaas.com/demande-de-demo2
  19. https://contact.damaaas.com/demande-de-demo2
  20. https://contact.damaaas.com/livre-blanc-processus-metier-transformation-digitale
  21. https://contact.damaaas.com/livre-blanc-conformite-preventive2
How to solve this?

Ensure that the HttpOnly flag is set for all cookies.

FAILED Cookie Without SameSite Attribute

Because of this your stored user preferences could leak to other websites and vice versa.

DETAILS

Because of this your stored user preferences could leak to other websites and vice versa.

What does this mean?

Same-site cookies allow servers to mitigate the risk of CSRF and information leakage attacks by asserting that a particular cookie should only be sent with requests initiated from the same registrable domain.

A cookie has been set with an invalid SameSite attribute value, 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://damaaas.com/wp-login.php?reauth=1&redirect_to=https%3A%2F%2Fdamaaas.com%2Fwp-admin%2F
  2. https://www.damaaas.com/v1/index.php/auth/login
  3. https://contact.damaaas.com/success-story-credit-agricole2
  4. https://contact.damaaas.com/demande-de-demo2
  5. https://contact.damaaas.com/inscription-newsletter2
  6. https://contact.damaaas.com/demande-de-demo2
  7. https://contact.damaaas.com/livre-blanc-collaboration
  8. https://contact.damaaas.com/inscription-newsletter2
  9. https://contact.damaaas.com/demande-de-demo2
  10. https://contact.damaaas.com/inscription-newsletter2
  11. https://contact.damaaas.com/demande-de-demo2
  12. https://contact.damaaas.com/inscription-newsletter2
  13. https://contact.damaaas.com/demande-de-demo2
  14. https://contact.damaaas.com/success-story-banque-populaire
  15. https://contact.damaaas.com/livre-blanc-processus-metier-transformation-digitale
  16. https://contact.damaaas.com/demande-de-demo2
  17. https://contact.damaaas.com/inscription-newsletter2
  18. https://contact.damaaas.com/inscription-newsletter2
  19. https://contact.damaaas.com/demande-de-demo2
  20. https://contact.damaaas.com/success-story-haas-avocats2
  21. https://contact.damaaas.com/success-story-credit-agricole-paris
  22. https://contact.damaaas.com/success-story-lagarde-autoclaves1
How to solve this?

Setting a Same-Site attribute to a cookie is quite simple. It consists of adding just one instruction to the cookie. Simply adding 'SameSite=Lax' or 'SameSite=Strict' is enough!

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

Read more

PASSED All cookies contain secure flags
DETAILS
Why is this important?

Because of this customers accessing your site from insecure or public networks can lose their login details.

What does this mean?

If your important site cookies are transmitted unencrypted, someone could steal them. By stealing an unencrypted session cookie an attacker could just log in as the user. This could easily happen in public WiFi networks.

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

How to solve this?

Please add a “secure” flag to all cookies that contain sensitive information. This way you can protect yourself and your users from eavesdropping.

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.

Real world example

Eavesdropping is the act of secretly or stealthily listening to the private conversation or communications of others without their consent. This type of network attack is generally one of the most effective ones.

FAILED CSP Scanner: Wildcard Directive

By ignoring this, an attacker could completely take over your site.

DETAILS

By ignoring this, an attacker could completely take over your site.

What does this mean?

Content Security Policy (CSP) is an extra layer of security that helps to relieve some types of serious attacks, including Cross Site Scripting (XSS) and data injection. These attacks can range from data theft and distribution of malware to total site takeover.

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, frame-ancestor, font-src, media-src, object-src, manifest-src, worker-src, prefetch-src

Where exactly is this vulnerability found?
  1. https://www.damaaas.com/v1/index.php/auth/forgot_password/
  2. https://www.damaaas.com/v1/index.php/auth/login
  3. https://www.damaaas.com/v1/index.php/auth/login
  4. https://www.damaaas.com/v1/index.php/auth/register
  5. https://www.damaaas.com/v1/index.php/anon/addElementForm/434/1265/dd48fda5e1ab37a5d9ed65a2d922c884fc868e41
How to solve this?

By sending a proper CSP header from a website, you are telling the browser what parts of code it is authorized to execute. This alert shows that the Content Security Policy headers of this webpage are not defined, or are too loosely configured. Please check the code of your website and make sure CSP headers are properly implemented. Many modern systems take care of this automatically, so updating your website could alleviate the issue.

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

Read more

Real world example

In 2017, cybercriminals were able to use listings of dental tools on eBay to extract login credentials from their victims. This was achieved by exploiting a XSS vulnerability.

FAILED Incomplete or No Cache-control and Pragma HTTP Header Set

Because of this your users on public computers could press the back button and view secure pages even after logging out.

DETAILS

Because of this your users on public computers could press the back button and view secure pages even after logging out.

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?
  1. https://damaaas.com/accueil/la-societe-inagua/
  2. https://damaaas.com/category/collaboration/
  3. https://damaaas.com/wp-content/uploads/2020/03/17-onduline-couleur.svg
  4. https://damaaas.com/wp-content/uploads/2020/03/08-lagarde-couleur.svg
  5. https://damaaas.com/wp-content/uploads/2020/03/18-submarine-couleur.svg
  6. https://damaaas.com/wp-content/uploads/2020/03/20-onduclair-couleur.svg
  7. https://damaaas.com/wp-json/
  8. https://damaaas.com/wp-content/uploads/2020/03/09-CA-camca-couleur.svg
  9. https://damaaas.com/wp-content/uploads/2020/03/07-RF-couleur.svg
  10. https://damaaas.com/wp-includes/css/dist/block-library/style.min.css?ver=5.5.4
  11. https://damaaas.com/wp-content/uploads/2020/03/06-CA-assurance.svg
  12. https://damaaas.com/wp-json/oembed/1.0/embed?url=https%3A%2F%2Fdamaaas.com%2Fressources-2%2F
  13. https://damaaas.com/wp-content/uploads/2020/03/19-suballiance.svg
  14. https://damaaas.com/wp-content/uploads/2020/03/20-onduclair.svg
  15. https://damaaas.com/wp-content/uploads/2020/03/14-resourcelab-couleur.svg
  16. https://damaaas.com/wp-json/oembed/1.0/embed?format=xml&url=https%3A%2F%2Fdamaaas.com%2Fressources-2%2F
  17. https://damaaas.com/wp-content/uploads/2020/03/18-submarine.svg
  18. https://damaaas.com/wp-content/uploads/2020/03/03-xerox.svg
  19. https://damaaas.com/wp-json/oembed/1.0/embed?format=xml&url=https%3A%2F%2Fdamaaas.com%2Fusages%2F
  20. https://damaaas.com/mentions-legales/
  21. https://www.damaaas.com/v1/application/assets/less/masterCSSv3.css?r=1619557542
  22. https://contact.damaaas.com/success-story-credit-agricole2
  23. https://contact.damaaas.com/success-story-banque-populaire
  24. https://contact.damaaas.com/success-story-ministere-des-armees
  25. https://contact.damaaas.com/livre-blanc-processus-metier-transformation-digitale
  26. https://contact.damaaas.com/demande-de-demo2
  27. https://contact.damaaas.com/livre-blanc-digitalisation-administrations
  28. https://contact.damaaas.com/success-story-lagarde-autoclaves1
  29. https://contact.damaaas.com/success-story-credit-agricole-paris
  30. https://contact.damaaas.com/success-story-haas-avocats2
  31. https://contact.damaaas.com/livre-blanc-conformite-preventive2
  32. https://contact.damaaas.com/dsi--devenez-le-stratege-de-la-transformation-digitale-de-votre-entreprise1
  33. https://contact.damaaas.com/inscription-newsletter2
  34. https://contact.damaaas.com/livre-blanc-collaboration
How to solve this?

"Please review how your system handles page caching. An software update might help too as many modern content management systems deal have eliminated the issue. If you need to configure this behaviour yourself then on Apache you can add the following directive to your .htaccess file: <IfModule mod_headers.c> Header set Cache-Control ""no-cache, no-store, must-revalidate"" Header set Pragma ""no-cache"" Header set Expires 0 </IfModule> However, please be aware that disabling caching all pages may have a negative impact on page responsiveness. On Debian based system, you can use the following command to make sure mod_headers is loaded: sudo a2enmod headers After enabling the module, you need to restart your server sudo service apache restart Alernatively you may control the Cache-Control headers from your application source code. For instance in php you can set it using the header(); function"

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.

Read more

PASSED No debug errors found
DETAILS
Why is this important?

This could help hackers collect data about your system and better plan an attack.

What does this mean?

It seems that part of the site is still running in development mode and is leaking data. Debug error messages are important for the webmaster but should be turned off for production sites.

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.

How to solve this?

Please turn off debug mode and error messages. This is usually a one minute fix for the developer.

Disable debugging messages before pushing to production.

Real world example

Some of today's systems have incredibly powerful debugging options built in. And these messages can reveal a vast amount of information about the system architecture. Sometimes developers just forget to switch “debug mode” off.

PASSED Session ID exposure not found
DETAILS
Why is this important?

Because of this someone could log in pretending to be your real user.

What does this mean?

Let's say your user logs into your webpage. They find a particularly interesting topic, and copy & paste the URL into an instant message to their friend. Unless the webmaster has taken steps to ensure that there's some form of validation on the session ID, the friend that clicked that link may inherit login access, and then would be able to do anything a user can do, as the user.

A hyperlink pointing to another host name was found. As session ID URL rewrite is used, it may be disclosed in referer header to external hosts.

How to solve this?

Please check that the code does not expose the session ID or that there is proper validation. Updated systems do not usually have this issue.

This is a risk if the session ID is sensitive and the hyperlink refers to an external or third party host. For secure content, put session ID in secured session cookie.

PASSED All content served over HTTPS
DETAILS
Why is this important?

Because of this not all data website traffic is encrypted and information the user enters into the webpage can be leaked.

What does this mean?

Mixed content 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.

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

How to solve this?

Please see your source code (even with the browser). Search for "http://" and load everything over HTTPS. It is an easy and important fix.

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.

FAILED Server Leaks Information via "X-Powered-By" HTTP Response Header Field(s)
DETAILS
PASSED No Session IDs in URL
DETAILS
Why is this important?

What does this mean?

URL rewrite is used to track user session ID. The session ID may be disclosed via cross-site referer header. In addition, the session ID might be stored in browser history or server logs.

How to solve this?

For secure content, put session ID in a cookie. To be even more secure consider using a combination of cookie and URL rewrite.

FAILED Web Browser XSS Protection Not Enabled

Because of this your clients could unknowingly let bad actors into your website.

DETAILS

Because of this your clients could unknowingly let bad actors into your website.

What does this mean?

Cross-site scripting (XSS) is a security exploit which allows an attacker to inject malicious client-side code into a website. This code is executed by the victims and lets the attackers bypass access controls and impersonate users.

Web Browser XSS Protection is not enabled, or is disabled by the configuration of the 'X-XSS-Protection' HTTP response header on the web server

Where exactly is this vulnerability found?
  1. https://damaaas.com/recrutement/
  2. https://damaaas.com/wp-login.php?reauth=1&redirect_to=https%3A%2F%2Fdamaaas.com%2Fwp-admin%2F
  3. https://damaaas.com/recrutement/consultant-operationnel-et-fonctionnel-h-f/
  4. https://damaaas.com/tarifs/
  5. https://damaaas.com/accueil/la-societe-inagua/
  6. https://damaaas.com/category/collaboration/
  7. https://damaaas.com/mentions-legales/
  8. https://damaaas.com/wp-admin/admin-ajax.php
  9. https://damaaas.com/cgu/
  10. https://damaaas.com/category/reseau-de-franchises/
  11. https://damaaas.com/
  12. https://damaaas.com/relation-franchiseur-franchise-comment-mieux-collaborer/
  13. https://damaaas.com/v1/auth/register
  14. https://damaaas.com/contact/
  15. https://damaaas.com/usages/
  16. https://damaaas.com/blog/
  17. https://damaaas.com/ressources-2/
  18. https://damaaas.com/securite/
  19. https://contact.damaaas.com/demande-de-demo2
  20. https://contact.damaaas.com/inscription-newsletter2
  21. https://contact.damaaas.com/success-story-haas-avocats2
  22. https://contact.damaaas.com/success-story-credit-agricole-paris
  23. https://contact.damaaas.com/success-story-banque-populaire
  24. https://contact.damaaas.com/success-story-ministere-des-armees
  25. https://contact.damaaas.com/dsi--devenez-le-stratege-de-la-transformation-digitale-de-votre-entreprise1
  26. https://contact.damaaas.com/livre-blanc-digitalisation-administrations
  27. https://contact.damaaas.com/livre-blanc-collaboration
  28. https://contact.damaaas.com/success-story-lagarde-autoclaves1
  29. https://contact.damaaas.com/success-story-credit-agricole2
  30. https://contact.damaaas.com/livre-blanc-conformite-preventive2
  31. https://contact.damaaas.com/livre-blanc-processus-metier-transformation-digitale
How to solve this?

Fixing this will provide additional protection for users of older web browsers. And the fix can be a small modification in your .htaccess file.

Ensure that the web browser's XSS filter is enabled, by setting the X-XSS-Protection HTTP response header to '1'.

Read more

Real world example

Samy (also known as JS.Spacehero) was a XSS worm that was designed to propagate across the MySpace social-networking site. Within just 20 hours of its release, over one million users had run the payload making Samy the fastest spreading virus of all time.

FAILED X-Content-Type-Options Header Missing

Because of this users could upload potentially harmful code to your website. This is especially dangerous in sites where users can upload anything.

DETAILS

Because of this users could upload potentially harmful code to your website. This is especially dangerous in sites where users can upload anything.

What does this mean?

The X-Content-Type-Options response HTTP header is a marker used by the server to indicate that the file types advertised in the Content-Type headers should not be changed and be followed. This allows to opt-out of MIME type sniffing, or, in other words, it is a way to say that the webmasters knew what they were doing.

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://damaaas.com/wp-content/uploads/2020/03/18-submarine.svg
  2. https://damaaas.com/wp-content/uploads/2020/03/logo-272x90-1.png
  3. https://damaaas.com/category/reseau-de-franchises/
  4. https://damaaas.com/wp-content/uploads/2020/03/QuAOjB9.jpg
  5. https://damaaas.com/wp-content/uploads/2020/09/240_F_133227879_rg3dk9tgHsAKM29IDNex18ht4eyf9SRr.jpg
  6. https://damaaas.com/recrutement/consultant-operationnel-et-fonctionnel-h-f/
  7. https://damaaas.com/wp-content/uploads/2020/03/19-suballiance.svg
  8. https://damaaas.com/tarifs/
  9. https://damaaas.com/wp-content/plugins/monarch/core/admin/fonts/modules.ttf
  10. https://damaaas.com/wp-content/themes/gtec/application/assets/scripts/minified/validator.min.js
  11. https://damaaas.com/wp-content/uploads/2020/03/20-onduclair-couleur.svg
  12. https://damaaas.com/wp-content/uploads/2020/04/connexion.svg
  13. https://damaaas.com/wp-content/themes/gtec/application/assets/scripts/minified/jquery-ui.js
  14. https://damaaas.com/wp-content/uploads/2020/03/09-CA-camca-couleur.svg
  15. https://damaaas.com/wp-content/uploads/2020/03/11-b2pweb.svg
  16. https://damaaas.com/wp-content/uploads/2020/03/fonctionnalite.svg
  17. https://damaaas.com/wp-content/uploads/2020/03/14-resourcelab.svg
  18. https://damaaas.com/wp-content/uploads/2020/03/08-lagarde.svg
  19. https://damaaas.com/wp-includes/wlwmanifest.xml
  20. https://damaaas.com/wp-content/uploads/2020/03/07-RF-couleur.svg
  21. https://www.damaaas.com/v1/index.php/auth/login
  22. https://www.damaaas.com/v1/application/assets/less/masterCSSv3.css?r=1619557542
  23. https://www.damaaas.com/v1/application/assets/scripts/dist/uidamaaas.js?r=1619557542
  24. https://www.damaaas.com/v1/index.php/auth/login
  25. https://www.damaaas.com/v1/index.php/auth/forgot_password/
  26. https://www.damaaas.com/v1/application/assets/scripts/logs.js?r=1587469567
  27. https://www.damaaas.com/v1/application/assets/scripts/dist/masterJSext.js?r=1618617815
  28. https://www.damaaas.com/v1/application/assets/scripts/lang/lang_en.js?r=1619293865
  29. https://www.damaaas.com/v1/application/assets/images/Logo-home.png
  30. https://www.damaaas.com/v1/application/assets/scripts/dist/masterJS.js?r=1619557542
  31. https://www.damaaas.com/v1/index.php/anon/addElementForm/434/1265/dd48fda5e1ab37a5d9ed65a2d922c884fc868e41
  32. https://www.damaaas.com/v1/index.php/auth/register
  33. https://www.damaaas.com/v1/application/assets/images/favicon.ico?v=3
  34. https://contact.damaaas.com/success-story-ministere-des-armees
  35. https://contact.damaaas.com/success-story-lagarde-autoclaves1
  36. https://contact.damaaas.com/livre-blanc-processus-metier-transformation-digitale
  37. https://contact.damaaas.com/success-story-credit-agricole-paris
  38. https://contact.damaaas.com/dsi--devenez-le-stratege-de-la-transformation-digitale-de-votre-entreprise1
  39. https://contact.damaaas.com/success-story-banque-populaire
  40. https://contact.damaaas.com/livre-blanc-digitalisation-administrations
  41. https://contact.damaaas.com/success-story-haas-avocats2
  42. https://contact.damaaas.com/asset/16:temoignage-collaborateur-damaaas-nicolas-loiretpdf
  43. https://contact.damaaas.com/demande-de-demo2
  44. https://contact.damaaas.com/livre-blanc-collaboration
  45. https://contact.damaaas.com/inscription-newsletter2
  46. https://contact.damaaas.com/livre-blanc-conformite-preventive2
  47. https://contact.damaaas.com/success-story-credit-agricole2
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.

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.

Read more

Low risk vulnerabilities
PASSED No loosely scoped cookies found
DETAILS
Why is this important?

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.

How to solve this?

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

Informative alerts
FAILED Cross-Domain JavaScript Source File Inclusion

Because of this some essential parts of the sites code come from third-parties and are therefore not fully under the administrators control. If these sources get hacked or change their behavior you and your customers are at risk.

DETAILS

Because of this some essential parts of the sites code come from third-parties and are therefore not fully under the administrators control. If these sources get hacked or change their behavior you and your customers are at risk.

What does this mean?

For example, your third-party code provider may suddenly decide they want to collect data from end-users of their script, and this data might include cookies, and HTML5 storage data. By including the script on their domain you are allowing them to make these changes without agreement from you.

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

Where exactly is this vulnerability found?
  1. https://damaaas.com/contact/
  2. https://damaaas.com/securite/
  3. https://damaaas.com/cgu/
  4. https://damaaas.com/
  5. https://damaaas.com/mentions-legales/
  6. https://damaaas.com/recrutement/consultant-operationnel-et-fonctionnel-h-f/
  7. https://damaaas.com/tarifs/
  8. https://damaaas.com/blog/
  9. https://damaaas.com/ressources-2/
  10. https://damaaas.com/relation-franchiseur-franchise-comment-mieux-collaborer/
  11. https://damaaas.com/v1/auth/register
  12. https://damaaas.com/category/collaboration/
  13. https://damaaas.com/accueil/la-societe-inagua/
  14. https://damaaas.com/usages/
  15. https://damaaas.com/category/reseau-de-franchises/
  16. https://damaaas.com/recrutement/
  17. https://damaaas.com/mentions-legales/
  18. https://www.damaaas.com/v1/index.php/auth/login
  19. https://www.damaaas.com/v1/index.php/auth/register
  20. https://www.damaaas.com/v1/index.php/auth/login
  21. https://contact.damaaas.com/success-story-lagarde-autoclaves1
  22. https://contact.damaaas.com/success-story-credit-agricole2
  23. https://contact.damaaas.com/success-story-lagarde-autoclaves1
  24. https://contact.damaaas.com/dsi--devenez-le-stratege-de-la-transformation-digitale-de-votre-entreprise1
  25. https://contact.damaaas.com/success-story-haas-avocats2
  26. https://contact.damaaas.com/success-story-ministere-des-armees
  27. https://contact.damaaas.com/livre-blanc-digitalisation-administrations
  28. https://contact.damaaas.com/success-story-banque-populaire
  29. https://contact.damaaas.com/success-story-credit-agricole-paris
  30. https://contact.damaaas.com/success-story-haas-avocats2
  31. https://contact.damaaas.com/demande-de-demo2
  32. https://contact.damaaas.com/inscription-newsletter2
  33. https://contact.damaaas.com/inscription-newsletter2
  34. https://contact.damaaas.com/success-story-credit-agricole-paris
  35. https://contact.damaaas.com/demande-de-demo2
  36. https://contact.damaaas.com/success-story-credit-agricole2
  37. https://contact.damaaas.com/livre-blanc-processus-metier-transformation-digitale
  38. https://contact.damaaas.com/livre-blanc-processus-metier-transformation-digitale
  39. https://contact.damaaas.com/livre-blanc-conformite-preventive2
  40. https://contact.damaaas.com/livre-blanc-conformite-preventive2
How to solve this?

Downloading the code and hosting from your own domain is the safe approach.

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

FAILED CSP Scanner: Notices
DETAILS

What does this mean?

Warnings:1:1: 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.damaaas.com/v1/index.php/anon/addElementForm/434/1265/dd48fda5e1ab37a5d9ed65a2d922c884fc868e41
  2. https://www.damaaas.com/v1/index.php/auth/login
  3. https://www.damaaas.com/v1/index.php/auth/login
  4. https://www.damaaas.com/v1/index.php/auth/forgot_password/
  5. https://www.damaaas.com/v1/index.php/auth/register
How to solve this?

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

Manual inspection results

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

Find this WSO report online:

Please note

Is damaaas.com secure and safe to use?

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

Please understand, that is an automated and unbiased OWASP ZAP based website security scan for damaaas.com and has nothing to do with human subjectivity, thoughts, opinions or relationships.

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!

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..)