Loading...
Skip to main content

CVE-2023-28846 — Vulnerability in unpoly-rails — CVE Details

MEDIUM

unpoly-rails Denial of Service vulnerability

Published March 30, 2023Updated September 10, 2026Source: osv

Summary

There is a possible Denial of Service (DoS) vulnerability in the unpoly-rails gem that implements the [Unpoly server protocol](https://unpoly.com/up.protocol) for Rails applications. ### Impact This issues affects Rails applications that operate as an upstream of a load balancer's that uses [passive health checks](https://docs.nginx.com/nginx/admin-guide/load-balancer/http-health-check/#passive-health-checks). The [unpoly-rails](https://github.com/unpoly/unpoly-rails/) gem echoes the request URL as an `X-Up-Location` response header. By making a request with exceedingly long URLs (paths or query string), an attacker can cause unpoly-rails to write a exceedingly large response header. If the response header is too large to be parsed by a load balancer downstream of the Rails application, it may cause the load balancer to remove the upstream from a load balancing group. This causes that application instance to become unavailable until a configured timeout is reached or until an active healthcheck succeeds. ### Patches The fixed release 2.7.2.2+ is available via RubyGems and GitHub. ### Workarounds If you cannot upgrade to a fixed release, several workarounds are available: - Configure your load balancer to use active health checks, e.g. by periodically requesting a route with a known response that indicates healthiness. - Configure your load balancer so the [maximum size of response headers](https://makandracards.com/operations/537537-nginx-proxy-buffer-tuning) is at least twice the [maximum size of a URL](https://tryhexadecimal.com/guides/http/414-request-uri-too-long). - Instead of changing your server configuration you may also configure your Rails application to delete redundant `X-Up-Location` headers set by unpoly-rails: ```ruby class ApplicationController < ActionController::Base after_action :remove_redundant_up_location_header private def remove_redundant_up_location_header if request.original_url == response.headers['X-Up-Location'] response.headers.delete('X-Up-Location') end end end ```

Advisory Timeline

  • First published March 30, 2023 (1292 days ago).
  • Last revised September 10, 2026 — 1259 days after initial publication.

Remediation

Upgrade to the fixed version using your package manager.

Bundler
Update unpoly-rails to 2.7.2.2 or later
gem install unpoly-rails -v 2.7.2.2

After upgrading, run your dependency scanner again to confirm the vulnerability is resolved.

Affected Packages (1)

Affects 1 ecosystem: rubygems (1).

PackageEcosystemAffectedFixed In
unpoly-rails
rubygems
0.20.0, 0.21.0, 0.22.0, 0.22.1 (+97 more)2.7.2.2

Vulnerability Classification

Common Weakness Enumeration (CWE) identifiers for this vulnerability type.

  • CWE-400
    Uncontrolled Resource ConsumptionMITRE

CVSS Score Breakdown

What the CVSS (Common Vulnerability Scoring System) 5.9 score means for each attack dimension.

Attack Vector
Network
Attack Complexity
High
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

Frequently Asked Questions

What is CVE-2023-28846?
unpoly-rails Denial of Service vulnerability This vulnerability has been assigned a severity rating of MEDIUM (CVSS score: 5.9/10).
How do I check if my project is affected by CVE-2023-28846?
CVE-2023-28846 affects unpoly-rails. Use GeekWala's free vulnerability scanner to check your dependencies against CVE-2023-28846 and 200,000+ other known vulnerabilities.

Severity & Exploitability

CVSS Score
5.9

Exploitation requires specific conditions or has limited impact. Remediate within weeks.

Also Known As

GHSA-m875-3xf6-mf78

Related CVEs

Check if you're affected

Scan your dependencies to see if this vulnerability affects your projects.

Scan Your Dependencies