CVE-2019-19379 json
In app/Controller/TagsController.php in MISP 2.4.118, users can bypass intended restrictions on tagging data.
published 6y ago modified 4mo ago also EUVD-2019-9000
- cvss
- 5.3
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.1%
- EPSS 1.1% chance of exploitation in 30 days, percentile 66%
- public exploits
- 0
- none known
Summary
In app/Controller/TagsController.php in MISP 2.4.118, users can bypass intended restrictions on tagging data.
Patch / fix
- github.com/MISP/MISP@e05dc51 commit
Is CVE-2019-19379 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
1.11% chance of exploitation in the next 30 days, higher than 66% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:P/A:N |
References
-
github.com
/MISP/MISP/commit/e05dc512a437284f14624da23cca4a829a76aebf
patch, third-party-advisory
Sources
- CVE List CVE-2019-19379
- NVD CVE-2019-19379
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.