Advisory Database
  • Advisories
  • Dependency Scanning
  1. npm
  2. ›
  3. sails
  4. ›
  5. GMS-2016-74

GMS-2016-74: Broken CORS

October 20, 2016

Sails has an issue with the CORS configuration where the value of the origin header is reflected as the value for the Access-Control-Allow-Origin header. This would allow an attacker to make AJAX requests to vulnerable hosts through cross site scripting or a malicious HTML Document, effectively bypassing the Same Origin Policy. Note that this is only an issue when allRoutes is set to true and origin is set to * or left commented out in the sails CORS config file. The problem can be compounded when the cors credentials setting is not provided. At that point authenticated cross domain requests are possible.

References

  • sailsjs.org/documentation/concepts/security/cors
  • sailsjs.org/documentation/reference/configuration/sails-config-cors
  • github.com/balderdashy/sails/commit/ca43e0507af79f15361789a3489013b01c8e1825

Code Behaviors & Features

Detect and mitigate GMS-2016-74 with GitLab Dependency Scanning

Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →

Affected versions

All versions before 0.12.7

Fixed versions

  • 0.12.7

Solution

When using Sails make sure to double check your CORS configuration. A misconfiguration in a production environment will result in a error message being written to the node process console upon application start in versions 0.12.7 and higher.

Source file

npm/sails/GMS-2016-74.yml

Spotted a mistake? Edit the file on GitLab.

  • Site Repo
  • About GitLab
  • Terms
  • Privacy Statement
  • Contact

Page generated Wed, 14 May 2025 12:14:50 +0000.