Sails Node Module
Approved changes feed: RSS · Atom
cpe:2.3:a:hackerone:sails_node_module:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Hackerone (9b72fff1-532f-502a-8030-14fc4a21dd17) |
|---|---|
| Product | Sails Node Module (5175970f-bf35-54a6-b0ac-a545be60255d) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2016-10549 |
vulnerable | 2026-06-08 05:07:25.299934 |
Details available
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.
Published: 2018-05-31T20:00:00.000Z
Updated: 2024-09-17T01:46:02.640Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.