# CVE-2005-0505: Other in n/a

> Remote attackers can exploit an unknown vulnerability in Information Resource Manager related to LDAP logins, potentially causing serious impact.

- **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 stated
- **Attackable:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 22 Feb 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-4fr4-555r-hrvp

## What is CVE-2005-0505?

CVE-2005-0505 is a high-severity vulnerability in n/a, published on 22 Feb 2005. It can be exploited over the network.

### Official description

Unknown vulnerability in Information Resource Manager (IRM) before 1.5.2.1 allows remote attackers to have "potentially serious" impact, related to LDAP logins.

## Which versions are affected by CVE-2005-0505?

It affects 1 product.


Products: Stackworks Enterprises Information Resource Manager.

## How do I fix CVE-2005-0505?

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

## Is CVE-2005-0505 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-0505 and fix it if it is affected.

What it is: CVE-2005-0505 is a high-severity vulnerability in n/a, published on 22 Feb 2005. It can be exploited over the network.
Exploitation: There is no known exploitation of CVE-2005-0505 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-2005-0505/ (Markdown: https://insights.sbomify.com/CVE-2005-0505/index.md)
```

## Sources

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

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