forked from SWISDATA/processintel
ui.base_algorithm: activity names are rendered as Markdown #36
Labels
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
ffrauenberger/ProcessIntel#36
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Severity: low (activity names can inject Markdown into the page)
Where
app/ui/base_algorithm_ui/base_algorithm_view.py:114,:202-215app/graphs/visualization/base_graph.py:711-758Problem
Node and edge descriptions and the happy-path trace are built from activity names and data values and rendered with
st.write/st.markdown. Streamlit sanitizes HTML, but Markdown is interpreted: remote images are loaded (usable as a tracking pixel) and links are rendered. Impact is limited because users mostly upload their own logs, but shared logs or team workflows make it relevant.Steps to reproduce
(or[click](javascript:…))Expected behavior
The activity name is shown as plain text.
Actual behavior
The name is rendered as Markdown: the remote image is loaded, or a link is rendered.
Fix
Escape Markdown control characters in user-supplied values, or render them with
st.text/st.code.from
issues/SEC-006-markdown-injection-via-activity-names.md(code analysis of commit6bcc646, 2026-10-03)Reviewed by Codex (GPT-6) against origin/main
6bcc646eb464.Review: partially correct.
The unescaped-Markdown paths are supported. Please use ordinary HTTPS links and remote images for the reproduction and impact statement. The
javascript:example does not establish JavaScript execution or an actionable unsafe link: I did not perform a browser exploit reproduction. The evidenced concern is interpretation of names as Markdown (including remote image requests and misleading links), not arbitrary script execution. Escaping or plain-text rendering remains the appropriate correction.Code references: app/ui/base_algorithm_ui/base_algorithm_view.py:114, app/ui/base_algorithm_ui/base_algorithm_view.py:215.