Security readout for executives and security teams
Plain-English summary
MISP versions through 2.4.133 contain a server-side request forgery issue in the REST client. A user-controlled use_full_path parameter could make MISP request an arbitrary URL. Business risk depends on who can use that client and what internal network resources the MISP server can reach.
Executive priority
Treat this as a near-term hardening and upgrade item, especially if MISP is internet-accessible or used by many analysts. The source evidence does not support emergency active-exploitation handling, but SSRF can expose internal systems if network controls are weak.
Technical view
The CVE describes SSRF in MISP's REST client caused by accepting an arbitrary URL through use_full_path. The public record identifies MISP through 2.4.133 as affected and references a MISP code commit. No CVSS score, CWE, affected CPE list, or detailed fixed release is provided in the source bundle.
Likely exposure
Exposure is most likely for organizations running MISP through 2.4.133 where untrusted or lower-trust users can access the REST client functionality. Impact may increase if the MISP host can reach internal metadata services, admin panels, or private APIs.
Exploitation context
The provided sources do not show CISA KEV listing or confirmed active exploitation. The issue is publicly disclosed and source-referenced, but exploitability details, required privileges, and attack complexity are not provided in the bundle.
Researcher notes
Key missing details are CVSS, required privileges, fixed release mapping, and exploit observations. The commit reference is the main technical anchor. Validation should focus on version, reachable internal services from the MISP host, and whether REST client use is limited to trusted users.
Mitigation direction
- Identify all MISP instances and confirm their running versions.
- Review MISP guidance and the referenced commit for the corrected behavior.
- Upgrade MISP beyond affected versions when vendor guidance confirms the fixed release.
- Restrict REST client access to trusted administrative users only.
- Limit outbound network access from MISP to required destinations.
Validation and detection
- Check whether any deployed MISP instance is version 2.4.133 or earlier.
- Review MISP roles to identify users with REST client access.
- Inspect outbound firewall rules from the MISP server.
- Check logs for unusual REST client requests to internal or unexpected URLs.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
Cloud metadata behavior lookup
The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2020-28043 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/MISP/MISP/commit/6e81c8ee8ad19576c055b5c4773f914b918f32beCVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
