Skip to content
This repository has been archived by the owner on Jan 31, 2024. It is now read-only.

lodash template injection vulnerability

Low
dudeisbrendan03 published GHSA-mxcq-9jpq-cgwv Jun 27, 2021

Package

npm big-oauth2 (npm)

Affected versions

< 0.2.14

Patched versions

0.2.15

Description

Impact

What kind of vulnerability is it? Who is impacted?

An injection vulnerability been know to exist in lodash for a period of 2 months, this does not affect any users since we do not utilise templates (neither to dependencies) or lodash directly.

Patches

Has the problem been patched? What versions should users upgrade to?

This dependency has been updated to resolve the issue, you can manually upgrade the dependency yourself or get the new release to resolve the issue.

Workarounds

Is there a way for users to fix or remediate the vulnerability without upgrading?

Manually updating the lodash package will resolve the issue, refer to npm documentation.

References

Are there any links users can visit to find out more?

See an example of the vulnerability and more information on Snyk

For more information

If you have any questions or comments about this advisory:

Severity

Low

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
Local
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
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:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N

CVE ID

No known CVE

Weaknesses

No CWEs