# CVE-2008-2291: Weak cryptography in n/a

> Remote attackers can guess encrypted domain credentials due to fixed or missing salts in Symantec Altiris Deployment Solution.

- **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:** No
- **Published:** 18 May 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-8f24-2cm6-vqqv

## What is CVE-2008-2291?

CVE-2008-2291 is a high-severity vulnerability in n/a, published on 18 May 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

axengine.exe in Symantec Altiris Deployment Solution 6.8.x and 6.9.x before 6.9.176 generates credentials with a fixed salt or without any salt, which makes it easier for remote attackers to guess encrypted domain credentials.

Weakness: CWE-255

## Which versions are affected by CVE-2008-2291?

It affects 1 product.


Products: Symantec Altiris Deployment Solution.

## How do I fix CVE-2008-2291?

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

## Is CVE-2008-2291 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-3179](https://insights.sbomify.com/CVE-2009-3179/): Other in n/a (critical 10.0)
- [CVE-2009-3033](https://insights.sbomify.com/CVE-2009-3033/): Memory corruption in n/a (critical 9.3)
- [CVE-2009-3031](https://insights.sbomify.com/CVE-2009-3031/): Memory corruption in n/a (critical 9.3)
- [CVE-2009-3109](https://insights.sbomify.com/CVE-2009-3109/): Auth bypass in n/a (critical 9.3)
- [CVE-2009-3178](https://insights.sbomify.com/CVE-2009-3178/): Denial of service in n/a (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-2291 and fix it if it is affected.

What it is: CVE-2008-2291 is a high-severity vulnerability in n/a, published on 18 May 2008. 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-2008-2291 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-2008-2291/ (Markdown: https://insights.sbomify.com/CVE-2008-2291/index.md)
```

## Sources

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

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