# CVE-2009-0809: Information disclosure in n/a

> Authenticated users can read private profile cards of document objects via crafted links, exposing sensitive metadata in ENOVIA SmarTeam.

- **Severity:** Low 3.5 (`AV:N/AC:M/Au:S/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 4 Mar 2009
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-v6m9-gggv-wxxh

## What is CVE-2009-0809?

CVE-2009-0809 is a low-severity vulnerability in n/a, published on 4 Mar 2009. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

The Web Editor in Dassault Systemes ENOVIA SmarTeam V5 before Release 18 Service Pack 8, and possibly CATIA and other products, allows remote authenticated users to read the profile card of an object in the document class via a link that is sent from the owner of the document object.

Weakness: CWE-264

## Which versions are affected by CVE-2009-0809?

It affects 2 products.


Products: 3ds Enovia Smarteam, Ibm Catia.

## How do I fix CVE-2009-0809?

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

## Is CVE-2009-0809 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-0809 and fix it if it is affected.

What it is: CVE-2009-0809 is a low-severity vulnerability in n/a, published on 4 Mar 2009. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2009-0809 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-2009-0809/ (Markdown: https://insights.sbomify.com/CVE-2009-0809/index.md)
```

## Sources

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

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