vulnerability / NVI-00013137 / Revision 1
Yamcs has DOM XSS in Extension Routing
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
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
**Attack type**: Unauthenticated remote **Impact**: Execution of arbitrary JavaScript in a user’s browser. **Affected components**: extension.matcher.ts:12, extension.component.ts:40, app.component.ts:134. Yamcs is vulnerable to cross-site scripting in the /ext URL endpoint. By inputting specially crafted code into the URL, an attacker can execute arbitrary JavaScript code in a user’s browser. This URL may be sent to a user via a phishing email. Steps to Reproduce: 1. Start a Yamcs instance. 2. Insert the following URL into the browser and press enter (change ‘myproject’ to the name of your instance): ``` http://localhost:8090/ext/img%20src%3Dx%20onerror%3Dalert%281%29?c=myproject ``` 3. You will receive an alert with the number ‘1’ in it. Recommendations: 1. Use document.createElement instead of innerHTML in extension.component.ts. 2. Validate the extension against registered plugin IDs. 3. Enforce a strict custom-element-name regex before mounting.
org.yamcs:yamcs-core
source listed<= 5.12.7
**Attack type**: Unauthenticated remote **Impact**: Execution of arbitrary JavaScript in a user’s browser. **Affected components**: extension.matcher.ts:12, extension.component.ts:40, app.component.ts:134. Yamcs is vulnerable to cross-site scripting in the /ext URL endpoint. By inputting specially crafted code into the URL, an attacker can execute arbitrary JavaScript code in a user’s browser. This URL may be sent to a user via a phishing email. Steps to Reproduce: 1. Start a Yamcs instance. 2. Insert the following URL into the browser and press enter (change ‘myproject’ to the name of your instance): ``` http://localhost:8090/ext/img%20src%3Dx%20onerror%3Dalert%281%29?c=myproject ``` 3. You will receive an alert with the number ‘1’ in it. Recommendations: 1. Use document.createElement instead of innerHTML in extension.component.ts. 2. Validate the extension against registered plugin IDs. 3. Enforce a strict custom-element-name regex before mounting.
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. GitHub Advisory Database
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-9272-wg2r-7xmx ↗
GitHub Advisory Database · vendor advisory
Observed . GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.
Public revision history
Only published revisions appear here. Routine fetches do not create a material-change event.
- Revision 1 ·
First indexed by Null; source disclosure date is shown separately.