LiveActive security incident?Get immediate response
CVE Record

CVE-2024-0241: encoded_id-rails Denial of Service Vulnerability

encoded_id-rails versions before 1.0.0.beta2 are affected by an uncontrolled resource consumption vulnerability. A remote and unauthenticated attacker might cause a denial of service condition by sending an HTTP request with an extremely long "id" parameter.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2024-0241 affects the Ruby gem encoded_id-rails before 1.0.0.beta2. An unauthenticated remote attacker may be able to exhaust server resources by sending a request with an extremely long id parameter, causing service disruption. The available sources do not show active exploitation.

Executive priority

Prioritize remediation for any public application using encoded_id-rails. The risk is service outage rather than data theft, but exploitation requires no authentication and low complexity, making exposed systems operationally important to fix.

Technical view

This is CWE-400 uncontrolled resource consumption in encoded_id-rails. The CVSS 3.1 score is 7.5: network-accessible, low complexity, no privileges, no user interaction, with high availability impact only. The issue is fixed by the referenced upstream patch and version 1.0.0.beta2 or later.

Likely exposure

Exposure is likely limited to Rails applications that include encoded_id-rails before 1.0.0.beta2 and process attacker-controlled id parameters through the vulnerable code path. The source bundle does not identify broader affected products or hosted services.

Exploitation context

The sources describe unauthenticated remote denial of service through oversized id input. KEV is false, and the provided sources do not cite active exploitation or public weaponization. Treat internet-facing Rails routes using encoded identifiers as the primary concern.

Researcher notes

Affected-version evidence is concise: sources state encoded_id-rails versions before 1.0.0.beta2. The bundle’s affected metadata is sparse, so validate exposure from real dependency data. No source in the bundle supports claims of exploitation in the wild.

Mitigation direction

  • Upgrade encoded_id-rails to 1.0.0.beta2 or later.
  • Review the GitHub advisory and patch before production rollout.
  • Prioritize internet-facing Rails applications using encoded_id-rails.
  • If upgrade is delayed, follow vendor guidance for temporary risk reduction.
  • Monitor application errors and resource exhaustion around id-handling routes.

Validation and detection

  • Check dependency manifests and lockfiles for encoded_id-rails versions before 1.0.0.beta2.
  • Identify public Rails routes that pass id parameters into encoded_id-rails.
  • Confirm the deployed application resolves to the patched package version.
  • Review logs for unusual availability events tied to long id parameters.
Prepared
Confidence
high
Sources
6

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.

cwe · low confidence lookup

CWE-400: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2024-0241 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
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

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

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
3Timeline events
2ADP providers
5Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical Impact: partial

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
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2024-0241Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Unknown vendorencoded_id-railsencoded_id-rails, 0unaffected
Weakness

CWE details

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

CWE-400 · source CWE mapping

Uncontrolled Resource Consumption

Uncontrolled Resource Consumption represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.