GHSA-X27V-F838-JH93
Vulnerability from github – Published: 2025-04-22 16:55 – Updated: 2025-05-27 17:19
VLAI?
Summary
io.jmix.rest:jmix-rest allows XSS in the /files Endpoint of the Generic REST API
Details
Impact
The input parameter, which consists of a file path and name, can be manipulated to return the Content-Type header with text/html if the name part ends with .html. This could allow malicious JavaScript code to be executed in the browser. For a successful attack, a malicious file needs to be uploaded beforehand.
The severity of the vulnerability is mitigated by the fact that the application UI and the generic REST API are typically accessible only to authenticated users. Additionally, the /files endpoint in Jmix requires specific permissions and is disabled by default.
Patches
The problem has been fixed in Jmix 1.6.2+ and 2.4.0+.
Workarounds
A workaround for those who are unable to upgrade: Disable Files Endpoint in Jmix Application.
Severity ?
6.4 (Medium)
{
"affected": [
{
"package": {
"ecosystem": "Maven",
"name": "io.jmix.rest:jmix-rest"
},
"ranges": [
{
"events": [
{
"introduced": "1.0.0"
},
{
"fixed": "1.6.2"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Maven",
"name": "io.jmix.rest:jmix-rest"
},
"ranges": [
{
"events": [
{
"introduced": "2.0.0"
},
{
"fixed": "2.4.0"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2025-32951"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": true,
"github_reviewed_at": "2025-04-22T16:55:13Z",
"nvd_published_at": "2025-04-22T18:15:59Z",
"severity": "MODERATE"
},
"details": "### Impact\n\nThe input parameter, which consists of a file path and name, can be manipulated to return the Content-Type header with text/html if the name part ends with .html. This could allow malicious JavaScript code to be executed in the browser. For a successful attack, a malicious file needs to be uploaded beforehand.\n\nThe severity of the vulnerability is mitigated by the fact that the application UI and the generic REST API are typically accessible only to authenticated users. Additionally, the /files endpoint in Jmix requires specific permissions and is disabled by default. \n\n### Patches\n\nThe problem has been fixed in Jmix 1.6.2+ and 2.4.0+.\n\n### Workarounds\n\nA workaround for those who are unable to upgrade: [Disable Files Endpoint in Jmix Application](https://docs.jmix.io/jmix/files-vulnerabilities.html#disable-files-endpoint-in-jmix-application).",
"id": "GHSA-x27v-f838-jh93",
"modified": "2025-05-27T17:19:00Z",
"published": "2025-04-22T16:55:13Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/jmix-framework/jmix/security/advisories/GHSA-x27v-f838-jh93"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-32951"
},
{
"type": "WEB",
"url": "https://github.com/jmix-framework/jmix/issues/3804"
},
{
"type": "WEB",
"url": "https://github.com/jmix-framework/jmix/issues/3836"
},
{
"type": "WEB",
"url": "https://github.com/jmix-framework/jmix/commit/6a66aa3adb967159a30d703e80403406f4c8f7a2"
},
{
"type": "WEB",
"url": "https://github.com/jmix-framework/jmix/commit/c589ef4e2b25620770b8036f4ad05f1a6250cb6a"
},
{
"type": "WEB",
"url": "https://github.com/jmix-framework/jmix/commit/cc97e6ff974b9e7af8160fab39cc5866169daa37"
},
{
"type": "WEB",
"url": "https://github.com/jmix-framework/jmix/commit/f4e6fb05bd245cf36f3e9319aaa0fcd540d024aa"
},
{
"type": "WEB",
"url": "https://docs.jmix.io/jmix/files-vulnerabilities.html"
},
{
"type": "WEB",
"url": "https://docs.jmix.io/jmix/files-vulnerabilities.html#disable-files-endpoint-in-jmix-application"
},
{
"type": "PACKAGE",
"url": "https://github.com/jmix-framework/jmix"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N",
"type": "CVSS_V3"
}
],
"summary": "io.jmix.rest:jmix-rest allows XSS in the /files Endpoint of the Generic REST API"
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…