CVE-2024-51735: Osmedeus Web Server Vulnerable to Stored XSS, Leading to RCE

Should you act?

Normal patch cycle

No exploitation signal; fix it in your next routine update if you are affected. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.

• No confirmed exploitation. It is not in CISA’s KEV catalog and CISA’s SSVC assessment records no known exploitation. That can change quickly after a public write-up; re-check if you are affected.
• EPSS 0.5%, percentile 39: FIRST’s model estimates a 0.5% chance of exploitation activity in the next 30 days, higher than 39% of all scored CVEs (low). EPSS is a probability, not a verdict.
• Only applies if your dependency tree includes github.com/j3ssie/osmedeus (Go) <= 4.6.4, no fixed version listed. Check your lockfile, including transitive dependencies.

What it is

Osmedeus is a Workflow Engine for Offensive Security. Cross-site Scripting (XSS) occurs on the Osmedues web server when viewing results from the workflow, allowing commands to be executed on the server. When using a workflow that contains the summary module, it generates reports in HTML and Markdown formats. The default report is based on the general-template.md template.The contents of the files are read and used to generate the report. However, the file contents are not properly filtered, leading to XSS. This may lead to commands executed on the host as well. This issue is not yet resolved. Users are advised to add their own filtering or to reach out to the developer to aid in developing a patch.

From the GitHub advisory

Summary XSS occurs on the Osmedues web server when viewing results from the workflow, allowing commands to be executed on the server.

Details When using a workflow that contains the summary module, it generates reports in HTML and Markdown formats. The default report is based on the general-template.md template.

The contents of the files are read and used to generate the report. However, the file contents are not properly filtered, leading to XSS The issue starts with processing the tags, and XSS occurs when the extendTag function is called.

https://github.com/j3ssie/osmedeus/blob/815c261d44f6df1183d77b0b264060eec3168f00/core/markdown.go#L36 https://github.com/j3ssie/osmedeus/blob/815c261d44f6df1183d77b0b264060eec3168f00/core/markdown.go#L95 https://github.com/j3ssie/osmedeus/blob/815c261d44f6df1183d77b0b264060eec3168f00/core/markdown.go#L114 https://github.com/j3ssie/osmedeus/blob/815c261d44f6df1183d77b0b264060eec3168f00/core/markdown.go#L122-L124

The condition to enter this if branch must meet one of the following cases:

Weakness type: CWE-79, CWE-80, CWE-78.

Product: github.com/j3ssie/osmedeus (Go) · Assigned by: GitHub_M · Published: 2024-11-05

Affected and fixed versions

Severity scores

• Attack vector: network (remotely reachable)
• Attack complexity: low
• Attack requirements: none
• Privileges required: none (no login)
• User interaction: passive

CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.

Exploitation and urgency

• CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
• CISA SSVC assessment: exploitation none, automatable yes, technical impact total.
• FIRST EPSS (model of 2026-10-21): 0.46% probability of exploitation activity in the next 30 days; percentile 39.

Timeline

• 2024-11-05 — CVE record last updated
• 2024-11-05 — CVE record published by GitHub_M
• 2024-11-05 — GitHub-reviewed advisory GHSA-wvv7-wm5v-w2gv published (critical)

Sources and references

Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.

Vulnerability records

1. GitHub Advisory GHSA-wvv7-wm5v-w2gv github.com
2. CVE.org record CVE-2024-51735 cve.org
3. NVD entry CVE-2024-51735 nvd.nist.gov

Other references from the CVE record and advisory

1. github.com github.com
2. drive.google.com drive.google.com

Critical Go advisories · Today’s Security Digest