Description
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 breakdown
Affected products
- spaceapplications / yamcs5.12.8
- yamcs / yamcs< 5.12.8 – < 5.12.8
- yamcs / yamcs>= 5.13.0, < 5.13.2 – >= 5.13.0, < 5.13.2
References
- VENDOR_ADVISORYhttps://github.com/yamcs/yamcs/security/advisories/GHSA-8xjq-pr36-ccgf
- PATCHhttps://github.com/yamcs/yamcs/commit/b566beceba98cc35514b0e1519be126b8c5a0438
- PATCHhttps://github.com/yamcs/yamcs/commit/c743cc3acf5b5c53ff5181b94eacc21340f70dd9
- PATCHhttps://github.com/yamcs/yamcs/releases/tag/yamcs-5.12.8
- PATCHhttps://github.com/yamcs/yamcs/releases/tag/yamcs-5.13.2