December 30, 2019
GNU LibreDWG is prone to multiple security vulnerabilities. Attackers can exploit these issues to cause denial-of-service conditions. Due to the nature of these issues, code execution may be possible but this has not been confirmed. Versions prior to GNU LibreDWG 0.9.3 are vulnerable.
- GNU LibreDWG 0.7
- GNU LibreDWG 0.8
- GNU LibreDWG 0.9
- GNU LibreDWG 0.9.1
- GNU LibreDWG 0.9.2
Block external access at the network boundary, unless external parties require service.
If global access isn't needed, filter access to the affected computer at the network boundary. Restricting access to only trusted computers and networks might greatly reduce the likelihood of exploits.
Deploy network intrusion detection systems to monitor network traffic for malicious activity.
Deploy a NID between the network perimeter and the affected application. Flag on all requests that appear to be anomalous. Audit logs regularly for evidence of attacks.
Implement multiple redundant layers of security.
Since some of these issues may be leveraged to execute code, we recommend memory-protection schemes, such as nonexecutable stack/heap configurations and randomly mapped memory segments. This tactic may complicate exploits of memory-corruption vulnerabilities.
Updates are available. Please see the references or vendor advisory for more information.
- GNU - Comparing changes
- linhlhq - Crafted input will lead to Memory allocation failed in dwg_decode_HATCH_private
- binutils - GNU Homepage
- linhlhq - Heap-buffer-overflow in decode_R13_R2000 (src/decode.c:1315)
- linhlhq - Heap-use-after-free in resolve_objectref_vector (src/decode.c:1434)
- Linhlhq - Several bugs found by fuzzing #176
Linhlhq from Infiniti Team, VinCSS (a member of Vingroup).
© 1995- Symantec Corporation
Permission to redistribute this alert electronically is granted as long as it is not edited in any way unless authorized by Symantec Security Response. Reprinting the whole or part of this alert in any medium other than electronically requires permission from firstname.lastname@example.org.
The information in the advisory is believed to be accurate at the time of publishing based on currently available information. Use of the information constitutes acceptance for use in an AS IS condition. There are no warranties with regard to this information. Neither the author nor the publisher accepts any liability for any direct, indirect, or consequential loss or damage arising from use of, or reliance on, this information.
Symantec, Symantec products, Symantec Security Response, and email@example.com are registered trademarks of Symantec Corp. and/or affiliated companies in the United States and other countries. All other registered and unregistered trademarks represented in this document are the sole property of their respective companies/owners.