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

> Remote attackers can trigger a stack-based buffer overflow in PHP's XML-RPC library via crafted date fields, potentially causing crashes or arbitrary code execution.

- **Severity:** High 7.5 (`AV:N/AC:L/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:** Not needed
- **Fix available:** Yes
- **Published:** 23 Nov 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-mfxw-8c28-qhqc, RHSA-2014:1825

## What is CVE-2014-8626?

CVE-2014-8626 is a high-severity memory corruption vulnerability in Php Php, published on 23 Nov 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Stack-based buffer overflow in the date_from_ISO8601 function in ext/xmlrpc/libxmlrpc/xmlrpc.c in PHP before 5.2.7 allows remote attackers to cause a denial of service (application crash) or possibly execute arbitrary code by including a timezone field in a date, leading to improper XML-RPC encoding.

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

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `php` | Red Hat:rhel_els:4::as | All versions | 0:4.3.9-3.38.el4 |
| `php-debuginfo` | Red Hat:rhel_els:4::as | All versions | 0:4.3.9-3.38.el4 |
| `php-devel` | Red Hat:rhel_els:4::as | All versions | 0:4.3.9-3.38.el4 |
| `php-domxml` | Red Hat:rhel_els:4::as | All versions | 0:4.3.9-3.38.el4 |
| `php-gd` | Red Hat:rhel_els:4::as | All versions | 0:4.3.9-3.38.el4 |
| `php-imap` | Red Hat:rhel_els:4::as | All versions | 0:4.3.9-3.38.el4 |
| `php-ldap` | Red Hat:rhel_els:4::as | All versions | 0:4.3.9-3.38.el4 |
| `php-mbstring` | Red Hat:rhel_els:4::as | All versions | 0:4.3.9-3.38.el4 |
| `php-mysql` | Red Hat:rhel_els:4::as | All versions | 0:4.3.9-3.38.el4 |
| `php-ncurses` | Red Hat:rhel_els:4::as | All versions | 0:4.3.9-3.38.el4 |
| `php-odbc` | Red Hat:rhel_els:4::as | All versions | 0:4.3.9-3.38.el4 |
| `php-pear` | Red Hat:rhel_els:4::as | All versions | 0:4.3.9-3.38.el4 |
| `php-pgsql` | Red Hat:rhel_els:4::as | All versions | 0:4.3.9-3.38.el4 |
| `php-snmp` | Red Hat:rhel_els:4::as | All versions | 0:4.3.9-3.38.el4 |
| `php-xmlrpc` | Red Hat:rhel_els:4::as | All versions | 0:4.3.9-3.38.el4 |
| `php` | Red Hat:rhel_els:4::es | All versions | 0:4.3.9-3.38.el4 |
| `php-debuginfo` | Red Hat:rhel_els:4::es | All versions | 0:4.3.9-3.38.el4 |
| `php-devel` | Red Hat:rhel_els:4::es | All versions | 0:4.3.9-3.38.el4 |
| `php-domxml` | Red Hat:rhel_els:4::es | All versions | 0:4.3.9-3.38.el4 |
| `php-gd` | Red Hat:rhel_els:4::es | All versions | 0:4.3.9-3.38.el4 |
| `php-imap` | Red Hat:rhel_els:4::es | All versions | 0:4.3.9-3.38.el4 |
| `php-ldap` | Red Hat:rhel_els:4::es | All versions | 0:4.3.9-3.38.el4 |
| `php-mbstring` | Red Hat:rhel_els:4::es | All versions | 0:4.3.9-3.38.el4 |
| `php-mysql` | Red Hat:rhel_els:4::es | All versions | 0:4.3.9-3.38.el4 |
| `php-ncurses` | Red Hat:rhel_els:4::es | All versions | 0:4.3.9-3.38.el4 |
| `php-odbc` | Red Hat:rhel_els:4::es | All versions | 0:4.3.9-3.38.el4 |
| `php-pear` | Red Hat:rhel_els:4::es | All versions | 0:4.3.9-3.38.el4 |
| `php-pgsql` | Red Hat:rhel_els:4::es | All versions | 0:4.3.9-3.38.el4 |
| `php-snmp` | Red Hat:rhel_els:4::es | All versions | 0:4.3.9-3.38.el4 |
| `php-xmlrpc` | Red Hat:rhel_els:4::es | All versions | 0:4.3.9-3.38.el4 |

Products: Php Php.

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

Upgrade to a fixed version.

## Is CVE-2014-8626 being exploited?

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

What it is: CVE-2014-8626 is a high-severity memory corruption vulnerability in Php Php, published on 23 Nov 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-8626 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-8626/ (Markdown: https://insights.sbomify.com/CVE-2014-8626/index.md)
```

## Sources

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

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