CWE-787
Out-of-bounds Write
Description
The product writes data past the end, or before the beginning, of the intended buffer.
Hierarchy (View 1000)
CVEs mapped to this weakness (15,178)
page 636 of 759| CVE | Vendor / Product | Sev | Risk | CVSS | EPSS | KEV | Published | Description |
|---|---|---|---|---|---|---|---|---|
| CVE-2022-35042 | Med | 0.42 | 6.5 | 0.01 | Oct 14, 2022 | OTFCC commit 617837b was discovered to contain a heap buffer overflow via /release-x64/otfccdump+0x4adb11. | ||
| CVE-2022-35041 | Med | 0.42 | 6.5 | 0.01 | Oct 14, 2022 | OTFCC commit 617837b was discovered to contain a heap buffer overflow via /release-x64/otfccdump+0x6b558f. | ||
| CVE-2022-35040 | Med | 0.42 | 6.5 | 0.01 | Oct 14, 2022 | OTFCC commit 617837b was discovered to contain a heap buffer overflow via /release-x64/otfccdump+0x6b5567. | ||
| CVE-2022-40160 | Med | 0.42 | 6.5 | 0.01 | Oct 6, 2022 | ** DISPUTED ** This record was originally reported by the oss-fuzz project who failed to consider the security context in which JXPath is intended to be used and failed to contact the JXPath maintainers prior to requesting the CVE allocation. The CVE was then allocated by Google… | ||
| CVE-2022-40159 | Med | 0.42 | 6.5 | 0.01 | Oct 6, 2022 | ** DISPUTED ** This record was originally reported by the oss-fuzz project who failed to consider the security context in which JXPath is intended to be used and failed to contact the JXPath maintainers prior to requesting the CVE allocation. The CVE was then allocated by Google… | ||
| CVE-2022-35039 | Med | 0.42 | 6.5 | 0.01 | Sep 22, 2022 | OTFCC commit 617837b was discovered to contain a heap buffer overflow via /release-x64/otfccdump+0x6e20a0. | ||
| CVE-2022-35038 | Med | 0.42 | 6.5 | 0.01 | Sep 22, 2022 | OTFCC commit 617837b was discovered to contain a heap buffer overflow via /release-x64/otfccdump+0x6b064d. | ||
| CVE-2022-35037 | Med | 0.42 | 6.5 | 0.01 | Sep 22, 2022 | OTFCC commit 617837b was discovered to contain a heap buffer overflow via /release-x64/otfccdump+0x6adb1e. | ||
| CVE-2022-35036 | Med | 0.42 | 6.5 | 0.01 | Sep 22, 2022 | OTFCC commit 617837b was discovered to contain a heap buffer overflow via /release-x64/otfccdump+0x6e1fc8. | ||
| CVE-2022-35035 | Med | 0.42 | 6.5 | 0.01 | Sep 22, 2022 | OTFCC commit 617837b was discovered to contain a heap buffer overflow via /release-x64/otfccdump+0x6b559f. | ||
| CVE-2022-35034 | Med | 0.42 | 6.5 | 0.01 | Sep 22, 2022 | OTFCC commit 617837b was discovered to contain a heap buffer overflow via /release-x64/otfccdump+0x6e7e3d. | ||
| CVE-2022-35031 | Med | 0.42 | 6.5 | 0.01 | Sep 22, 2022 | OTFCC commit 617837b was discovered to contain a segmentation violation via /release-x64/otfccdump+0x703969. | ||
| CVE-2022-35030 | Med | 0.42 | 6.5 | 0.01 | Sep 22, 2022 | OTFCC commit 617837b was discovered to contain a segmentation violation via /release-x64/otfccdump+0x4fe954. | ||
| CVE-2022-35029 | Med | 0.42 | 6.5 | 0.01 | Sep 22, 2022 | OTFCC commit 617837b was discovered to contain a segmentation violation via /release-x64/otfccdump+0x6babea. | ||
| CVE-2022-35028 | Med | 0.42 | 6.5 | 0.01 | Sep 22, 2022 | OTFCC commit 617837b was discovered to contain a segmentation violation via /release-x64/otfccdump+0x4fbbb6. | ||
| CVE-2022-35027 | Med | 0.42 | 6.5 | 0.01 | Sep 22, 2022 | OTFCC commit 617837b was discovered to contain a segmentation violation via /release-x64/otfccdump+0x4fe9a7. | ||
| CVE-2022-35026 | Med | 0.42 | 6.5 | 0.01 | Sep 22, 2022 | OTFCC commit 617837b was discovered to contain a segmentation violation via /release-x64/otfccdump+0x4fbc0b. | ||
| CVE-2022-35025 | Med | 0.42 | 6.5 | 0.01 | Sep 22, 2022 | OTFCC commit 617837b was discovered to contain a segmentation violation via /release-x64/otfccdump+0x5266a8. | ||
| CVE-2022-35023 | Med | 0.42 | 6.5 | 0.01 | Sep 22, 2022 | OTFCC commit 617837b was discovered to contain a segmentation violation via /lib/x86_64-linux-gnu/libc.so.6+0xbb384. | ||
| CVE-2022-35022 | Med | 0.42 | 6.5 | 0.01 | Sep 22, 2022 | OTFCC commit 617837b was discovered to contain a segmentation violation via /release-x64/otfccdump+0x6badae. |
- risk 0.42cvss 6.5epss 0.01
OTFCC commit 617837b was discovered to contain a heap buffer overflow via /release-x64/otfccdump+0x4adb11.
- risk 0.42cvss 6.5epss 0.01
OTFCC commit 617837b was discovered to contain a heap buffer overflow via /release-x64/otfccdump+0x6b558f.
- risk 0.42cvss 6.5epss 0.01
OTFCC commit 617837b was discovered to contain a heap buffer overflow via /release-x64/otfccdump+0x6b5567.
- risk 0.42cvss 6.5epss 0.01
** DISPUTED ** This record was originally reported by the oss-fuzz project who failed to consider the security context in which JXPath is intended to be used and failed to contact the JXPath maintainers prior to requesting the CVE allocation. The CVE was then allocated by Google…
- risk 0.42cvss 6.5epss 0.01
** DISPUTED ** This record was originally reported by the oss-fuzz project who failed to consider the security context in which JXPath is intended to be used and failed to contact the JXPath maintainers prior to requesting the CVE allocation. The CVE was then allocated by Google…
- risk 0.42cvss 6.5epss 0.01
OTFCC commit 617837b was discovered to contain a heap buffer overflow via /release-x64/otfccdump+0x6e20a0.
- risk 0.42cvss 6.5epss 0.01
OTFCC commit 617837b was discovered to contain a heap buffer overflow via /release-x64/otfccdump+0x6b064d.
- risk 0.42cvss 6.5epss 0.01
OTFCC commit 617837b was discovered to contain a heap buffer overflow via /release-x64/otfccdump+0x6adb1e.
- risk 0.42cvss 6.5epss 0.01
OTFCC commit 617837b was discovered to contain a heap buffer overflow via /release-x64/otfccdump+0x6e1fc8.
- risk 0.42cvss 6.5epss 0.01
OTFCC commit 617837b was discovered to contain a heap buffer overflow via /release-x64/otfccdump+0x6b559f.
- risk 0.42cvss 6.5epss 0.01
OTFCC commit 617837b was discovered to contain a heap buffer overflow via /release-x64/otfccdump+0x6e7e3d.
- risk 0.42cvss 6.5epss 0.01
OTFCC commit 617837b was discovered to contain a segmentation violation via /release-x64/otfccdump+0x703969.
- risk 0.42cvss 6.5epss 0.01
OTFCC commit 617837b was discovered to contain a segmentation violation via /release-x64/otfccdump+0x4fe954.
- risk 0.42cvss 6.5epss 0.01
OTFCC commit 617837b was discovered to contain a segmentation violation via /release-x64/otfccdump+0x6babea.
- risk 0.42cvss 6.5epss 0.01
OTFCC commit 617837b was discovered to contain a segmentation violation via /release-x64/otfccdump+0x4fbbb6.
- risk 0.42cvss 6.5epss 0.01
OTFCC commit 617837b was discovered to contain a segmentation violation via /release-x64/otfccdump+0x4fe9a7.
- risk 0.42cvss 6.5epss 0.01
OTFCC commit 617837b was discovered to contain a segmentation violation via /release-x64/otfccdump+0x4fbc0b.
- risk 0.42cvss 6.5epss 0.01
OTFCC commit 617837b was discovered to contain a segmentation violation via /release-x64/otfccdump+0x5266a8.
- risk 0.42cvss 6.5epss 0.01
OTFCC commit 617837b was discovered to contain a segmentation violation via /lib/x86_64-linux-gnu/libc.so.6+0xbb384.
- risk 0.42cvss 6.5epss 0.01
OTFCC commit 617837b was discovered to contain a segmentation violation via /release-x64/otfccdump+0x6badae.