Security readout for executives and security teams
Plain-English summary
CVE-2019-19379 affects MISP 2.4.118 and lets users bypass intended restrictions on tagging data. For an organization using MISP, this could undermine trust in threat-intelligence labels and handling workflows. The source bundle does not provide CVSS scoring, a fixed version, or evidence of active exploitation.
Executive priority
Treat this as a targeted integrity risk for MISP-based intelligence operations. Prioritize if MISP tags drive incident severity, sharing controls, automated workflows, or partner-facing intelligence. Urgency is lower if MISP is not used or tagging is not security-critical.
Technical view
The issue is in MISP app/Controller/TagsController.php. The CVE description states that users can bypass intended restrictions on tagging data in version 2.4.118. A MISP commit is referenced, but the provided sources do not state affected version ranges beyond 2.4.118, root cause details, or complete remediation instructions.
Likely exposure
Exposure is likely limited to organizations running MISP 2.4.118 where authenticated users have access to tagging-related functionality. The provided sources do not identify other affected products, broader version ranges, or unauthenticated exposure.
Exploitation context
The CVE is not listed as KEV in the bundle, and no cited source reports active exploitation. The available evidence supports a restriction-bypass issue, not public weaponization or mass exploitation.
Researcher notes
The public bundle is sparse: no CVSS vector, CWE, exploit evidence, detailed affected range, or named fixed release. Analysis should stay anchored to MISP 2.4.118, TagsController.php, and the referenced MISP commit until additional vendor data is reviewed.
Mitigation direction
- Identify any MISP 2.4.118 deployments in production or trusted-intelligence environments.
- Check MISP vendor guidance and the referenced commit for fixed release information.
- Restrict tagging permissions to trusted users until remediation is confirmed.
- Review recent tagging changes for unexpected or policy-violating labels.
- Prioritize upgrade or patch validation before relying on tag-based workflows.
Validation and detection
- Confirm the deployed MISP version and whether TagsController.php includes the referenced change.
- Review MISP role and permission settings for tag creation and assignment.
- Check audit logs for unusual tag additions, removals, or changes.
- Test tagging restrictions with non-admin accounts in a controlled environment.
- Verify vendor release notes before declaring the issue remediated.
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.
CVE-2019-19379 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/e05dc512a437284f14624da23cca4a829a76aebfCVE 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.