Skype NotifierApplication · Jenkins
CVE-2022-34805
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedJenkins Skype notifier Plugin 1.1.0 and earlier stores a password unencrypted in its global configuration file on the Jenkins controller where it can be viewed by users with access to the Jenkins controller file system.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Jenkins Skype notifier Plugin versions 1.1.0 and earlier stores passwords in plain text (unencrypted) within its global configuration file on the Jenkins controller filesystem. Any user with access to the Jenkins controller's file system can read this configuration file and obtain the stored password in cleartext.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Skype NotifierApplication
<= 1.1.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if Skype Notifier Plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed, or list contents of $JENKINS_HOME/plugins/ directory and look for a folder named 'skype-notifier' or similarAffected if The plugin is installed and the folder name or version metadata shows version 1.1.0 or lower
-
Identify the plugin configuration fileIn the Jenkins home directory ($JENKINS_HOME), look for an XML config file matching the plugin's internal name; common paths include config.xml or a dedicated file like org.jenkinsci.plugins.skype.*.xml in the $JENKINS_HOME/ directoryAffected if A configuration file associated with the Skype notifier plugin exists in the Jenkins home directory
-
Inspect the configuration file for stored passwordsOpen the identified configuration file using a text editor or command line (e.g., cat or type command) and search for password-related XML elements such as <password>, <secret>, or similar fields containing credential dataAffected if The password field contains an unencrypted, plain text value rather than an encrypted or hashed string
A user is affected if the Skype Notifier Plugin version 1.1.0 or earlier is installed AND its configuration file contains unencrypted password values in plain text.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade the Skype notifier Plugin to a version that encrypts stored passwords, or migrate the credential to Jenkins' built-in credentials store. Until patched, restrict filesystem access to the Jenkins controller to trusted administrators only.
Fix this in Skype Notifier
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-34805 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-34805 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data