概要
認証なしで、細工した SOAP 応答から、不正なプログラムを実行されるおそれ。
元の説明(英語)を読む
** UNSUPPORTED WHEN ASSIGNED ** Deserialization of an inbound SOAP fault in Apache Axis 1.x allows unauthenticated remote class instantiation. When a SOAP <Fault> carries a <detail><exceptionName> element, Axis loads the named class and, if a String <data> 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.
影響を受ける人
Apache Axis 1.x(1.4 まで)を使うシステムの管理者
対策
- ベンダーの告知を確認する。Axis 1 は EOL のため、Axis 2/Java など別の SOAP エンジンへの移行を検討する。
- 移行できない場合は、説明文にある修正パッチを適用した Axis を使う。
国内の動き
- Security NEXT(報道)↗11/19
海外の動き
- CISA(注意喚起)↗11/18
- BleepingComputer(報道)↗11/13
- The Hacker News(報道)↗11/12
- SecurityWeek(報道)↗11/13
PoC
リンクだけを載せる。中身は確かめていない。