vulnerability / NVI-00013863 / Revision 2
Yamcs's Missing Authorization on Role and Privilege Enumeration Endpoints Allows Any Authenticated User to Disclose Full Security Configuration
GitHub lists this reviewed advisory for org.yamcs:yamcs-core, org.yamcs:yamcs-core. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.
This report has not inspected your inventory, configuration, deployed build, reachability or evidence. A catalog listing and a severity score do not establish exposure or compromise.
01 / Meaning
Why it matters
Published affected context helps an owner decide what evidence to gather. This report has not examined your application.
4.3 medium
GitHub source severity; exploitability and local consequence require separate evidence.
As of · GitHub Advisory Database
0.342%
FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.2789. Missing scores are unknown.
As of · FIRST EPSS
02 / Applicability
The affected context
Affected versions, configuration prerequisites and known exclusions are public. Confirm each one against the deployed service.
org.yamcs:yamcs-core
source listed>= 5.13.0, <= 5.13.1
## Summary Missing authorization checks on three IAM API endpoints (`GET /api/roles`, `GET /api/roles/{name}`, `GET /api/privileges`) allow any authenticated user — regardless of their assigned permissions — to enumerate the complete list of system privileges and role definitions. An attacker with only a low-privilege account (e.g., a read-only operator) can retrieve the full privilege taxonomy of the server, including the names and assignments of all administrator-level capabilities. This information directly enables targeted privilege escalation attacks. --- ## Details Three handler methods in `IamApi.java` serve sensitive security metadata without performing any authorization check: **File:** `yamcs-core/src/main/java/org/yamcs/http/api/IamApi.java` ```java // Line 73 — GET /api/roles @Override public void listRoles(Context ctx, Empty request, Observer observer) { SecurityStore securityStore = YamcsServer.getServer().getSecurityStore(); List roles = securityStore.getDirectory().getRoles(); // No ctx.checkSystemPrivilege() call — any authenticated user proceeds ... observer.complete(responseb.build()); } // Line 87 — GET /api/ro
org.yamcs:yamcs-core
source listed<= 5.12.7
## Summary Missing authorization checks on three IAM API endpoints (`GET /api/roles`, `GET /api/roles/{name}`, `GET /api/privileges`) allow any authenticated user — regardless of their assigned permissions — to enumerate the complete list of system privileges and role definitions. An attacker with only a low-privilege account (e.g., a read-only operator) can retrieve the full privilege taxonomy of the server, including the names and assignments of all administrator-level capabilities. This information directly enables targeted privilege escalation attacks. --- ## Details Three handler methods in `IamApi.java` serve sensitive security metadata without performing any authorization check: **File:** `yamcs-core/src/main/java/org/yamcs/http/api/IamApi.java` ```java // Line 73 — GET /api/roles @Override public void listRoles(Context ctx, Empty request, Observer observer) { SecurityStore securityStore = YamcsServer.getServer().getSecurityStore(); List roles = securityStore.getDirectory().getRoles(); // No ctx.checkSystemPrivilege() call — any authenticated user proceeds ... observer.complete(responseb.build()); } // Line 87 — GET /api/ro
03 / Response
What to do next
- investigate
Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.
Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system. FIRST EPSS
A fixed release is not deployment evidence.
Check current vendor support and compatibility. After making a change, verify the deployed build and relevant runtime conditions. Keep the evidence, owner and time. An updated lockfile alone does not prove what is running.
04 / Limits
What this report cannot establish
- Customer inventory, deployment, reachability and exploitation have not been inspected.
05 / Provenance
Sources you can inspect
Each assertion retains its source. Mirrored records may repeat one underlying publisher; additional links are not independent corroboration.
- GHSA-cvw4-55pp-3hfq ↗
GitHub Advisory Database · vendor advisory
Observed . GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.
- CVE-2026-55547 ↗
FIRST EPSS · official catalog
Observed . FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.
Public revision history
Only published revisions appear here. Routine fetches do not create a material-change event.
- Revision 2 ·
Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.
- Revision 1 ·
First indexed by Null; source disclosure date is shown separately.