CVE-2016-10549
Version 0.12.7 and lower have 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.
Does this matter?
Lower severity and a low EPSS score (0.65%). Track it; it rarely justifies an emergency change on its own.
Description
Sails is an MVC style framework for building realtime web applications. Version 0.12.7 and lower have 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.
- CVSS 3.0
- 4.4 MEDIUMCVSS:3.0/AV:N/AC:H/PR:L/UI:R/S:C/C:L/I:L/A:N
- EPSS
- 0.65% probability · 49th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-284, CWE-79
- Affected
- sailsjs/sails
- Source
- support@hackerone.com
References
- http://sailsjs.org/documentation/concepts/security/corsVendor Advisory
- http://sailsjs.org/documentation/reference/configuration/sails-config-corsVendor Advisory
- https://nodesecurity.io/advisories/148Third Party Advisory
- http://sailsjs.org/documentation/concepts/security/corsVendor Advisory
- http://sailsjs.org/documentation/reference/configuration/sails-config-corsVendor Advisory
- https://nodesecurity.io/advisories/148Third Party Advisory
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.