Yamcs is a mission control framework. Prior to 5.12.8 and 5.13.2, the PacketsApi.exportPackets endpoint in yamcs-core/src/main/java/org/yamcs/http/api/PacketsApi.java failed to enforce object-level ReadPacket privileges when a request omitted specific packet names: with an empty name list the ctx.checkObjectPrivileges(ObjectPrivilegeType.ReadPacket, nameSet) call passed over an empty set, no WHERE pname IN filter was applied to the resulting SELECT * FROM tm query, and the onTuple handler streamed every retrieved packet without any per-row authorization check, so a low-privileged or zero-privilege authenticated user could dump the entire raw telemetry packet archive and bypass the role-based access control model. This issue is fixed in versions 5.12.8 and 5.13.2, which enforce per-packet ReadPacket checks in exportPackets.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:NSpaceapplications Yamcs
APPSpaceapplications< 5.12.85.13.0 – 5.13.2 (excl.)
Related vulnerabilities
RCE w Yamcs — wstrzyknięcie kodu Java przez silnik algorytmów
Yamcs RCE przez niezabezpieczony silnik skryptów Python (Jython)
Yamcs: RCE poprzez brak ClassFilter w silniku Nashorn JavaScript
Path Traversal w Yamcs umożliwia usunięcie dowolnych plików przez API
Yamcs 5.8.6 is vulnerable to directory traversal (issue 1 of 2). The vulnerability is in the storage functiona...