# CVE-2014-2020: ext/gd/gd.c in PHP 5.5.x before 5.5.9 does not check data types, which might allow remote attackers to obtain sensitive information by using


- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 18 Feb 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-vpwx-8jjr-fghp

## What is CVE-2014-2020?

CVE-2014-2020 is a medium-severity vulnerability in Php Php, published on 18 Feb 2014. 

### Official description

ext/gd/gd.c in PHP 5.5.x before 5.5.9 does not check data types, which might allow remote attackers to obtain sensitive information by using a (1) string or (2) array data type in place of a numeric data type, as demonstrated by an imagecrop function call with a string for the x dimension value, a different vulnerability than CVE-2013-7226.

Weakness: CWE-189

## Which versions are affected by CVE-2014-2020?

It affects 1 product.


Products: Php Php.

## How do I fix CVE-2014-2020?

No fix has been published for CVE-2014-2020 yet. Limit exposure of the affected software until one is available.

## Is CVE-2014-2020 being exploited?

There is no known exploitation of CVE-2014-2020 in the wild and no public exploit code.

## Other vulnerabilities in Php Php

- [CVE-2012-2688](https://insights.sbomify.com/CVE-2012-2688/): Integer overflow in n/a (critical 10.0)
- [CVE-2012-2376](https://insights.sbomify.com/CVE-2012-2376/): Memory corruption in n/a (critical 10.0)
- [CVE-2011-3268](https://insights.sbomify.com/CVE-2011-3268/): Memory corruption in n/a (critical 10.0)
- [CVE-2009-4143](https://insights.sbomify.com/CVE-2009-4143/): Other in n/a (critical 10.0)
- [CVE-2008-5557](https://insights.sbomify.com/CVE-2008-5557/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-2020 and fix it if it is affected.

What it is: CVE-2014-2020 is a medium-severity vulnerability in Php Php, published on 18 Feb 2014. 
Exploitation: There is no known exploitation of CVE-2014-2020 in the wild and no public exploit code.

Affected product: Php Php. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2014-2020/ (Markdown: https://insights.sbomify.com/CVE-2014-2020/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2014-2020
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2014-2020
- OSV: https://osv.dev/vulnerability/CVE-2014-2020

---
From sbomify Insights: https://insights.sbomify.com/CVE-2014-2020/
Summaries are generated and may contain mistakes; the official description above is the record.