Skip to content
Fencer Intel
high 7.5

CVE-2019-25073 json

Path traversal in github.com/goadesign/goa

published 5y ago modified 4mo ago also GHSA-fjgq-224f-fq37 , GO-2020-0032 , EUVD-2022-7619

cvss
7.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.5%
EPSS 1.5% chance of exploitation in 30 days, percentile 74%
public exploits
0
none known

Summary

Improper path sanitization in github.com/goadesign/goa before v3.0.9, v2.0.10, or v1.4.3 allow remote attackers to read files outside of the intended directory.

Patch / fix

  • go github.com/goadesign/goa 1.4.3
  • go goa.design/goa 1.4.3
  • go goa.design/goa/v3 3.0.9
  • github.com/goadesign/goa github.com/goadesign/goa 1.4.3
  • goa.design/goa goa.design/goa 1.4.3
  • goa.design/goa/v3 goa.design/goa/v3 3.0.9

Is CVE-2019-25073 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
last yr.

Exploit prediction

1.50% chance of exploitation in the next 30 days, higher than 74% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/goadesign/goa/pull/2388 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CISA ADP 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
CNA 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
GitHub 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
go github.com/goadesign/goa
<1.4.3
1.4.3
go goa.design/goa
<1.4.3
1.4.3
go goa.design/goa/v3
<3.0.9
3.0.9

Affected products

  • github.com/goadesign/goa github.com/goadesign/goa
  • goa.design/goa goa.design/goa
  • goa.design/goa/v3 goa.design/goa/v3

Classification

Weakness
  • CWE-22 Improper Limitation of a Pathname to a Restricted Directory

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.