LiveActive security incident?Get immediate response
CVE Record

CVE-2020-7622: HTTP Response Splitting

This affects the package io.jooby:jooby-netty before 1.6.9, from 2.0.0 and before 2.2.1. The DefaultHttpHeaders is set to false which means it does not validates that the header isn't being abused for HTTP Response Splitting.

MediumCVSS 6.5Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Some Jooby applications using the Netty module accepted unsafe response header values. If an application reflects untrusted data into response headers, an attacker could influence HTTP response structure, potentially causing response confusion or limited confidentiality and integrity impact. The issue is medium severity because exposure depends on application header-handling behavior.

Executive priority

Treat as a moderate-priority dependency remediation for Jooby Netty applications. Prioritize internet-facing services and systems that create response headers from user input, then complete normal patch validation before deployment.

Technical view

CVE-2020-7622 affects io.jooby:jooby-netty before 1.6.9, and 2.0.0 through before 2.2.1. The reported cause is DefaultHttpHeaders validation being disabled, allowing unsafe header content that could enable HTTP response splitting when attacker-controlled data reaches response headers.

Likely exposure

Exposure is most likely in Java services using the affected jooby-netty versions, especially public web applications that set response headers from request parameters, cookies, paths, or other user-controlled input.

Exploitation context

The provided sources do not show CISA KEV listing or confirmed active exploitation. Practical risk depends on whether an application passes untrusted input into response headers; the package flaw alone does not prove exploitable business impact.

Researcher notes

The key research question is data flow into response headers. Validate affected version ranges first, then trace framework and application header-setting paths. The source bundle provides version boundaries and root cause, but no confirmed exploitation evidence.

Mitigation direction

  • Upgrade io.jooby:jooby-netty to 1.6.9, 2.2.1, or a later fixed release.
  • Check Jooby advisory guidance for the version line used in each application.
  • Avoid building response headers directly from untrusted input.
  • Review code paths that set redirects, cookies, cache headers, and custom headers.
  • Add dependency scanning to prevent reintroducing affected versions.

Validation and detection

  • Check dependency manifests and lockfiles for io.jooby:jooby-netty versions.
  • Confirm deployed artifacts match a fixed jooby-netty version.
  • Run SCA tooling against source and built packages.
  • Review application code for user-controlled data reaching response headers.
  • Test that unsafe header values are rejected or normalized by the application.
Prepared
Confidence
high
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2020-7622 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N3.92.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.5Medium
CVSS 3.1 vector shape for CVE-2020-7622Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/aio.jooby:jooby-nettyunspecified, 2.0.0, unspecifiedListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.