VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
299422 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2017-9440 | redhat_vex | ImageMagick: Memory leak in the ReadPSDChannel function | known affected: 16 | 2026-05-13T04:07:52+00:00 | Vulnerability · Source |
| CVE-2017-9439 | redhat_vex | ImageMagick: Memory leak in the ReadPDBImage function | known affected: 16 | 2026-05-13T04:07:50+00:00 | Vulnerability · Source |
| CVE-2017-9412 | redhat_vex | lame: Multiple vulnerabilities | known affected: 3 | 2026-05-13T04:07:47+00:00 | Vulnerability · Source |
| CVE-2017-9409 | redhat_vex | ImageMagick: Memory leak in the ReadMPCImage function | known affected: 16 | 2026-05-13T04:07:43+00:00 | Vulnerability · Source |
| CVE-2017-9408 | redhat_vex | poppler: Memory leak in the Object::initArray function | known affected: 22 | 2026-05-13T04:07:42+00:00 | Vulnerability · Source |
| CVE-2017-9407 | redhat_vex | ImageMagick: Memory leak in the ReadPALMImage function | known affected: 16 | 2026-05-13T04:07:38+00:00 | Vulnerability · Source |
| CVE-2017-9406 | redhat_vex | poppler: Memory leak in the gmalloc function in gmem.cc | known affected: 22 | 2026-05-13T04:07:36+00:00 | Vulnerability · Source |
| CVE-2017-9405 | redhat_vex | ImageMagick: Memory leak in the ReadICONImage function | known affected: 16 | 2026-05-13T04:07:34+00:00 | Vulnerability · Source |
| CVE-2017-9404 | redhat_vex | libtiff: Memory leak in OJPEGReadHeaderInfoSecTablesQTable | known affected: 12 | 2026-05-13T04:07:32+00:00 | Vulnerability · Source |
| CVE-2017-9403 | redhat_vex | libtiff: Memory leak in TIFFReadDirEntryLong8Array | known affected: 12 | 2026-05-13T04:07:27+00:00 | Vulnerability · Source |
| CVE-2017-9330 | redhat_vex | Qemu: usb: ohci: infinite loop due to incorrect return value | known affected: 1 known not affected: 57 | 2026-05-13T04:07:25+00:00 | Vulnerability · Source |
| CVE-2017-9262 | redhat_vex | ImageMagick: Memory leak in the ReadJNGImage function | known affected: 16 | 2026-05-13T04:07:22+00:00 | Vulnerability · Source |
| CVE-2017-9261 | redhat_vex | ImageMagick: Memory leak in the ReadMNGImage function | known affected: 16 | 2026-05-13T04:07:18+00:00 | Vulnerability · Source |
| CVE-2017-9260 | redhat_vex | soundtouch: Heap-buffer over-read in the TDStretchSSE::calcCrossCorr function | known affected: 2 | 2026-05-13T04:07:16+00:00 | Vulnerability · Source |
| CVE-2017-9259 | redhat_vex | soundtouch: Memory allocation error in the TDStretch::acceptNewOverlapLength function | known affected: 2 | 2026-05-13T04:07:13+00:00 | Vulnerability · Source |
| CVE-2017-9258 | redhat_vex | soundtouch: Infinite loop in the TDStretch::processSamples function | known affected: 2 | 2026-05-13T04:07:09+00:00 | Vulnerability · Source |
| CVE-2017-9239 | redhat_vex | exiv2: Segmentation fault in TiffImageEntry::doWriteImage function | known affected: 8 | 2026-05-13T04:07:07+00:00 | Vulnerability · Source |
| CVE-2017-9210 | redhat_vex | qpdf: Infinite loop related to unparse functions | known affected: 4 | 2026-05-13T04:07:03+00:00 | Vulnerability · Source |
| CVE-2017-9209 | redhat_vex | qpdf: Infinite loop related to QPDFObjectHandle::parseInternal | known affected: 4 | 2026-05-13T04:07:01+00:00 | Vulnerability · Source |
| CVE-2017-9208 | redhat_vex | qpdf: Infinite loop related to releaseResolved functions | known affected: 4 | 2026-05-13T04:06:59+00:00 | Vulnerability · Source |
| CVE-2017-9200 | redhat_vex | autotrace: Multiple security issues | known affected: 5 | 2026-05-13T04:06:56+00:00 | Vulnerability · Source |
| CVE-2017-9198 | redhat_vex | autotrace: Multiple security issues | known affected: 5 | 2026-05-13T04:06:52+00:00 | Vulnerability · Source |
| CVE-2017-9199 | redhat_vex | autotrace: Multiple security issues | known affected: 5 | 2026-05-13T04:06:52+00:00 | Vulnerability · Source |
| CVE-2017-9197 | redhat_vex | autotrace: Multiple security issues | known affected: 5 | 2026-05-13T04:06:45+00:00 | Vulnerability · Source |
| CVE-2017-9196 | redhat_vex | autotrace: Multiple security issues | known affected: 5 | 2026-05-13T04:06:42+00:00 | Vulnerability · Source |
| CVE-2017-9195 | redhat_vex | autotrace: Multiple security issues | known affected: 5 | 2026-05-13T04:06:39+00:00 | Vulnerability · Source |
| CVE-2017-9194 | redhat_vex | autotrace: Multiple security issues | known affected: 5 | 2026-05-13T04:06:34+00:00 | Vulnerability · Source |
| CVE-2017-9193 | redhat_vex | autotrace: Multiple security issues | known affected: 5 | 2026-05-13T04:06:31+00:00 | Vulnerability · Source |
| CVE-2017-9192 | redhat_vex | autotrace: Multiple security issues | known affected: 5 | 2026-05-13T04:06:27+00:00 | Vulnerability · Source |
| CVE-2017-9191 | redhat_vex | autotrace: Multiple security issues | known affected: 5 | 2026-05-13T04:06:24+00:00 | Vulnerability · Source |
| CVE-2017-9190 | redhat_vex | autotrace: Multiple security issues | known affected: 5 | 2026-05-13T04:06:22+00:00 | Vulnerability · Source |
| CVE-2017-9189 | redhat_vex | autotrace: Multiple security issues | known affected: 5 | 2026-05-13T04:06:17+00:00 | Vulnerability · Source |
| CVE-2017-9188 | redhat_vex | autotrace: Multiple security issues | known affected: 5 | 2026-05-13T04:06:14+00:00 | Vulnerability · Source |
| CVE-2017-9187 | redhat_vex | autotrace: Multiple security issues | known affected: 5 | 2026-05-13T04:06:10+00:00 | Vulnerability · Source |
| CVE-2017-9185 | redhat_vex | autotrace: Multiple security issues | known affected: 5 | 2026-05-13T04:06:08+00:00 | Vulnerability · Source |
| CVE-2017-9186 | redhat_vex | autotrace: Multiple security issues | known affected: 5 | 2026-05-13T04:06:07+00:00 | Vulnerability · Source |
| CVE-2017-9184 | redhat_vex | autotrace: Multiple security issues | known affected: 5 | 2026-05-13T04:06:03+00:00 | Vulnerability · Source |
| CVE-2017-9183 | redhat_vex | autotrace: Multiple security issues | known affected: 5 | 2026-05-13T04:06:01+00:00 | Vulnerability · Source |
| CVE-2017-9182 | redhat_vex | autotrace: Multiple security issues | known affected: 5 | 2026-05-13T04:05:57+00:00 | Vulnerability · Source |
| CVE-2017-9181 | redhat_vex | autotrace: Multiple security issues | known affected: 5 | 2026-05-13T04:05:55+00:00 | Vulnerability · Source |
| CVE-2017-9180 | redhat_vex | autotrace: Multiple security issues | known affected: 5 | 2026-05-13T04:05:51+00:00 | Vulnerability · Source |
| CVE-2017-9179 | redhat_vex | autotrace: Multiple security issues | known affected: 5 | 2026-05-13T04:05:47+00:00 | Vulnerability · Source |
| CVE-2017-9178 | redhat_vex | autotrace: Multiple security issues | known affected: 5 | 2026-05-13T04:05:44+00:00 | Vulnerability · Source |
| CVE-2017-9177 | redhat_vex | autotrace: Multiple security issues | known affected: 5 | 2026-05-13T04:05:42+00:00 | Vulnerability · Source |
| CVE-2017-9176 | redhat_vex | autotrace: Multiple security issues | known affected: 5 | 2026-05-13T04:05:39+00:00 | Vulnerability · Source |
| CVE-2017-9175 | redhat_vex | autotrace: Multiple security issues | known affected: 5 | 2026-05-13T04:05:37+00:00 | Vulnerability · Source |
| CVE-2017-9174 | redhat_vex | autotrace: Multiple security issues | known affected: 5 | 2026-05-13T04:05:35+00:00 | Vulnerability · Source |
| CVE-2017-9173 | redhat_vex | autotrace: Multiple security issues | known affected: 5 | 2026-05-13T04:05:33+00:00 | Vulnerability · Source |
| CVE-2017-9172 | redhat_vex | autotrace: Multiple security issues | known affected: 5 | 2026-05-13T04:05:31+00:00 | Vulnerability · Source |
| CVE-2017-9171 | redhat_vex | autotrace: Multiple security issues | known affected: 5 | 2026-05-13T04:05:27+00:00 | Vulnerability · Source |