Unrestricted network access between execution contexts in KNIME Business Hub
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.19.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
KNIME Business Hub is affected, where an authenticated user can reach open network ports on executors belonging to other execution contexts. This could let that user access services without further authentication if they know the target executor's IP address and a port has been opened by a running workflow.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
Unrestricted network access between execution contexts in KNIME Business Hub before version 1.19.0 allows an authenticated remote user to access open network ports on executors in different execution contexts. This only poses a security issue if the IP address of the attacked executor is know and there are open network ports that provided access without further authentication. By default no network ports are open. However, depending on the running workflows, ports may be opened and provide an attack surface. As a workaround, network policies can be created manually.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- KNIME KNIME Business Hub
fixed in 1.19.0