A segmentation fault during PCF file parsing in pcf2bdf versions >=1.05 allows an attacker to trigger a program crash via a specially crafted PCF font file. This crash affects the availability of the software and dependent downstream components.
The product receives input that is expected to specify a quantity (such as size or length), but it does not validate or incorrectly validates that the quantity has the required properties.
Name | Vendor | Start Version | End Version |
---|---|---|---|
Pcf2bdf | Pcf2bdf_project | 1.04 (including) | 1.04 (including) |
Pcf2bdf | Pcf2bdf_project | 1.05 (including) | 1.05 (including) |
Pcf2bdf | Ubuntu | bionic | * |
Pcf2bdf | Ubuntu | impish | * |
Pcf2bdf | Ubuntu | kinetic | * |
Pcf2bdf | Ubuntu | lunar | * |
Pcf2bdf | Ubuntu | mantic | * |
Pcf2bdf | Ubuntu | trusty | * |
Pcf2bdf | Ubuntu | xenial | * |
Specified quantities include size, length, frequency, price, rate, number of operations, time, and others. Code may rely on specified quantities to allocate resources, perform calculations, control iteration, etc. When the quantity is not properly validated, then attackers can specify malicious quantities to cause excessive resource allocation, trigger unexpected failures, enable buffer overflows, etc.