CVE-2023-25230
SSRF in Loonflow Project Loonflow r2.0.14
Raw vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2023-25230 is a medium-severity SSRF (CWE-918) vulnerability in Loonflow Project Loonflow. Its CVSS base score is 4.9 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Proxy (T1090); ranked in the top 48% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-29193
Vulnerability Data
A Server-Side Request Forgery (SSRF) in loonflow r2.0.14 allows attackers to force the application to make arbitrary requests via manipulation of the hook_url parameter.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
MITRE ATT&CK v20.0
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.3.6V1.5.3V5.3.2V10.4.7
Likely Mitigating Controls
Our mappings. Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Penetration testing attempts server-side requests to internal resources, identifying SSRF weaknesses for remediation.
Outbound connections to external resources can be monitored and limited at the boundary, reducing SSRF impact.
Validates server-side URLs and resource references to block SSRF attempts.
Detects server-side request forgery through monitoring of unexpected outbound connections.
Mitigating Controls (NIST CSF 2.0)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.
Secure development practices directly include input validation and destination allow-listing that prevent SSRF.
Runtime monitoring of web applications and services can detect anomalous outbound requests indicative of SSRF.
Vulnerability identification processes can discover and record SSRF flaws in web applications.
Network segmentation and egress controls can limit the damage from successful SSRF requests.
Mitigating Controls (ISO/IEC 27001:2022 Annex A)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.
A.8.29's testing programme (code review, static analysis, vulnerability scanning, penetration testing, architecture review) covers every detection method CWE-918 rates High or Moderate, and the clause explicitly names code review for un-anticipated inputs and acceptance testing of acquired products, so no further act of finding is left over — the same logic the owner applied to A.8.29 finds CWE-89 = full.
A.8.20's firewall and network filtering controls (items i, j, n) can block a meaningful portion of SSRF exploitation paths — particularly outbound connections to internal networks, cloud metadata endpoints, and disallowed protocols — but the application-layer URL validation defect remains and SSRF can still be exploited via external attacker-controlled destinations, DNS rebinding, and allowed internal services, leaving a nameable remainder.
A.8.21's network connection controls, egress restrictions and monitoring of network service use can block some SSRF exploitation (e.g., preventing the server from reaching internal services, cloud metadata endpoints, or arbitrary ports), but the application-level URL-fetching vulnerability remains and can still be exploited against any destination the network permits.
Network segregation with gateway controls blocks SSRF exploitation against internal network resources (internal admin panels, cross-domain port scanning, internal services), which is a major portion of the weakness's damage surface, but the weakness remains exploitable for external destinations, localhost services, and cloud metadata endpoints that the segregation does not reach.
A.8.28 mandates secure coding principles that include URL/destination validation and allowlisting practices which, where followed, prevent SSRF from being introduced; but the clause is a practice-based control whose effect depends on developer implementation rigor, so it catches only a minority of instances — the same reading that graded A.8.28 -> CWE-502 and A.8.28 -> CWE-79 at `partial`, and the clause's declared ceiling on this verb.
A.8.30's contractual requirements for acceptance testing (8.29) and evidence of testing for malicious content and known vulnerabilities cause SSRF to be discovered in delivered outsourced code, but the finding is performed by the testing programme A.8.30 contracts for rather than by A.8.30 itself, and the effect is reduced because it is mediated through a supplier relationship.