175 lines
10 KiB
JSON
175 lines
10 KiB
JSON
{
|
|
"dataType": "CVE_RECORD",
|
|
"dataVersion": "5.2",
|
|
"cveMetadata": {
|
|
"cveId": "CVE-2026-82438",
|
|
"assignerOrgId": "f0158376-9dc2-43b6-827c-5f631a4d8d09",
|
|
"state": "PUBLISHED",
|
|
"assignerShortName": "apache",
|
|
"dateReserved": "2026-08-29T10:37:41.671Z",
|
|
"datePublished": "2026-09-14T14:02:07.213Z",
|
|
"dateUpdated": "2026-09-14T19:52:48.724Z"
|
|
},
|
|
"containers": {
|
|
"cna": {
|
|
"providerMetadata": {
|
|
"orgId": "f0158376-9dc2-43b6-827c-5f631a4d8d09",
|
|
"shortName": "apache",
|
|
"dateUpdated": "2026-09-14T14:02:07.213Z"
|
|
},
|
|
"title": "Apache Storm Webapp: Authenticated API Responses Exposed to Arbitrary Web Origins",
|
|
"problemTypes": [
|
|
{
|
|
"descriptions": [
|
|
{
|
|
"description": "CWE-346 Origin Validation Error",
|
|
"lang": "en",
|
|
"cweId": "CWE-346",
|
|
"type": "CWE"
|
|
}
|
|
]
|
|
},
|
|
{
|
|
"descriptions": [
|
|
{
|
|
"description": "CWE-942 Permissive Cross-domain Security Policy with Untrusted Domains",
|
|
"lang": "en",
|
|
"cweId": "CWE-942",
|
|
"type": "CWE"
|
|
}
|
|
]
|
|
}
|
|
],
|
|
"source": {
|
|
"discovery": "UNKNOWN"
|
|
},
|
|
"affected": [
|
|
{
|
|
"vendor": "Apache Software Foundation",
|
|
"product": "Apache Storm Webapp",
|
|
"collectionURL": "https://repo.maven.apache.org/maven2",
|
|
"packageName": "org.apache.storm:storm-webapp",
|
|
"versions": [
|
|
{
|
|
"status": "affected",
|
|
"version": "3.0.0",
|
|
"lessThan": "3.1.0",
|
|
"versionType": "semver"
|
|
}
|
|
],
|
|
"defaultStatus": "unaffected"
|
|
}
|
|
],
|
|
"descriptions": [
|
|
{
|
|
"value": "Description\n\nThree separate mechanisms allowed a web page on an unrelated origin to read responses that Storm's HTTP\ncomponents served to an authenticated user.\n\nThe Logviewer reflected the request's `Origin` header back in `Access-Control-Allow-Origin` while also\nsending `Access-Control-Allow-Credentials: true`. The published security model documents a permissive\n`Access-Control-Allow-Origin: *` posture as accepted, which is safe precisely because browsers refuse to\nhonour `*` together with credentials; reflecting the concrete origin removes that protection.\n\nThe shared CORS filter used by the UI, the Logviewer and DRPC was configured with a response header name\nwhere an initialisation parameter name was expected. The container ignored the setting and applied its own\ndefaults, which allow credentials.\n\nFinally, the UI and Logviewer wrapped API responses in a caller-supplied JSONP callback for every GET\nrequest. A script element on any origin can load such a response, which bypasses the same-origin policy\nentirely rather than negotiating it, and there was no way to turn the behaviour off.\n\nIn each case the effect is that a page visited by an authenticated operator can read cluster, topology and\nlog data on their behalf.\n\nMitigation\n\nUpgrade to 3.1.0, where the Logviewer no longer reflects the request origin in a credentialed response, the\nCORS filter is configured explicitly, and JSONP wrapping is governed by `ui.enable.jsonp`, which defaults to\nfalse.\n\nNote that disabling JSONP is a behaviour change for tooling that passes a `callback` query parameter; such\ntooling should be moved to ordinary JSON requests.\n\nUsers who cannot upgrade immediately should place the UI, Logviewer and DRPC HTTP endpoints behind a reverse\nproxy that strips `Access-Control-Allow-Origin` and `Access-Control-Allow-Credentials` from responses and\nrejects requests carrying a `callback` parameter.\n\nCredit\n\nThe ASF -- found using Claude agents to study the security of open-source projects, validated and reported by Apache Storm.",
|
|
"lang": "en",
|
|
"supportingMedia": [
|
|
{
|
|
"type": "text/html",
|
|
"base64": false,
|
|
"value": "<b>Description</b><br><br>Three separate mechanisms allowed a web page on an unrelated origin to read responses that Storm's HTTP<br>components served to an authenticated user.<br><br>The Logviewer reflected the request's `Origin` header back in `Access-Control-Allow-Origin` while also<br>sending `Access-Control-Allow-Credentials: true`. The published security model documents a permissive<br>`Access-Control-Allow-Origin: *` posture as accepted, which is safe precisely because browsers refuse to<br>honour `*` together with credentials; reflecting the concrete origin removes that protection.<br><br>The shared CORS filter used by the UI, the Logviewer and DRPC was configured with a response header name<br>where an initialisation parameter name was expected. The container ignored the setting and applied its own<br>defaults, which allow credentials.<br><br>Finally, the UI and Logviewer wrapped API responses in a caller-supplied JSONP callback for every GET<br>request. A script element on any origin can load such a response, which bypasses the same-origin policy<br>entirely rather than negotiating it, and there was no way to turn the behaviour off.<br><br>In each case the effect is that a page visited by an authenticated operator can read cluster, topology and<br>log data on their behalf.<br><br><b>Mitigation</b><br><br>Upgrade to 3.1.0, where the Logviewer no longer reflects the request origin in a credentialed response, the<br>CORS filter is configured explicitly, and JSONP wrapping is governed by `ui.enable.jsonp`, which defaults to<br>false.<br><br>Note that disabling JSONP is a behaviour change for tooling that passes a `callback` query parameter; such<br>tooling should be moved to ordinary JSON requests.<br><br>Users who cannot upgrade immediately should place the UI, Logviewer and DRPC HTTP endpoints behind a reverse<br>proxy that strips `Access-Control-Allow-Origin` and `Access-Control-Allow-Credentials` from responses and<br>rejects requests carrying a `callback` parameter.<br><br><b>Credit</b><br><br>The ASF -- found using Claude agents to study the security of open-source projects, validated and reported by Apache Storm.<br>"
|
|
}
|
|
]
|
|
}
|
|
],
|
|
"references": [
|
|
{
|
|
"url": "https://lists.apache.org/thread/2o7tl3hcdd865njxsn4d9cxp1frkctz3",
|
|
"tags": [
|
|
"vendor-advisory"
|
|
]
|
|
}
|
|
],
|
|
"metrics": [
|
|
{
|
|
"other": {
|
|
"type": "Textual description of severity",
|
|
"content": {
|
|
"text": "important"
|
|
}
|
|
},
|
|
"scenarios": [
|
|
{
|
|
"lang": "en",
|
|
"value": "GENERAL"
|
|
}
|
|
]
|
|
}
|
|
],
|
|
"credits": [
|
|
{
|
|
"lang": "en",
|
|
"value": "The ASF using Claude Agents",
|
|
"type": "finder"
|
|
}
|
|
],
|
|
"x_generator": {
|
|
"engine": "Vulnogram 1.0.3"
|
|
}
|
|
},
|
|
"adp": [
|
|
{
|
|
"title": "CVE Program Container",
|
|
"references": [
|
|
{
|
|
"url": "http://www.openwall.com/lists/oss-security/2026/09/13/17"
|
|
}
|
|
],
|
|
"providerMetadata": {
|
|
"orgId": "af854a3a-2127-422b-91ae-364da2661108",
|
|
"shortName": "CVE",
|
|
"dateUpdated": "2026-09-14T14:13:42.629Z"
|
|
}
|
|
},
|
|
{
|
|
"metrics": [
|
|
{
|
|
"cvssV3_1": {
|
|
"scope": "UNCHANGED",
|
|
"version": "3.1",
|
|
"baseScore": 8.1,
|
|
"attackVector": "NETWORK",
|
|
"baseSeverity": "HIGH",
|
|
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N",
|
|
"integrityImpact": "HIGH",
|
|
"userInteraction": "NONE",
|
|
"attackComplexity": "LOW",
|
|
"availabilityImpact": "NONE",
|
|
"privilegesRequired": "LOW",
|
|
"confidentialityImpact": "HIGH"
|
|
}
|
|
},
|
|
{
|
|
"other": {
|
|
"type": "ssvc",
|
|
"content": {
|
|
"timestamp": "2026-09-14T19:52:29.973602Z",
|
|
"id": "CVE-2026-82438",
|
|
"options": [
|
|
{
|
|
"Exploitation": "none"
|
|
},
|
|
{
|
|
"Automatable": "no"
|
|
},
|
|
{
|
|
"Technical Impact": "total"
|
|
}
|
|
],
|
|
"role": "CISA Coordinator",
|
|
"version": "2.0.3"
|
|
}
|
|
}
|
|
}
|
|
],
|
|
"title": "CISA ADP Vulnrichment",
|
|
"providerMetadata": {
|
|
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
|
|
"shortName": "CISA-ADP",
|
|
"dateUpdated": "2026-09-14T19:52:48.724Z"
|
|
}
|
|
}
|
|
]
|
|
}
|
|
} |