CVE-2019-11034
No exploitation reported by the sources we read.
- Published2019-04-18
- WeaknessCWE-125
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
When processing certain files, PHP EXIF extension in versions 7.1.x below 7.1.28, 7.2.x below 7.2.17 and 7.3.x below 7.3.4 can be caused to read past allocated buffer in exif_process_IFD_TAG function. This may lead to information disclosure or crash.
Timeline
dates in UTC- 2019-04-1817:29CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-10-23 21:37 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2019-11034?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2019-11034?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 12.4 | = 12.04 | no fix published | NVD |
| 14.4 | = 14.04 | no fix published | NVD |
| 16.4 | = 16.04 | no fix published | NVD |
| 18.4 | = 18.04 | no fix published | NVD |
| 18.10 | = 18.10 | no fix published | NVD |
| 19.4 | = 19.04 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 15.0 | = 15.0 | no fix published | NVD |
| 15.1 | = 15.1 | no fix published | NVD |
| 42.3 | = 42.3 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 7.3 | ≥ 7.3.0, < 7.3.4 | 7.3.4 | NVD |
| 7.2 | ≥ 7.2.9, < 7.2.17 | 7.2.17 | NVD |
| 7.1 | ≥ 7.1.0, < 7.1.28 | 7.1.28 | NVD |
3 more products in the sources.
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Distribution builds and vendor advisories
Packages from OSV.dev and products from the vendors' CSAF advisories.
version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.
Packages
- libzipAlmaLinux:8all versions · fixed in 1.5.1-2.module_el8.3.0+2010+7c76a223and 2 other packages
- libzipAlmaLinux:8all versions · fixed in 1.5.1-2.module_el8.4.0+2228+7c76a223and 2 other packages
- libzipAlmaLinux:8all versions · fixed in 1.5.1-2.module_el8.5.0+53+9945c2afand 2 other packages
- phpAlmaLinux:8all versions · fixed in 7.2.24-1.module_el8.3.0+2010+7c76a223and 26 other packages
- phpAlmaLinux:8all versions · fixed in 7.2.24-1.module_el8.4.0+2228+7c76a223and 26 other packages
- phpAlmaLinux:8all versions · fixed in 7.2.24-1.module_el8.5.0+53+9945c2afand 26 other packages
- php-pearAlmaLinux:8all versions · fixed in 1:1.10.5-9.module_el8.3.0+2010+7c76a223
- php-pecl-apcuAlmaLinux:8all versions · fixed in 5.1.12-2.module_el8.3.0+2010+7c76a223and 2 other packages
5 more package ranges on OSV.dev
Fix
Advisories and patches
- bugs.php.netPatch · Vendor Advisory
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
- Published
- 2019-04-18
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2019-11034?
Is CVE-2019-11034 actively exploited?
What is the CVSS score for CVE-2019-11034?
Running PHP? Hear about its next vulnerability
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.