# CVE-2004-1833: Misconfiguration in n/a

> Local attackers can gain database administrative privileges due to default world-writable permissions on the admin.ib file.

- **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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 May 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-9vg5-q5qw-72m8

## What is CVE-2004-1833?

CVE-2004-1833 is a high-severity vulnerability in n/a, published on 10 May 2005. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The admin.ib file in Borland Interbase 7.1 for Linux has default world writable permissions, which allows local users to gain database administrative privileges.

## Which versions are affected by CVE-2004-1833?

It affects 1 product.


Products: Borland Software Interbase.

## How do I fix CVE-2004-1833?

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

## Is CVE-2004-1833 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2001-0008](https://insights.sbomify.com/CVE-2001-0008/): Auth bypass in n/a (critical 10.0)
- [CVE-2007-5243](https://insights.sbomify.com/CVE-2007-5243/): Memory corruption in n/a (critical 9.3)
- [CVE-2007-5244](https://insights.sbomify.com/CVE-2007-5244/): Memory corruption in n/a (critical 9.3)
- [CVE-2007-3566](https://insights.sbomify.com/CVE-2007-3566/): Memory corruption in n/a (high 7.5)
- [CVE-2002-1514](https://insights.sbomify.com/CVE-2002-1514/): Path traversal in n/a (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-1833 and fix it if it is affected.

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

## Sources

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

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