How severe is GHSA-g376-whg7-896m?

No CVSS score has been assigned to GHSA-g376-whg7-896m yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-g376-whg7-896m?

GHSA-g376-whg7-896m affects the following packages: yjmyjmyjm (npm). Ecosystems affected: npm.

How do I fix GHSA-g376-whg7-896m?

No patched version of yjmyjmyjm has shipped for GHSA-g376-whg7-896m yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect GHSA-g376-whg7-896m in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for yjmyjmyjm, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-g376-whg7-896m if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Is GHSA-g376-whg7-896m actively exploited in the wild?

No public exploit code has been indexed for GHSA-g376-whg7-896m yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-g376-whg7-896m published, and has it been updated?

GHSA-g376-whg7-896m was published on September 1, 2020 and was last updated on August 31, 2020. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

Directory Traversal in yjmyjmyjmGHSA-g376-whg7-896m

GHSA-g376-whg7-896m is a security vulnerability in yjmyjmyjm. No vendor fix is recorded yet; mitigation options are listed below.

Published

Sep 1, 2020

Updated

Aug 31, 2020

Affected

1 pkg

Patched

None yet

Exploits

None indexed

Exploitation data as of Aug 31, 2020 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

0other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

yjmyjmyjmnpm

20downloads / week

Description

Affected versions of yjmyjmyjm resolve relative file paths, resulting in a directory traversal vulnerability. A malicious actor can use this vulnerability to access files outside of the intended directory root, which may result in the disclosure of private files on the vulnerable system.

Example request:

GET /../../../../../../../../../../etc/passwd HTTP/1.1
host:foo

Recommendation

No patch is available for this vulnerability.

It is recommended that the package is only used for local development, and if the functionality is needed for production, a different package is used instead.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
📦npm	`yjmyjmyjm`	≥ 0.0.0	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for yjmyjmyjm, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of yjmyjmyjm has shipped for GHSA-g376-whg7-896m yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Frequently Asked Questions

Affected versions of `yjmyjmyjm` resolve relative file paths, resulting in a directory traversal vulnerability. A malicious actor can use this vulnerability to access files outside of the intended directory root, which may result in the disclosure of private files on the vulnerable system. Example request: ``` GET /../../../../../../../../../../etc/passwd HTTP/1.1 host:foo ``` ## Recommendation No patch is available for this vulnerability. It is recommended that the package is only used for local development, and if the functionality is needed for production, a different package is used i

O3 Security · Impact-Aware SCA

Is GHSA-g376-whg7-896m in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works