OpenCTI: Synchronizer SSRF: stream fetch has no URL validation
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| OpenCTI-Platform | opencti | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Opencti-platform | Opencti |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.415% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Opencti-platform
Opencti-platform opencti |
|
| Vendors & Products |
Opencti-platform
Opencti-platform opencti |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | OpenCTI is an open source platform for managing cyber threat intelligence knowledge and observables. Prior to 7.260701.0, the synchronizerFetch GraphQL query called fetchRemoteStreams after checking only that a remote stream URL used HTTP or HTTPS. The backend did not apply the ingestion deny list or reject private, loopback, and link-local destinations, allowing an authenticated account with the INGESTION capability to make OpenCTI request internal services and cloud metadata endpoints. Returned connection errors could distinguish open HTTP ports, open non-HTTP ports, and closed ports, enabling internal network scanning, while compatible endpoint responses could disclose internal data. This issue is fixed in version 7.260701.0. | |
| Title | OpenCTI: Synchronizer SSRF: stream fetch has no URL validation | |
| Weaknesses | CWE-918 | |
| References |
| |
| Metrics |
cvssV3_1
|