Directory Traversal in getcityapi.yoehoehne

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.5 · CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS

• CVE-2017-16192: 1.97% estimated exploitation activity in the next 30 days; percentile 80.48 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Affected versions of getcityapi.yoehoehne 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: 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.

Published by the source

23 Jul 2018, 20:40 UTC

Last modified by the source

8 Nov 2023, 03:59 UTC

Source last checked

26 Oct 2026, 12:26 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-4vcm-qfxh-p6c3

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-4vcm-qfxh-p6c3

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2017-16192

Advisory: Directory Traversal in getcityapi.yoehoehne
IDs: CVE-2017-16192, GHSA-4vcm-qfxh-p6c3
Record: https://patchnext.com/advisories/cve-2017-16192 (revision 2, source checked 26 Oct 2026, 12:26 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm getcityapi.yoehoehne: affected <= 0.0.1

## Suggested inspection (read-only)
- `npm ls getcityapi.yoehoehne --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on getcityapi.yoehoehne.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-4vcm-qfxh-p6c3 (OSV record GHSA-4vcm-qfxh-p6c3 lists affected ranges: npm getcityapi.yoehoehne >=0 <=0.0.1)
- Verified: https://github.com/advisories/GHSA-4vcm-qfxh-p6c3 (GitHub-reviewed advisory GHSA-4vcm-qfxh-p6c3 lists affected ranges: npm getcityapi.yoehoehne >=0 <=0.0.1)

Commands are suggestions: review each one before running it.