CVE-2023-46402 — git-urls
HIGHCVE-2023-46402 is a high-severity (CVSS 7.5) CWE-1333 vulnerability in github.com/whilp/git-urls. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.
Inefficient Regular Expression Complexity in git-urls
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
github.com/whilp/git-urlsReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
git-urls version 1.0.1 is vulnerable to ReDOS (Regular Expression Denial of Service) in Go package.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/whilp/git-urls | all versions | No fix |
Affected Products
git-urlsgit-urls_projectResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/whilp/git-urls, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of github.com/whilp/git-urls for CVE-2023-46402. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
This vulnerability in the git-urls package requires an attacker to provide malicious input to the git URL parsing function. In Red Hat OpenShift GitOps deployments, git repository URLs are configured exclusively by platform administrators through Application and ApplicationSet custom resources. End users do not have…
To reduce exposure to this vulnerability in OpenShift GitOps: 1. Limit Application and ApplicationSet creation to platform administrators using RBAC. 2. Configure ArgoCD AppProjects with explicit sourceRepos allowlists. Avoid wildcard (*) sources. 3. Use ApplicationSet resource policies to prevent user-provided git URLs from being templated into Applications. 4. In order to Audit which Git repositories are used by GitOps and Validate no untrusted repos are configured use: `oc get applications -A -o jsonpath='{range .items[*]}{.metadata.name}{"\t"}{.spec.source.repoURL}{"\n"}{end}'`Source: Red Hat security advisory for CVE-2023-46402 (CC BY 4.0)
Frequently Asked Questions
Is CVE-2023-46402 in your dependencies?
Find it across Go, including transitive dependencies.