Security readout for executives and security teams
Plain-English summary
This flaw can let an unauthenticated remote user read files outside the intended directory in applications using vulnerable goa versions. The main business risk is exposure of sensitive local files, configuration, or secrets available to the running service.
Executive priority
Treat as a high-priority dependency remediation for internet-facing Go services using goa. It is not marked as actively exploited here, but unauthenticated file disclosure can expose secrets and accelerate further compromise.
Technical view
CVE-2019-25073 is CWE-22 path traversal caused by improper path sanitization in github.com/goadesign/goa before v3.0.9, v2.0.10, or v1.4.3. The CVSS 3.1 score is 7.5 because it is network reachable, low complexity, unauthenticated, and impacts confidentiality.
Likely exposure
Exposure is most likely in Go services that depend on vulnerable goa module versions and expose affected file access behavior. The provided data does not identify specific downstream products or deployment patterns.
Exploitation context
The source bundle says remote attackers may read files outside the intended directory. It does not provide evidence of active exploitation, and the CVE is not listed as KEV in the provided data.
Researcher notes
Evidence supports path traversal and confidentiality impact, but the provided affected-version metadata is limited. Use the Go advisory, CVE record, linked pull request, and fixing commit to confirm exact module paths and fixed versions.
Mitigation direction
- Upgrade goa dependencies to v3.0.9, v2.0.10, v1.4.3, or later as appropriate.
- Review any goa-based file-serving routes for unintended local file exposure.
- Check vendor guidance and Go vulnerability data before accepting exceptions.
- Redeploy rebuilt services after dependency updates are verified.
Validation and detection
- Inventory Go modules for github.com/goadesign/goa, goa.design/goa, or goa.design/goa/v3.
- Confirm deployed builds use versions at or above the fixed release lines.
- Review dependency lockfiles and build artifacts, not only source manifests.
- Assess whether exposed routes could reach sensitive local files.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupFile access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2019-25073 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N3.93.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/goadesign/goa/pull/2388CVE reference
- https://github.com/goadesign/goa/commit/70b5a199d0f813d74423993832c424e1fc73fb39CVE reference
- https://pkg.go.dev/vuln/GO-2020-0032CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.