# CVE-2009-3035: Hardcoded credentials in n/a

> Local attackers can exploit a hardcoded key to decrypt SQL credentials, potentially leading to data theft and arbitrary code execution.

- **Severity:** Medium 4.3 (`AV:L/AC:L/Au:S/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Feb 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-2c59-mm9r-vwwg

## What is CVE-2009-3035?

CVE-2009-3035 is a medium-severity vulnerability in n/a, published on 2 Feb 2010. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The web console in Symantec Altiris Notification Server 6.0.x before 6.0 SP3 R12 uses a hardcoded key that can decrypt SQL Server credentials and certain discovery credentials, and stores this key on the Notification Server machine, which allows local users to obtain sensitive information and possibly execute arbitrary code by decrypting and using these credentials.

Weakness: CWE-255

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

It affects 1 product.


Products: Symantec Altiris Notification Server.

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

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

## Is CVE-2009-3035 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-2794](https://insights.sbomify.com/CVE-2008-2794/): Privilege escalation in n/a (medium 6.8)
- [CVE-2008-0716](https://insights.sbomify.com/CVE-2008-0716/): Privilege escalation in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2009-3035 is a medium-severity vulnerability in n/a, published on 2 Feb 2010. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2009-3035 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-3035/ (Markdown: https://insights.sbomify.com/CVE-2009-3035/index.md)
```

## Sources

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

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