Gitforwindows vulnerabilitiesNone on the known-exploited list.
Gitforwindows has 3 published vulnerabilities across 1 product in our catalogue. None of them is on the list of flaws known to be exploited today. The most affected product is Git, with 3. If you run Gitforwindows software, patch the exploited flaws first.
We keep watching the known-exploited list.
Which Gitforwindows products have the most vulnerabilities?
Git leads with 3 published vulnerabilities. Open a product to see its versions and which of its flaws criminals are already using.
Which Gitforwindows vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Gitforwindows's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Gitforwindows flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 48%CVE-2018-11235High
In Git before 2.13.7, 2.14.x before 2.14.4, 2.15.x before 2.15.2, 2.16.x before 2.16.4, and 2.17.x before 2.17.1, remote code execution can occur.
- 1.4%CVE-2021-46101High
In Git for windows through 2.34.1 when using git pull to update the local warehouse, git.cmd can be run directly.
- 0.4%CVE-2022-31012High
Git for Windows is a fork of Git that contains Windows-specific patches.
All Gitforwindows products we track.
1 products, most vulnerabilities first. Find the ones you run, then open a product to see its versions and exploited flaws.
Running Gitforwindows? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
In Git before 2.13.7, 2.14.x before 2.14.4, 2.15.x before 2.15.2, 2.16.x before 2.16.4, and 2.17.x before 2.17.1, remote code execution can occur. With a crafted .gitmodules file, a malicious project can execute an arbitrary script on a machine that runs "git clone --recurse-submodules" because submodule "names" are obtained from this file, and then appended to $GIT_DIR/modules, leading to directory traversal with "../" in a name. Finally, post-checkout hooks from a submodule are executed, bypassing the intended design in which hooks are not obtained from a remote server.
- Matched to
- Git on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
Our catalogue lists 3 published vulnerabilities across 1 product and 3 versions from Gitforwindows.
None of Gitforwindows's vulnerabilities is on the list of flaws known to be exploited today.
Git, with 3 published vulnerabilities. Its own page lists the ones known to be exploited.
Create a Precursor Intelligence account and track the Gitforwindows products you run. We match them against every published flaw, give each one a risk score from 0 to 100 and tell you as soon as we spot one that affects you, by email, in the app or by webhook.