Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.0

Local Temp Directory Hijacking Vulnerability

CVE-2020-27216GHSA-g3wg-6mcf-8jj6

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (org.mortbay.jetty:jetty-webapp 11.0.0.beta3, 10.0.0.beta3, 9.4.33; org.eclipse.jetty:jetty-webapp 11.0.0.beta3, 10.0.0.beta3, 9.4.33.v20201020), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Maven org.mortbay.jetty:jetty-webapp

    Affected
    < 9.4.33>= 10.0.0.beta1, <= 10.0.0.beta2>= 11.0.0.beta1, <= 11.0.0.beta2
    Fixed in
    11.0.0.beta3, 10.0.0.beta3, 9.4.33

  • Maven org.eclipse.jetty:jetty-webapp

    Affected
    >= 10.0.0.beta1, <= 10.0.0.beta2>= 11.0.0.beta1, <= 11.0.0.beta2< 9.4.33.v20201020
    Fixed in
    11.0.0.beta3, 10.0.0.beta3, 9.4.33.v20201020

Sources

  • GitHub Advisory Database and maintainer security advisories on GitHub

    GitHub-reviewed advisory GHSA-g3wg-6mcf-8jj6 lists affected ranges: Maven org.mortbay.jetty:jetty-webapp >=0 =10.0.0.beta1 =11.0.0.beta1 =10.0.0.beta1 =11.0.0.beta1 =0 <9.4.33.v20201020

    VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.0 · CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
  • CVE-2020-27216: 4.35% estimated exploitation activity in the next 30 days; percentile 91.25 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Impact On Unix like systems, the system's temporary directory is shared between all users on that system. A collocated user can observe the process of creating a temporary sub directory in the shared temporary directory and race to complete the creation of the temporary subdirectory. If the attacker wins the race then they will have read and write permission to the subdirectory used to unpack web applications, including their WEB-INF/lib jar files and JSP files. If any code is ever executed out of this temporary directory, this can lead to a local privilege escalation vulnerability. Additionally, any user code uses of WebAppContext::getTempDirectory) would similarly be vulnerable. Additionally, any user application code using the ServletContext attribute for the tempdir will also be impacted. See: https://javaee.github.io/javaee-spec/javadocs/javax/servlet/ServletContext.html#TEMPDIR For example: Example: The JSP library itself will use the container temp directory for compiling the…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-g3wg-6mcf-8jj6

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2020-27216

Advisory: Local Temp Directory Hijacking Vulnerability
IDs: CVE-2020-27216, GHSA-g3wg-6mcf-8jj6
Record: https://patchnext.com/advisories/cve-2020-27216 (revision 1, source checked 26 Oct 2026, 16:20 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.mortbay.jetty:jetty-webapp 11.0.0.beta3, 10.0.0.beta3, 9.4.33; org.eclipse.jetty:jetty-webapp 11.0.0.beta3, 10.0.0.beta3, 9.4.33.v20201020. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.mortbay.jetty:jetty-webapp: affected < 9.4.33; >= 10.0.0.beta1, <= 10.0.0.beta2; >= 11.0.0.beta1, <= 11.0.0.beta2; fixed in 11.0.0.beta3, 10.0.0.beta3, 9.4.33
- Maven org.eclipse.jetty:jetty-webapp: affected >= 10.0.0.beta1, <= 10.0.0.beta2; >= 11.0.0.beta1, <= 11.0.0.beta2; < 9.4.33.v20201020; fixed in 11.0.0.beta3, 10.0.0.beta3, 9.4.33.v20201020

## Suggested inspection (read-only)
- Maven org.mortbay.jetty:jetty-webapp: check the installed version with your package manager.
- Maven org.eclipse.jetty:jetty-webapp: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.mortbay.jetty:jetty-webapp, org.eclipse.jetty:jetty-webapp.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-g3wg-6mcf-8jj6 (GitHub-reviewed advisory GHSA-g3wg-6mcf-8jj6 lists affected ranges: Maven org.mortbay.jetty:jetty-webapp >=0 =10.0.0.beta1 =11.0.0.beta1 =10.0.0.beta1 =11.0.0.beta1 =0 <9.4.33.v20201020)

Commands are suggestions: review each one before running it.

Loading voting…