LibreOffice documents can contain macros. The execution of those macros is controlled by the document security settings, typically execution of macros are blocked by default. A URL decoding flaw existed in how the urls to the macros within the document were processed and categorized, resulting in the possibility to construct a document where macro execution bypassed the security settings. The documents were correctly detected as containing macros, and prompted the user to their existence within the documents, but macros within the document were subsequently not controlled by the security settings allowing arbitrary macro execution This issue affects: LibreOffice 6.2 series versions prior to 6.2.7; LibreOffice 6.3 series versions prior to 6.3.1.
The product prepares a structured message for communication with another component, but encoding or escaping of the data is either missing or done incorrectly. As a result, the intended structure of the message is not preserved.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Libreoffice | Libreoffice | 6.2.0 (including) | 6.2.6 (excluding) |
| Libreoffice | Libreoffice | 6.3.0 (including) | 6.3.1 (excluding) |
| Libreoffice | Ubuntu | bionic | * |
| Libreoffice | Ubuntu | disco | * |
| Libreoffice | Ubuntu | trusty | * |
| Libreoffice | Ubuntu | upstream | * |
| Libreoffice | Ubuntu | xenial | * |
| Red Hat Enterprise Linux 7 | RedHat | libreoffice-1:5.3.6.1-24.el7 | * |
| Red Hat Enterprise Linux 8 | RedHat | libreoffice-1:6.0.6.1-20.el8 | * |
Improper encoding or escaping can allow attackers to change the commands that are sent to another component, inserting malicious commands instead. Most products follow a certain protocol that uses structured messages for communication between components, such as queries or commands. These structured messages can contain raw data interspersed with metadata or control information. For example, “GET /index.html HTTP/1.1” is a structured message containing a command (“GET”) with a single argument ("/index.html") and metadata about which protocol version is being used (“HTTP/1.1”). If an application uses attacker-supplied inputs to construct a structured message without properly encoding or escaping, then the attacker could insert special characters that will cause the data to be interpreted as control information or metadata. Consequently, the component that receives the output will perform the wrong operations, or otherwise interpret the data incorrectly.