Gitforge.Jl
Approved changes feed: RSS · Atom
cpe:2.3:a:juliaweb:gitforge.jl:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Juliaweb (c4614454-faf2-5098-ae2f-92ae80586ec4) |
|---|---|
| Product | Gitforge.Jl (a3b40406-03d8-5a3e-a6d7-1100f96368a8) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2025-50178 |
vulnerable | 2026-06-08 07:31:10.842103 |
GitForge.jl lacks validation for user provided fields
GitForge.jl is a unified interface for interacting with Git "forges." Versions prior to 0.4.3 lack input validation for user provided values in certain functions. In the `GitForge.get_repo` function for GitHub, the user can provide any string for the owner and repo fields. These inputs are not validated or safely encoded and are sent directly to the server. This means a user can add path traversal patterns like `../` in the input to access any other endpoints on api.github.com that were not intended. Version 0.4.3 contains a patch for the issue. No known workarounds are available.
Published: 2025-06-25T15:12:24.751Z
Updated: 2025-06-25T15:20:43.040Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.