Skip to content

Deserialization of Untrusted Data in apache-submarine

Critical severity GitHub Reviewed Published Nov 20, 2023 to the GitHub Advisory Database • Updated Nov 30, 2023

Package

pip apache-submarine (pip)

Affected versions

>= 0.7.0, < 0.8.0

Patched versions

0.8.0

Description

Apache Software Foundation Apache Submarine has a bug when serializing against yaml. The bug is caused by snakeyaml https://nvd.nist.gov/vuln/detail/CVE-2022-1471 .

Apache Submarine uses JAXRS to define REST endpoints. In order to
handle YAML requests (using application/yaml content-type), it defines
a YamlEntityProvider entity provider that will process all incoming
YAML requests. In order to unmarshal the request, the readFrom method
is invoked, passing the entityStream containing the user-supplied data in submarine-server/server-core/src/main/java/org/apache/submarine/server/utils/YamlUtils.java.

We have now fixed this issue in the new version by replacing to jackson-dataformat-yaml.
This issue affects Apache Submarine: from 0.7.0 before 0.8.0. Users are recommended to upgrade to version 0.8.0, which fixes this issue.
If using the version smaller than 0.8.0 and not want to upgrade, you can try cherry-pick PR apache/submarine#1054 and rebuild the submart-server image to fix this.

References

Published by the National Vulnerability Database Nov 20, 2023
Published to the GitHub Advisory Database Nov 20, 2023
Reviewed Nov 20, 2023
Last updated Nov 30, 2023

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS score

0.237%
(63rd percentile)

Weaknesses

CVE ID

CVE-2023-46302

GHSA ID

GHSA-8hcr-5x2g-9f7j

Source code

No known source code
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.