Publish Over FtpApplication · Jenkins
CVE-2022-29050
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 · uneditedA cross-site request forgery (CSRF) vulnerability in Jenkins Publish Over FTP Plugin 1.16 and earlier allows attackers to connect to an FTP server using attacker-specified credentials.
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 confidenceA cross-site request forgery (CSRF) vulnerability in Jenkins Publish Over FTP Plugin version 1.16 and earlier allows attackers to trick authenticated users into connecting to an attacker-specified FTP server using credentials of the attacker's choosing.
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
Publish Over FtpApplication
<= 1.16CVSS 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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.
-
Verify the plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Publish Over FTP' in the list of installed pluginsAffected if The plugin appears in the installed plugins list
-
Check the installed versionIn the same Installed plugins list, locate the 'Publish Over FTP' plugin and note the Version columnAffected if The version is 1.16 or earlier (e.g., 1.16, 1.15, 1.14, etc.)
-
Confirm the plugin is activeNavigate to Manage Jenkins > Manage Plugins > Installed tab and verify the 'Publish Over FTP' plugin shows as 'Enabled' or has a checkbox ticked in the Enable columnAffected if The plugin is enabled/active in Jenkins
-
Check for FTP publisher configurationsNavigate to a job configuration page (or global configuration if available) and look for FTP publisher settings under 'Build Steps' or 'Post-build Actions'Affected if There are FTP publisher configurations defined in any job
A user is affected if the Jenkins Publish Over FTP Plugin version 1.16 or earlier is installed and enabled, regardless of whether it is actively configured.
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.
dbcve · scopedUpdate the Jenkins Publish Over FTP Plugin to a version newer than 1.16, or disable the plugin if not required.
Publish Over FTP plugin version 1.17
- In Jenkins, go to Manage Jenkins > Manage Plugins
- Go to the 'Installed' tab
- Find 'Publish Over FTP' plugin in the list
- If an update is available, select the checkbox next to the plugin
- Click 'Download now and install after restart' or 'Update'
- After the update completes, restart Jenkins or wait for the pending plugin installation to finish
- Verify the plugin version is 1.17 or later
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Publish Over Ftp
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-29050 — 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-29050 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