Service crash via oversized JPEG allocation

Resource exhaustion in metadata-extractor before 2.18.0 allows context-dependent attackers to crash applications using a crafted JPEG file. The getBytes paths in the byte readers allocate an attacker-sized array before safely rejecting a count beyond the remaining input, while one bounds check also uses overflow-prone integer addition. A consuming application must parse the malicious image; the resulting heap exhaustion can terminate or interrupt its service without disclosing or modifying data.