CVE-2022-4817: A vulnerability was found in centic9 jgit-cookbook

Q: How do I fix CVE-2022-4817?

jgit-cookbook: upgrade to 2022-08-09. Exact commands for each OS are on this page.

Q: Is CVE-2022-4817 being exploited?

CVE-2022-4817 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2022-4817 affect?

CVE-2022-4817 affects jgit-cookbook. Severity is low (CVSS 3.1). A vulnerability was found in centic9 jgit-cookbook. It has been declared as problematic. This vulnerability affects unknown code. The manipulation leads to insecure temporary file. The attack can be initiated remotely. The name of the patch

Q: How urgent is CVE-2022-4817?

Priority 22/100. No elevated risk signals yet.

Routine

LOW 3.1UPGRADE

CVE-2022-4817 is a low-severity flaw (CVSS 3.1) affecting jgit-cookbook. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

A vulnerability was found in centic9 jgit-cookbook. It has been declared as problematic. This vulnerability affects unknown code. The manipulation leads to insecure temporary file. The attack can be initiated remotely. The name of the patch is b8cb29b43dc704708d598c60ac1881db7cf8e9c3. It is recommended to apply a patch to fix this issue. The identifier of this vulnerability is VDB-216988.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	3.1 (Low)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.6% (top 54%)
CISA exploited list	No
Weakness	CWE-377, CWE-668
Published	2022-12-28
Last modified	2026-06-17

Publisher (CNA): VulDB · Vendor: jgit-cookbook project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2022-12-28 19:15 UTCPublished CVE record published
2026-06-17 05:21 UTCUpdated Record last modified

jgit-cookbook project jgit-cookbook UPGRADE

Affected: < 2022-08-09

Fixed in: 2022-08-09

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy jgit-cookbook || rpm -q jgit-cookbook || jgit-cookbook --version

2. UPGRADE to 2022-08-09 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade jgit-cookbook

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade jgit-cookbook

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2022-4817?

jgit-cookbook: upgrade to 2022-08-09. Exact commands for each OS are on this page.

Is CVE-2022-4817 being exploited?

CVE-2022-4817 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2022-4817 affect?

CVE-2022-4817 affects jgit-cookbook. Severity is low (CVSS 3.1). A vulnerability was found in centic9 jgit-cookbook. It has been declared as problematic. This vulnerability affects unknown code. The manipulation leads to insecure temporary file. The attack can be initiated remotely. The name of the patch

How urgent is CVE-2022-4817?

Priority 22/100. No elevated risk signals yet.

References

← Back to latest CVEs