CVE-2022-34800 Plaintext Storage of a Password in Jenkins Build Notifications Plugin

Medium 4.3 Published Updated

Attackers with file system access can read unencrypted tokens from Jenkins Build Notifications Plugin configuration files.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
Not needed
Fix
None listed

What is CVE-2022-34800?

CVE-2022-34800 is a medium-severity vulnerability in Jenkins Build Notifications Plugin, published on 30 Jun 2022. Any signed-in user can exploit it over the network, with no action from the victim.

Official description

Jenkins Build Notifications Plugin 1.5.0 and earlier stores tokens unencrypted in its global configuration files on the Jenkins controller where they can be viewed by users with access to the Jenkins controller file system.

Weakness: CWE-522

Which versions are affected by CVE-2022-34800?

2 open source packages ship an affected version, including tools.devnull:build-notifications. It affects 1 product.

PackageAffectedFixed in
tools.devnull:build-notifications MavenAll versions to 1.5.0None
tools.devnull:build-notifications MavenAll versions to 1.5.0None

Products include Jenkins Build Notifications.

How do I fix CVE-2022-34800?

No fix has been published for CVE-2022-34800 yet. Limit exposure of the affected software until one is available.

Is CVE-2022-34800 being exploited?

There is no known exploitation of CVE-2022-34800 in the wild and no public exploit code.

Sources

Also known as GHSA-v3r8-6vfj-pppf.

Is CVE-2022-34800 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free