dbcve.org
Html ResourceApplication · Jenkins

CVE-2023-50774

HIGH · 8.1 CVSS v3.1 Published 2023-12-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
88/100
Remediation priority · High
Remotely reachable No privileges

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 · unedited
A cross-site request forgery (CSRF) vulnerability in Jenkins HTMLResource Plugin 1.02 and earlier allows attackers to delete arbitrary files on 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 confidence

A cross-site request forgery (CSRF) vulnerability in Jenkins HTMLResource Plugin version 1.02 and earlier allows authenticated attackers to trick the Jenkins controller into deleting arbitrary files on the file system by forcing a malicious HTTP request through a user's authenticated session.

MitigationUpdate to a patched version of the HTMLResource Plugin when available, or remove the plugin if not needed. In the interim, restrict network access to Jenkins and monitor for suspicious file deletion activity.

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
Html ResourceApplication
Affected:= 1.01= 1.02

CVSS 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
None
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check if HTMLResource Plugin is installed
    Navigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab, or use the Jenkins CLI: `java -jar jenkins-cli.jar -s http://localhost:8080 list-plugins` and look for 'htmlresource' in the list.
    Affected if The plugin appears in the installed plugins list
  2. Determine the installed version of HTMLResource Plugin
    In Jenkins > Manage Jenkins > Manage Plugins > Installed tab, find 'HTML Resource' and note the Version column. Alternatively, check the manifest file in the plugin directory: `<jenkins_home>/plugins/htmlresource/WEB-INF/lib/htmlresource.hpi` or look at the plugin's `manifest.xml`.
    Affected if The version is 1.01 or 1.02
  3. Verify plugin is active and not disabled
    In Jenkins > Manage Jenkins > Manage Plugins > Installed tab, confirm the 'Enable' checkbox is checked for HTML Resource, or check via CLI: `java -jar jenkins-cli.jar -s http://localhost:8080 list-plugins | grep -i htmlresource` - an asterisk (*) indicates enabled.
    Affected if The plugin shows as enabled/active with version 1.01 or 1.02
  4. Confirm authenticated users exist
    In Jenkins > Manage Jenkins > Manage Users, verify that at least one user account exists, or check that Jenkins is configured to allow user authentication (even via LDAP/AD). The CSRF attack requires a victim's authenticated session.
    Affected if Jenkins has at least one authenticated user account configured and HTMLResource Plugin version 1.01 or 1.02 is installed and enabled

A user is affected if Jenkins has HTMLResource Plugin version 1.01 or 1.02 installed and enabled, with at least one authenticated user session possible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to a patched version of the HTMLResource Plugin when available, or remove the plugin if not needed. In the interim, restrict network access to Jenkins and monitor for suspicious file deletion activity.

Recommended fix Moderate confidence

HTMLResource plugin version 1.03 or later

  1. 1. Backup your Jenkins instance and current plugin configuration
  2. 2. Navigate to Manage Jenkins > Manage Plugins
  3. 3. Go to the 'Installed' tab and locate the HTMLResource plugin
  4. 4. Check if an update is available for the HTMLResource plugin
  5. 5. If an update is available, review the changelog to confirm it includes the CVE-2023-50774 security fix
  6. 6. Update the HTMLResource plugin to the latest available version
  7. 7. After updating, verify the plugin is functioning correctly
  8. 8. Test that the CSRF protection is working as expected

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Html Resource Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-50774 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-50774 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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