rpm package
suse/libredwg&distro=SUSE Package Hub 15 SP1
pkg:rpm/suse/libredwg&distro=SUSE%20Package%20Hub%2015%20SP1
Vulnerabilities (24)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2020-6615 | Med | 6.5 | < 0.10-bp151.2.6.1 | 0.10-bp151.2.6.1 | Jan 8, 2020 | GNU LibreDWG 0.9.3.2564 has an invalid pointer dereference in dwg_dynapi_entity_value in dynapi.c (dynapi.c is generated by gen-dynapi.pl). | |
| CVE-2020-6614 | Hig | 8.1 | < 0.10-bp151.2.6.1 | 0.10-bp151.2.6.1 | Jan 8, 2020 | GNU LibreDWG 0.9.3.2564 has a heap-based buffer over-read in bfr_read in decode.c. | |
| CVE-2020-6613 | Hig | 8.1 | < 0.10-bp151.2.6.1 | 0.10-bp151.2.6.1 | Jan 8, 2020 | GNU LibreDWG 0.9.3.2564 has a heap-based buffer over-read in bit_search_sentinel in bits.c. | |
| CVE-2020-6612 | Hig | 8.1 | < 0.10-bp151.2.6.1 | 0.10-bp151.2.6.1 | Jan 8, 2020 | GNU LibreDWG 0.9.3.2564 has a heap-based buffer over-read in copy_compressed_bytes in decode_r2007.c. | |
| CVE-2020-6611 | Med | 6.5 | < 0.10-bp151.2.6.1 | 0.10-bp151.2.6.1 | Jan 8, 2020 | GNU LibreDWG 0.9.3.2564 has a NULL pointer dereference in get_next_owned_entity in dwg.c. | |
| CVE-2020-6610 | Med | 6.5 | < 0.10-bp151.2.6.1 | 0.10-bp151.2.6.1 | Jan 8, 2020 | GNU LibreDWG 0.9.3.2564 has an attempted excessive memory allocation in read_sections_map in decode_r2007.c. | |
| CVE-2020-6609 | Hig | 8.8 | < 0.10-bp151.2.6.1 | 0.10-bp151.2.6.1 | Jan 8, 2020 | GNU LibreDWG 0.9.3.2564 has a heap-based buffer over-read in read_pages_map in decode_r2007.c. | |
| CVE-2019-20015 | Med | 6.5 | < 0.9.3-bp151.2.3.1 | 0.9.3-bp151.2.3.1 | Dec 27, 2019 | An issue was discovered in GNU LibreDWG 0.92. Crafted input will lead to an attempted excessive memory allocation in dwg_decode_LWPOLYLINE_private in dwg.spec. | |
| CVE-2019-20014 | Hig | 8.8 | < 0.9.3-bp151.2.3.1 | 0.9.3-bp151.2.3.1 | Dec 27, 2019 | An issue was discovered in GNU LibreDWG before 0.93. There is a double-free in dwg_free in free.c. | |
| CVE-2019-20013 | Med | 6.5 | < 0.9.3-bp151.2.3.1 | 0.9.3-bp151.2.3.1 | Dec 27, 2019 | An issue was discovered in GNU LibreDWG before 0.93. Crafted input will lead to an attempted excessive memory allocation in decode_3dsolid in dwg.spec. | |
| CVE-2019-20012 | Med | 6.5 | < 0.9.3-bp151.2.3.1 | 0.9.3-bp151.2.3.1 | Dec 27, 2019 | An issue was discovered in GNU LibreDWG 0.92. Crafted input will lead to an attempted excessive memory allocation in dwg_decode_HATCH_private in dwg.spec. | |
| CVE-2019-20011 | Hig | 8.8 | < 0.9.3-bp151.2.3.1 | 0.9.3-bp151.2.3.1 | Dec 27, 2019 | An issue was discovered in GNU LibreDWG 0.92. There is a heap-based buffer over-read in decode_R13_R2000 in decode.c. | |
| CVE-2019-20010 | Hig | 8.8 | < 0.9.3-bp151.2.3.1 | 0.9.3-bp151.2.3.1 | Dec 27, 2019 | An issue was discovered in GNU LibreDWG 0.92. There is a use-after-free in resolve_objectref_vector in decode.c. | |
| CVE-2019-20009 | Med | 6.5 | < 0.9.3-bp151.2.3.1 | 0.9.3-bp151.2.3.1 | Dec 27, 2019 | An issue was discovered in GNU LibreDWG before 0.93. Crafted input will lead to an attempted excessive memory allocation in dwg_decode_SPLINE_private in dwg.spec. | |
| CVE-2019-9779 | Hig | 7.5 | < 0.9.3-bp151.2.3.1 | 0.9.3-bp151.2.3.1 | Mar 14, 2019 | An issue was discovered in GNU LibreDWG 0.7 and 0.7.1645. There is a NULL pointer dereference in the function dwg_dxf_LTYPE at dwg.spec (earlier than CVE-2019-9776). | |
| CVE-2019-9778 | Hig | 7.5 | < 0.9.3-bp151.2.3.1 | 0.9.3-bp151.2.3.1 | Mar 14, 2019 | An issue was discovered in GNU LibreDWG 0.7 and 0.7.1645. There is a heap-based buffer over-read in the function dwg_dxf_LTYPE at dwg.spec. | |
| CVE-2019-9777 | Hig | 7.5 | < 0.9.3-bp151.2.3.1 | 0.9.3-bp151.2.3.1 | Mar 14, 2019 | An issue was discovered in GNU LibreDWG 0.7 and 0.7.1645. There is a heap-based buffer over-read in the function dxf_header_write at header_variables_dxf.spec. | |
| CVE-2019-9776 | Hig | 7.5 | < 0.9.3-bp151.2.3.1 | 0.9.3-bp151.2.3.1 | Mar 14, 2019 | An issue was discovered in GNU LibreDWG 0.7 and 0.7.1645. There is a NULL pointer dereference in the function dwg_dxf_LTYPE at dwg.spec (later than CVE-2019-9779). | |
| CVE-2019-9775 | Cri | 9.1 | < 0.9.3-bp151.2.3.1 | 0.9.3-bp151.2.3.1 | Mar 14, 2019 | An issue was discovered in GNU LibreDWG 0.7 and 0.7.1645. There is an out-of-bounds read in the function dwg_dxf_BLOCK_CONTROL at dwg.spec. | |
| CVE-2019-9774 | Cri | 9.1 | < 0.9.3-bp151.2.3.1 | 0.9.3-bp151.2.3.1 | Mar 14, 2019 | An issue was discovered in GNU LibreDWG 0.7 and 0.7.1645. There is an out-of-bounds read in the function bit_read_B at bits.c. |
- affected < 0.10-bp151.2.6.1fixed 0.10-bp151.2.6.1
GNU LibreDWG 0.9.3.2564 has an invalid pointer dereference in dwg_dynapi_entity_value in dynapi.c (dynapi.c is generated by gen-dynapi.pl).
- affected < 0.10-bp151.2.6.1fixed 0.10-bp151.2.6.1
GNU LibreDWG 0.9.3.2564 has a heap-based buffer over-read in bfr_read in decode.c.
- affected < 0.10-bp151.2.6.1fixed 0.10-bp151.2.6.1
GNU LibreDWG 0.9.3.2564 has a heap-based buffer over-read in bit_search_sentinel in bits.c.
- affected < 0.10-bp151.2.6.1fixed 0.10-bp151.2.6.1
GNU LibreDWG 0.9.3.2564 has a heap-based buffer over-read in copy_compressed_bytes in decode_r2007.c.
- affected < 0.10-bp151.2.6.1fixed 0.10-bp151.2.6.1
GNU LibreDWG 0.9.3.2564 has a NULL pointer dereference in get_next_owned_entity in dwg.c.
- affected < 0.10-bp151.2.6.1fixed 0.10-bp151.2.6.1
GNU LibreDWG 0.9.3.2564 has an attempted excessive memory allocation in read_sections_map in decode_r2007.c.
- affected < 0.10-bp151.2.6.1fixed 0.10-bp151.2.6.1
GNU LibreDWG 0.9.3.2564 has a heap-based buffer over-read in read_pages_map in decode_r2007.c.
- affected < 0.9.3-bp151.2.3.1fixed 0.9.3-bp151.2.3.1
An issue was discovered in GNU LibreDWG 0.92. Crafted input will lead to an attempted excessive memory allocation in dwg_decode_LWPOLYLINE_private in dwg.spec.
- affected < 0.9.3-bp151.2.3.1fixed 0.9.3-bp151.2.3.1
An issue was discovered in GNU LibreDWG before 0.93. There is a double-free in dwg_free in free.c.
- affected < 0.9.3-bp151.2.3.1fixed 0.9.3-bp151.2.3.1
An issue was discovered in GNU LibreDWG before 0.93. Crafted input will lead to an attempted excessive memory allocation in decode_3dsolid in dwg.spec.
- affected < 0.9.3-bp151.2.3.1fixed 0.9.3-bp151.2.3.1
An issue was discovered in GNU LibreDWG 0.92. Crafted input will lead to an attempted excessive memory allocation in dwg_decode_HATCH_private in dwg.spec.
- affected < 0.9.3-bp151.2.3.1fixed 0.9.3-bp151.2.3.1
An issue was discovered in GNU LibreDWG 0.92. There is a heap-based buffer over-read in decode_R13_R2000 in decode.c.
- affected < 0.9.3-bp151.2.3.1fixed 0.9.3-bp151.2.3.1
An issue was discovered in GNU LibreDWG 0.92. There is a use-after-free in resolve_objectref_vector in decode.c.
- affected < 0.9.3-bp151.2.3.1fixed 0.9.3-bp151.2.3.1
An issue was discovered in GNU LibreDWG before 0.93. Crafted input will lead to an attempted excessive memory allocation in dwg_decode_SPLINE_private in dwg.spec.
- affected < 0.9.3-bp151.2.3.1fixed 0.9.3-bp151.2.3.1
An issue was discovered in GNU LibreDWG 0.7 and 0.7.1645. There is a NULL pointer dereference in the function dwg_dxf_LTYPE at dwg.spec (earlier than CVE-2019-9776).
- affected < 0.9.3-bp151.2.3.1fixed 0.9.3-bp151.2.3.1
An issue was discovered in GNU LibreDWG 0.7 and 0.7.1645. There is a heap-based buffer over-read in the function dwg_dxf_LTYPE at dwg.spec.
- affected < 0.9.3-bp151.2.3.1fixed 0.9.3-bp151.2.3.1
An issue was discovered in GNU LibreDWG 0.7 and 0.7.1645. There is a heap-based buffer over-read in the function dxf_header_write at header_variables_dxf.spec.
- affected < 0.9.3-bp151.2.3.1fixed 0.9.3-bp151.2.3.1
An issue was discovered in GNU LibreDWG 0.7 and 0.7.1645. There is a NULL pointer dereference in the function dwg_dxf_LTYPE at dwg.spec (later than CVE-2019-9779).
- affected < 0.9.3-bp151.2.3.1fixed 0.9.3-bp151.2.3.1
An issue was discovered in GNU LibreDWG 0.7 and 0.7.1645. There is an out-of-bounds read in the function dwg_dxf_BLOCK_CONTROL at dwg.spec.
- affected < 0.9.3-bp151.2.3.1fixed 0.9.3-bp151.2.3.1
An issue was discovered in GNU LibreDWG 0.7 and 0.7.1645. There is an out-of-bounds read in the function bit_read_B at bits.c.
Page 1 of 2