Vendor CVEs
OTFCC
All CVEs
88 total · sorted by risk| CVE | Vendor / Product | Sev | Risk | CVSS | EPSS | KEV | Published | Description |
|---|---|---|---|---|---|---|---|---|
| CVE-2022-35485 | Med | 0.42 | 6.5 | 0.01 | Aug 16, 2022 | OTFCC v0.10.4 was discovered to contain a segmentation violation via /release-x64/otfccdump+0x703969. | ||
| CVE-2022-35484 | Med | 0.42 | 6.5 | 0.01 | Aug 16, 2022 | OTFCC v0.10.4 was discovered to contain a segmentation violation via /release-x64/otfccdump+0x6b6a8f. | ||
| CVE-2022-35483 | Med | 0.42 | 6.5 | 0.01 | Aug 16, 2022 | OTFCC v0.10.4 was discovered to contain a segmentation violation via /release-x64/otfccdump+0x5266a8. | ||
| CVE-2022-35482 | Med | 0.42 | 6.5 | 0.01 | Aug 16, 2022 | OTFCC v0.10.4 was discovered to contain a segmentation violation via /release-x64/otfccdump+0x65f724. | ||
| CVE-2022-35481 | Med | 0.42 | 6.5 | 0.01 | Aug 16, 2022 | OTFCC v0.10.4 was discovered to contain a segmentation violation via /multiarch/memmove-vec-unaligned-erms.S. | ||
| CVE-2022-35479 | Med | 0.42 | 6.5 | 0.01 | Aug 16, 2022 | OTFCC v0.10.4 was discovered to contain a segmentation violation via /release-x64/otfccdump+0x4fbbb6. | ||
| CVE-2022-35478 | Med | 0.42 | 6.5 | 0.01 | Aug 16, 2022 | OTFCC v0.10.4 was discovered to contain a segmentation violation via /release-x64/otfccdump+0x6babea. | ||
| CVE-2022-35477 | Med | 0.42 | 6.5 | 0.01 | Aug 16, 2022 | OTFCC v0.10.4 was discovered to contain a segmentation violation via /release-x64/otfccdump+0x4fe954. | ||
| CVE-2022-35476 | Med | 0.42 | 6.5 | 0.01 | Aug 16, 2022 | OTFCC v0.10.4 was discovered to contain a segmentation violation via /release-x64/otfccdump+0x4fbc0b. | ||
| CVE-2022-35475 | Med | 0.42 | 6.5 | 0.01 | Aug 16, 2022 | OTFCC v0.10.4 was discovered to contain a heap-buffer overflow via /release-x64/otfccdump+0x6e41a8. | ||
| CVE-2022-35474 | Med | 0.42 | 6.5 | 0.01 | Aug 16, 2022 | OTFCC v0.10.4 was discovered to contain a heap-buffer overflow via /release-x64/otfccdump+0x6b544e. | ||
| CVE-2022-35473 | Med | 0.42 | 6.5 | 0.01 | Aug 16, 2022 | OTFCC v0.10.4 was discovered to contain a segmentation violation via /release-x64/otfccdump+0x4fe9a7. | ||
| CVE-2022-35472 | Med | 0.42 | 6.5 | 0.01 | Aug 16, 2022 | OTFCC v0.10.4 was discovered to contain a global overflow via /release-x64/otfccdump+0x718693. | ||
| CVE-2022-35471 | Med | 0.42 | 6.5 | 0.01 | Aug 16, 2022 | OTFCC v0.10.4 was discovered to contain a heap-buffer overflow via /release-x64/otfccdump+0x6e41b0. | ||
| CVE-2022-35470 | Med | 0.42 | 6.5 | 0.01 | Aug 16, 2022 | OTFCC v0.10.4 was discovered to contain a heap-buffer overflow via /release-x64/otfccdump+0x65fc97. | ||
| CVE-2022-35469 | Med | 0.42 | 6.5 | 0.01 | Aug 16, 2022 | OTFCC v0.10.4 was discovered to contain a segmentation violation via /x86_64-linux-gnu/libc.so.6+0xbb384. | ||
| CVE-2022-35468 | Med | 0.42 | 6.5 | 0.01 | Aug 16, 2022 | OTFCC v0.10.4 was discovered to contain a heap-buffer overflow via /release-x64/otfccdump+0x6e420d. | ||
| CVE-2022-35467 | Med | 0.42 | 6.5 | 0.01 | Aug 16, 2022 | OTFCC v0.10.4 was discovered to contain a heap-buffer overflow via /release-x64/otfccdump+0x6e41b8. | ||
| CVE-2022-35466 | Med | 0.42 | 6.5 | 0.01 | Aug 16, 2022 | OTFCC v0.10.4 was discovered to contain a heap-buffer overflow via /release-x64/otfccdump+0x6c0473. | ||
| CVE-2022-35465 | Med | 0.42 | 6.5 | 0.01 | Aug 16, 2022 | OTFCC v0.10.4 was discovered to contain a heap-buffer overflow via /release-x64/otfccdump+0x6c0414. | ||
| CVE-2022-35464 | Med | 0.42 | 6.5 | 0.01 | Aug 16, 2022 | OTFCC v0.10.4 was discovered to contain a heap-buffer overflow via /release-x64/otfccdump+0x6171b2. | ||
| CVE-2022-35463 | Med | 0.42 | 6.5 | 0.01 | Aug 16, 2022 | OTFCC v0.10.4 was discovered to contain a heap-buffer overflow via /release-x64/otfccdump+0x6b0478. | ||
| CVE-2022-35462 | Med | 0.42 | 6.5 | 0.01 | Aug 16, 2022 | OTFCC v0.10.4 was discovered to contain a heap-buffer overflow via /release-x64/otfccdump+0x6c0bc3. | ||
| CVE-2022-35461 | Med | 0.42 | 6.5 | 0.01 | Aug 16, 2022 | OTFCC v0.10.4 was discovered to contain a heap-buffer overflow via /release-x64/otfccdump+0x6c0a32. | ||
| CVE-2022-35460 | Med | 0.42 | 6.5 | 0.01 | Aug 16, 2022 | OTFCC v0.10.4 was discovered to contain a heap-buffer overflow via /release-x64/otfccdump+0x61731f. | ||
| CVE-2022-35459 | Med | 0.42 | 6.5 | 0.01 | Aug 16, 2022 | OTFCC v0.10.4 was discovered to contain a heap-buffer overflow via /release-x64/otfccdump+0x6e412a. | ||
| CVE-2022-35458 | Med | 0.42 | 6.5 | 0.01 | Aug 16, 2022 | OTFCC v0.10.4 was discovered to contain a heap-buffer overflow via /release-x64/otfccdump+0x6b05ce. | ||
| CVE-2022-35456 | Med | 0.42 | 6.5 | 0.01 | Aug 16, 2022 | OTFCC v0.10.4 was discovered to contain a heap-buffer overflow via /release-x64/otfccdump+0x617087. | ||
| CVE-2022-35455 | Med | 0.42 | 6.5 | 0.01 | Aug 16, 2022 | OTFCC v0.10.4 was discovered to contain a heap-buffer overflow via /release-x64/otfccdump+0x6b0d63. | ||
| CVE-2022-35454 | Med | 0.42 | 6.5 | 0.01 | Aug 16, 2022 | OTFCC v0.10.4 was discovered to contain a heap-buffer overflow via /release-x64/otfccdump+0x6b05aa. | ||
| CVE-2022-35453 | Med | 0.42 | 6.5 | 0.01 | Aug 16, 2022 | OTFCC v0.10.4 was discovered to contain a heap-buffer overflow via /release-x64/otfccdump+0x6c08a6. | ||
| CVE-2022-35452 | Med | 0.42 | 6.5 | 0.01 | Aug 16, 2022 | OTFCC v0.10.4 was discovered to contain a heap-buffer overflow via /release-x64/otfccdump+0x6b0b2c. | ||
| CVE-2022-35451 | Med | 0.42 | 6.5 | 0.01 | Aug 16, 2022 | OTFCC v0.10.4 was discovered to contain a heap-buffer overflow via /release-x64/otfccdump+0x6b03b5. | ||
| CVE-2022-35450 | Med | 0.42 | 6.5 | 0.01 | Aug 16, 2022 | OTFCC v0.10.4 was discovered to contain a heap-buffer overflow via /release-x64/otfccdump+0x6b84b1. | ||
| CVE-2022-35449 | Med | 0.42 | 6.5 | 0.01 | Aug 16, 2022 | OTFCC v0.10.4 was discovered to contain a heap-buffer overflow via /release-x64/otfccdump+0x6b0466. | ||
| CVE-2022-35448 | Med | 0.42 | 6.5 | 0.01 | Aug 16, 2022 | OTFCC v0.10.4 was discovered to contain a heap-buffer overflow via /release-x64/otfccdump+0x6b55af. | ||
| CVE-2022-35447 | Med | 0.42 | 6.5 | 0.01 | Aug 16, 2022 | OTFCC v0.10.4 was discovered to contain a heap-buffer overflow via /release-x64/otfccdump+0x6b04de. | ||
| CVE-2018-20588 | Med | 0.42 | 6.5 | 0.01 | Dec 30, 2018 | lib/support/unicodeconv/unicodeconv.c in libotfcc.a in otfcc v0.10.3-alpha has a buffer over-read. |
- risk 0.42cvss 6.5epss 0.01
OTFCC v0.10.4 was discovered to contain a segmentation violation via /release-x64/otfccdump+0x703969.
- risk 0.42cvss 6.5epss 0.01
OTFCC v0.10.4 was discovered to contain a segmentation violation via /release-x64/otfccdump+0x6b6a8f.
- risk 0.42cvss 6.5epss 0.01
OTFCC v0.10.4 was discovered to contain a segmentation violation via /release-x64/otfccdump+0x5266a8.
- risk 0.42cvss 6.5epss 0.01
OTFCC v0.10.4 was discovered to contain a segmentation violation via /release-x64/otfccdump+0x65f724.
- risk 0.42cvss 6.5epss 0.01
OTFCC v0.10.4 was discovered to contain a segmentation violation via /multiarch/memmove-vec-unaligned-erms.S.
- risk 0.42cvss 6.5epss 0.01
OTFCC v0.10.4 was discovered to contain a segmentation violation via /release-x64/otfccdump+0x4fbbb6.
- risk 0.42cvss 6.5epss 0.01
OTFCC v0.10.4 was discovered to contain a segmentation violation via /release-x64/otfccdump+0x6babea.
- risk 0.42cvss 6.5epss 0.01
OTFCC v0.10.4 was discovered to contain a segmentation violation via /release-x64/otfccdump+0x4fe954.
- risk 0.42cvss 6.5epss 0.01
OTFCC v0.10.4 was discovered to contain a segmentation violation via /release-x64/otfccdump+0x4fbc0b.
- risk 0.42cvss 6.5epss 0.01
OTFCC v0.10.4 was discovered to contain a heap-buffer overflow via /release-x64/otfccdump+0x6e41a8.
- risk 0.42cvss 6.5epss 0.01
OTFCC v0.10.4 was discovered to contain a heap-buffer overflow via /release-x64/otfccdump+0x6b544e.
- risk 0.42cvss 6.5epss 0.01
OTFCC v0.10.4 was discovered to contain a segmentation violation via /release-x64/otfccdump+0x4fe9a7.
- risk 0.42cvss 6.5epss 0.01
OTFCC v0.10.4 was discovered to contain a global overflow via /release-x64/otfccdump+0x718693.
- risk 0.42cvss 6.5epss 0.01
OTFCC v0.10.4 was discovered to contain a heap-buffer overflow via /release-x64/otfccdump+0x6e41b0.
- risk 0.42cvss 6.5epss 0.01
OTFCC v0.10.4 was discovered to contain a heap-buffer overflow via /release-x64/otfccdump+0x65fc97.
- risk 0.42cvss 6.5epss 0.01
OTFCC v0.10.4 was discovered to contain a segmentation violation via /x86_64-linux-gnu/libc.so.6+0xbb384.
- risk 0.42cvss 6.5epss 0.01
OTFCC v0.10.4 was discovered to contain a heap-buffer overflow via /release-x64/otfccdump+0x6e420d.
- risk 0.42cvss 6.5epss 0.01
OTFCC v0.10.4 was discovered to contain a heap-buffer overflow via /release-x64/otfccdump+0x6e41b8.
- risk 0.42cvss 6.5epss 0.01
OTFCC v0.10.4 was discovered to contain a heap-buffer overflow via /release-x64/otfccdump+0x6c0473.
- risk 0.42cvss 6.5epss 0.01
OTFCC v0.10.4 was discovered to contain a heap-buffer overflow via /release-x64/otfccdump+0x6c0414.
- risk 0.42cvss 6.5epss 0.01
OTFCC v0.10.4 was discovered to contain a heap-buffer overflow via /release-x64/otfccdump+0x6171b2.
- risk 0.42cvss 6.5epss 0.01
OTFCC v0.10.4 was discovered to contain a heap-buffer overflow via /release-x64/otfccdump+0x6b0478.
- risk 0.42cvss 6.5epss 0.01
OTFCC v0.10.4 was discovered to contain a heap-buffer overflow via /release-x64/otfccdump+0x6c0bc3.
- risk 0.42cvss 6.5epss 0.01
OTFCC v0.10.4 was discovered to contain a heap-buffer overflow via /release-x64/otfccdump+0x6c0a32.
- risk 0.42cvss 6.5epss 0.01
OTFCC v0.10.4 was discovered to contain a heap-buffer overflow via /release-x64/otfccdump+0x61731f.
- risk 0.42cvss 6.5epss 0.01
OTFCC v0.10.4 was discovered to contain a heap-buffer overflow via /release-x64/otfccdump+0x6e412a.
- risk 0.42cvss 6.5epss 0.01
OTFCC v0.10.4 was discovered to contain a heap-buffer overflow via /release-x64/otfccdump+0x6b05ce.
- risk 0.42cvss 6.5epss 0.01
OTFCC v0.10.4 was discovered to contain a heap-buffer overflow via /release-x64/otfccdump+0x617087.
- risk 0.42cvss 6.5epss 0.01
OTFCC v0.10.4 was discovered to contain a heap-buffer overflow via /release-x64/otfccdump+0x6b0d63.
- risk 0.42cvss 6.5epss 0.01
OTFCC v0.10.4 was discovered to contain a heap-buffer overflow via /release-x64/otfccdump+0x6b05aa.
- risk 0.42cvss 6.5epss 0.01
OTFCC v0.10.4 was discovered to contain a heap-buffer overflow via /release-x64/otfccdump+0x6c08a6.
- risk 0.42cvss 6.5epss 0.01
OTFCC v0.10.4 was discovered to contain a heap-buffer overflow via /release-x64/otfccdump+0x6b0b2c.
- risk 0.42cvss 6.5epss 0.01
OTFCC v0.10.4 was discovered to contain a heap-buffer overflow via /release-x64/otfccdump+0x6b03b5.
- risk 0.42cvss 6.5epss 0.01
OTFCC v0.10.4 was discovered to contain a heap-buffer overflow via /release-x64/otfccdump+0x6b84b1.
- risk 0.42cvss 6.5epss 0.01
OTFCC v0.10.4 was discovered to contain a heap-buffer overflow via /release-x64/otfccdump+0x6b0466.
- risk 0.42cvss 6.5epss 0.01
OTFCC v0.10.4 was discovered to contain a heap-buffer overflow via /release-x64/otfccdump+0x6b55af.
- risk 0.42cvss 6.5epss 0.01
OTFCC v0.10.4 was discovered to contain a heap-buffer overflow via /release-x64/otfccdump+0x6b04de.
- risk 0.42cvss 6.5epss 0.01
lib/support/unicodeconv/unicodeconv.c in libotfcc.a in otfcc v0.10.3-alpha has a buffer over-read.
Page 2 of 2