# CVE-2005-3325: SQL injection in n/a

> Remote attackers can execute arbitrary SQL commands in ACID and BASE intrusion detection consoles via the sig parameter.

- **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 needed
- **Fix available:** Yes
- **Published:** 27 Oct 2005
- **Updated:** 7 Aug 2024
- **Also known as:** DSA-893-1, GHSA-3qqc-m294-6m8c

## What is CVE-2005-3325?

CVE-2005-3325 is a high-severity SQL injection vulnerability in n/a, published on 27 Oct 2005. It can be exploited over the network, with no action from the victim.

### Official description

Multiple SQL injection vulnerabilities in (1) acid_qry_main.php in Analysis Console for Intrusion Databases (ACID) 0.9.6b20 and (2) base_qry_main.php in Basic Analysis and Security Engine (BASE) 1.2, and unspecified other console scripts in these products, allow remote attackers to execute arbitrary SQL commands via the sig[1] parameter and possibly other parameters.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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

It affects 2 products.


Products: Acid Analysis Console for Intrusion Databases, Secureideas Basic Analysis and Security Engine.

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

Apply the vendor's patch.

## Is CVE-2005-3325 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-3325 exists.

Public exploit code:

- Basic Analysis and Security Engine (BASE) 1.2 - 'Base_qry_main.php' SQL Injection (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2005-4878](https://insights.sbomify.com/CVE-2005-4878/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-3325 is a high-severity SQL injection vulnerability in n/a, published on 27 Oct 2005. It can be exploited over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-3325 exists.

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-3325/ (Markdown: https://insights.sbomify.com/CVE-2005-3325/index.md)
```

## Sources

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

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