CVE-2026-104016
개요
A flaw was found in jackson-dataformat-protobuf. This vulnerability allows a remote attacker to cause a Denial of Service (DoS) by sending specially crafted Protocol Buffers data. Due to an integer overflow during bounds checking for length-prefixed string and byte fields, the parser bypasses validation and attempts an oversized memory allocation, crashing the application.
내용
This vulnerability is rated as having an Important impact because an unauthenticated remote attacker can crash the host Java virtual machine, causing a complete denial of service without requiring user interaction or special permissions. Red Hat integration services and middleware that consume external Protocol Buffers streams are directly exposed, as even minimal payloads can trigger unbounded internal buffer allocations. Standard parser restrictions and resource caps fail to intercept this condition, which elevates the risk above Moderate whenever endpoints accept untrusted binary input.
CVSS (Common Vulnerability Scoring System) 점수 세부 사항
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
CVSS v3 점수 분석
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| 기본 점수 | 7.5 | N/A | 7.5 |
| 공격 벡터 | Network | N/A | Network |
| 공격 복잡성 | Low | N/A | Low |
| 필요한 권한 | None | N/A | None |
| 사용자 상호 작용 | None | N/A | None |
| 범위 | Unchanged | N/A | Unchanged |
| 기밀성 | None | N/A | None |
| 무결성에 미치는 영향 | None | N/A | None |
| 가용성에 미치는 영향 | High | N/A | High |
벡터
Red Hat: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
cve.org: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
취약점 이해 (CWE)
Availability
Technical Impact: DoS: Crash, Exit, or Restart; DoS: Resource Consumption (Memory); DoS: Instability
This weakness can generally lead to undefined behavior and therefore crashes. When the calculated result is used for resource allocation, this weakness can cause too many (or too few) resources to be allocated, possibly enabling crashes if the product requests more resources than can be provided. If the calculated result involves time values, then the product might crash when it encounters a time that is less than the previously-calculated time.
Integrity
Technical Impact: Modify Memory
If the value in question is important to data (as opposed to flow), simple data corruption has occurred. Also, if the overflow/wraparound results in other conditions such as buffer overflows, further memory corruption may occur.
Confidentiality,Availability,Access Control
Technical Impact: Execute Unauthorized Code or Commands; Bypass Protection Mechanism
This weakness can sometimes trigger buffer overflows, which can be used to execute arbitrary code. This is usually outside the scope of the product's implicit security policy.
Availability,Other
Technical Impact: Alter Execution Logic; DoS: Crash, Exit, or Restart; DoS: Resource Consumption (CPU)
If the overflow/wraparound occurs in a loop index variable, this could cause the loop to terminate at the wrong time - too early, too late, or not at all (i.e., infinite loops). With too many iterations, some loops could consume too many resources such as memory, file handles, etc., possibly leading to a crash or other DoS.
Access Control
Technical Impact: Bypass Protection Mechanism
If integer values are used in security-critical decisions, such as calculating quotas or allocation limits, integer overflows can be used to cause an incorrect security decision.
Access Control
Technical Impact: Bypass Protection Mechanism; DoS: Crash, Exit, or Restart
If integer values are used in time-based, security-critical decisions, such as calculating expiration times or determining whether an event occurs within a specific time or date range, to cause an incorrect security decision. The consequences could even include "self-DoS" if the overflow produces a time value that is not accounted for in protection mechanism logic [REF-1570].
