# CVE-2014-3670: Memory corruption in n/a

> Remote attackers can cause denial of service or execute arbitrary code via crafted JPEG images processed by the PHP EXIF extension.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 29 Oct 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-r6jr-5phj-2qqh, UBUNTU-CVE-2014-3670

## What is CVE-2014-3670?

CVE-2014-3670 is a medium-severity memory corruption vulnerability in Php Php, published on 29 Oct 2014. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The exif_ifd_make_value function in exif.c in the EXIF extension in PHP before 5.4.34, 5.5.x before 5.5.18, and 5.6.x before 5.6.2 operates on floating-point arrays incorrectly, which allows remote attackers to cause a denial of service (heap memory corruption and application crash) or possibly execute arbitrary code via a crafted JPEG image with TIFF thumbnail data that is improperly handled by the exif_thumbnail function.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Php Php.

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

Upgrade to a fixed version.

## Is CVE-2014-3670 being exploited?

There is no known exploitation of CVE-2014-3670 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-3670 and fix it if it is affected.

What it is: CVE-2014-3670 is a medium-severity memory corruption vulnerability in Php Php, published on 29 Oct 2014. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2014-3670 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-3670/ (Markdown: https://insights.sbomify.com/CVE-2014-3670/index.md)
```

## Sources

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

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