Skip to content

Overly permissive origin policy

High severity GitHub Reviewed Published Dec 11, 2023 in koajs/cors • Updated Dec 12, 2023

Package

npm @koa/cors (npm)

Affected versions

< 5.0.0

Patched versions

5.0.0

Description

Currently, the middleware operates in a way that if an allowed origin is not provided, it will return an Access-Control-Allow-Origin header with the value of the origin from the request. This behavior completely disables one of the most crucial elements of browsers - the Same Origin Policy (SOP), this could cause a very serious security threat to the users of this middleware.

If such behavior is expected, for instance, when middleware is used exclusively for prototypes and not for production applications, it should be heavily emphasized in the documentation along with an indication of the risks associated with such behavior, as many users may not be aware of it.

References

@fengmk2 fengmk2 published to koajs/cors Dec 11, 2023
Published to the GitHub Advisory Database Dec 11, 2023
Reviewed Dec 11, 2023
Published by the National Vulnerability Database Dec 11, 2023
Last updated Dec 12, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Changed
Confidentiality
None
Integrity
High
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N

EPSS score

0.051%
(21st percentile)

Weaknesses

CVE ID

CVE-2023-49803

GHSA ID

GHSA-qxrj-hx23-xp82

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.