** UNSUPPORTED WHEN ASSIGNED ** Deserialization of an inbound SOAP fault in Apache Axis 1.x allows unauthenticated remote class instantiation. When a...
影響パッケージ
| パッケージ | 影響を受ける版 → 修正版 | |
|---|---|---|
| Ubuntu:Pro:16.04:LTSaxis |
すべての版→ 記載なし |
記載なし |
| Ubuntu:Pro:18.04:LTSaxis |
すべての版→ 記載なし |
記載なし |
| Ubuntu:20.04:LTSaxis |
すべての版→ 記載なし |
記載なし |
| Ubuntu:22.04:LTSaxis |
すべての版→ 記載なし |
記載なし |
| Ubuntu:24.04:LTSaxis |
すべての版→ 記載なし |
記載なし |
| Ubuntu:26.10axis |
すべての版→ 記載なし |
記載なし |
| Ubuntu:26.04:LTSaxis |
すべての版→ 記載なし |
記載なし |
この記録には修正版の版が載っていません。修正版の有無と版は、本文か参照URLのベンダーの勧告で確かめてください。
原文の説明 取得元が公開している説明をそのまま載せています (多くは英語)。
** UNSUPPORTED WHEN ASSIGNED ** Deserialization of an inbound SOAP fault in Apache Axis 1.x allows unauthenticated remote class instantiation. When a SOAP carries a element, Axis loads the named class and, if a String element is also present, instantiates it through its String constructor before checking that it is an AxisFault. Loading alone runs the class's static initializer. With a suitable class on the application's classpath this leads to remote code execution. The fault is parsed while the engine resolves the target service, before any per-service handler chain runs, so authentication handlers configured on a service do not protect against it. This affects all Apache Axis 1.x versions through 1.4. As Axis 1 has been EOL we recommend you migrate to a different SOAP engine, such as Apache Axis 2/Java. Alternatively you could use a build of Axis with the patch from https://github.com/apache/axis-axis1-java/commit/41f3b4e8d04e310ca81f86b92630ab2c11d608bd applied. The Apache Axis project does not expect to create an Axis 1.x release fixing this problem.
出典: OSV.dev (Open Source Vulnerabilities) OSV
参照URL
- report ubuntu.com
- report cve.org
- report lists.apache.org
- report github.com
- report lists.apache.org
- report openwall.com
- report cisa.gov