# CVE-2002-1252: The Application Messaging Gateway for PeopleTools 8.1x before 8.19, as used in various PeopleSoft products, allows remote attackers to read


- **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:** 1 Sep 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-g8hf-fqm5-7rhh

## What is CVE-2002-1252?

CVE-2002-1252 is a medium-severity vulnerability in n/a, published on 1 Sep 2004. 

### Official description

The Application Messaging Gateway for PeopleTools 8.1x before 8.19, as used in various PeopleSoft products, allows remote attackers to read arbitrary files via certain XML External Entities (XXE) fields in an HTTP POST request that is processed by the SimpleFileHandler handler.

## Which versions are affected by CVE-2002-1252?

It affects 1 product.


Products: Peoplesoft Peopletools.

## How do I fix CVE-2002-1252?

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

## Is CVE-2002-1252 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2003-0950](https://insights.sbomify.com/CVE-2003-0950/): File upload in n/a (high 7.5)
- [CVE-2003-0626](https://insights.sbomify.com/CVE-2003-0626/): Path traversal in n/a (medium 5.0)
- [CVE-2003-0627](https://insights.sbomify.com/CVE-2003-0627/): Denial of service in n/a (medium 5.0)
- [CVE-2003-0104](https://insights.sbomify.com/CVE-2003-0104/): Path traversal in n/a (medium 5.0)
- [CVE-2003-0628](https://insights.sbomify.com/CVE-2003-0628/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2002-1252 and fix it if it is affected.

What it is: CVE-2002-1252 is a medium-severity vulnerability in n/a, published on 1 Sep 2004. 
Exploitation: There is no known exploitation of CVE-2002-1252 in the wild and no public exploit code.

Affected product: n/a. 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-2002-1252/ (Markdown: https://insights.sbomify.com/CVE-2002-1252/index.md)
```

## Sources

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

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