153 lines
8.0 KiB
JSON
153 lines
8.0 KiB
JSON
{
|
|
"dataType": "CVE_RECORD",
|
|
"dataVersion": "5.2",
|
|
"cveMetadata": {
|
|
"cveId": "CVE-2026-58064",
|
|
"assignerOrgId": "f0158376-9dc2-43b6-827c-5f631a4d8d09",
|
|
"state": "PUBLISHED",
|
|
"assignerShortName": "apache",
|
|
"dateReserved": "2026-06-28T05:52:16.170Z",
|
|
"datePublished": "2026-10-21T11:41:13.666Z",
|
|
"dateUpdated": "2026-10-30T14:05:38.961Z"
|
|
},
|
|
"containers": {
|
|
"cna": {
|
|
"providerMetadata": {
|
|
"orgId": "f0158376-9dc2-43b6-827c-5f631a4d8d09",
|
|
"shortName": "apache",
|
|
"dateUpdated": "2026-10-21T11:41:13.666Z"
|
|
},
|
|
"title": "Apache bRPC: Denial of Service via Unbounded Redis Inline Command Allocation",
|
|
"problemTypes": [
|
|
{
|
|
"descriptions": [
|
|
{
|
|
"description": "CWE-770 Allocation of Resources Without Limits or Throttling",
|
|
"lang": "en",
|
|
"cweId": "CWE-770",
|
|
"type": "CWE"
|
|
}
|
|
]
|
|
}
|
|
],
|
|
"source": {
|
|
"discovery": "EXTERNAL"
|
|
},
|
|
"affected": [
|
|
{
|
|
"vendor": "Apache Software Foundation",
|
|
"product": "Apache bRPC",
|
|
"packageURL": "pkg:github/apache/brpc",
|
|
"versions": [
|
|
{
|
|
"status": "affected",
|
|
"version": "0",
|
|
"lessThan": "1.18.0",
|
|
"versionType": "semver"
|
|
}
|
|
],
|
|
"defaultStatus": "unaffected",
|
|
"collectionURL": "https://github.com",
|
|
"packageName": "apache/brpc"
|
|
}
|
|
],
|
|
"descriptions": [
|
|
{
|
|
"value": "The Redis protocol implementation in Apache bRPC allowed inline command parsing to allocate and copy the full connection buffer before a complete CRLF-terminated command was available. A remote attacker with access to a Redis-protocol bRPC service could send long inline inputs without a terminating CRLF to increase memory usage and CPU copy overhead, potentially causing denial of service.\n\n\nRoot Cause:\nThe Redis inline command parser allocated memory based on the current input buffer size and copied the entire buffer before determining the current inline command boundary. The existing redis_max_allocation_size limit was applied to RESP bulk strings and arrays, but not effectively to the inline command path before allocation.\n\n\nAffected Scenarios:\nUse Apache bRPC server with Redis protocol enabled and reachable by untrusted clients.\n\n\nHow to Fix:\n1. Upgrade Apache bRPC to version 1.18.0, which fixes this issue.\n2. Apply the patch from PR https://github.com/apache/brpc/pull/3363 .\n\n\nNote:\nThe fix applies redis_max_allocation_size to Redis inline command lines and scans for CRLF before allocating parser arena memory. Inline command lines exceeding this limit are rejected.",
|
|
"lang": "en",
|
|
"supportingMedia": [
|
|
{
|
|
"type": "text/html",
|
|
"base64": false,
|
|
"value": "<div><div>The Redis protocol implementation in Apache bRPC allowed inline command parsing to allocate and copy the full connection buffer before a complete CRLF-terminated command was available. A remote attacker with access to a Redis-protocol bRPC service could send long inline inputs without a terminating CRLF to increase memory usage and CPU copy overhead, potentially causing denial of service.</div><br><div>Root Cause:<br>The Redis inline command parser allocated memory based on the current input buffer size and copied the entire buffer before determining the current inline command boundary. The existing redis_max_allocation_size limit was applied to RESP bulk strings and arrays, but not effectively to the inline command path before allocation.</div><br><div>Affected Scenarios:<br>Use Apache bRPC server with Redis protocol enabled and reachable by untrusted clients.</div><br><div>How to Fix:<br>1. Upgrade Apache bRPC to version 1.18.0, which fixes this issue.<br>2. Apply the patch from PR <a target=\"_blank\" rel=\"nofollow\" href=\"https://github.com/apache/brpc/pull/3363\">https://github.com/apache/brpc/pull/3363</a>.</div><br><div>Note:<br>The fix applies redis_max_allocation_size to Redis inline command lines and scans for CRLF before allocating parser arena memory. Inline command lines exceeding this limit are rejected.</div></div>\n\n<br>"
|
|
}
|
|
]
|
|
}
|
|
],
|
|
"references": [
|
|
{
|
|
"url": "https://lists.apache.org/thread/2pf15ojj0vr7rtx95677kgtl1mx3gdgb",
|
|
"tags": [
|
|
"vendor-advisory"
|
|
]
|
|
}
|
|
],
|
|
"metrics": [
|
|
{
|
|
"other": {
|
|
"type": "Textual description of severity",
|
|
"content": {
|
|
"text": "high"
|
|
}
|
|
},
|
|
"scenarios": [
|
|
{
|
|
"lang": "en",
|
|
"value": "GENERAL"
|
|
}
|
|
]
|
|
}
|
|
],
|
|
"credits": [
|
|
{
|
|
"lang": "en",
|
|
"value": "73Lab of Qingteng.cn",
|
|
"type": "finder"
|
|
}
|
|
],
|
|
"x_generator": {
|
|
"engine": "Vulnogram 0.2.0"
|
|
}
|
|
},
|
|
"adp": [
|
|
{
|
|
"metrics": [
|
|
{
|
|
"cvssV3_1": {
|
|
"scope": "UNCHANGED",
|
|
"version": "3.1",
|
|
"baseScore": 7.5,
|
|
"attackVector": "NETWORK",
|
|
"baseSeverity": "HIGH",
|
|
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
|
|
"integrityImpact": "NONE",
|
|
"userInteraction": "NONE",
|
|
"attackComplexity": "LOW",
|
|
"availabilityImpact": "HIGH",
|
|
"privilegesRequired": "NONE",
|
|
"confidentialityImpact": "NONE"
|
|
}
|
|
},
|
|
{
|
|
"other": {
|
|
"type": "ssvc",
|
|
"content": {
|
|
"timestamp": "2026-10-30T13:59:03.634739Z",
|
|
"id": "CVE-2026-58064",
|
|
"options": [
|
|
{
|
|
"Exploitation": "none"
|
|
},
|
|
{
|
|
"Automatable": "yes"
|
|
},
|
|
{
|
|
"Technical Impact": "partial"
|
|
}
|
|
],
|
|
"role": "CISA Coordinator",
|
|
"version": "2.0.3"
|
|
}
|
|
}
|
|
}
|
|
],
|
|
"title": "CISA ADP Vulnrichment",
|
|
"providerMetadata": {
|
|
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
|
|
"shortName": "CISA-ADP",
|
|
"dateUpdated": "2026-10-30T14:05:38.961Z"
|
|
}
|
|
}
|
|
]
|
|
}
|
|
} |