# CVE-2006-3105: Other in n/a

> Remote attackers can perform HTTP response splitting via CRLF injection in Bitweaver parameters, potentially enabling cache poisoning or XSS.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Jun 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-r6x4-g6mq-2ww5

## What is CVE-2006-3105?

CVE-2006-3105 is a medium-severity vulnerability in n/a, published on 21 Jun 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

CRLF injection vulnerability in Bitweaver 1.3 allows remote attackers to conduct HTTP response splitting attacks by via CRLF sequences in multiple unspecified parameters that are injected into HTTP headers, as demonstrated by the BWSESSION parameter in index.php.

## Which versions are affected by CVE-2006-3105?

It affects 1 product.


Products: Bitweaver Bitweaver.

## How do I fix CVE-2006-3105?

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

## Is CVE-2006-3105 being exploited?

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

Public exploit code:

- Bitweaver 1.3 - 'tmpImagePath' Attachment mod_mime (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2009-1678](https://insights.sbomify.com/CVE-2009-1678/): Path traversal in n/a (high 7.5)
- [CVE-2007-6375](https://insights.sbomify.com/CVE-2007-6375/): SQL injection in n/a (high 7.5)
- [CVE-2006-6923](https://insights.sbomify.com/CVE-2006-6923/): SQL injection in n/a (high 7.5)
- [CVE-2005-4380](https://insights.sbomify.com/CVE-2005-4380/): SQL injection in n/a (high 7.5)
- [CVE-2007-6412](https://insights.sbomify.com/CVE-2007-6412/): Code injection in n/a (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-3105 and fix it if it is affected.

What it is: CVE-2006-3105 is a medium-severity vulnerability in n/a, published on 21 Jun 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-3105 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-2006-3105/ (Markdown: https://insights.sbomify.com/CVE-2006-3105/index.md)
```

## Sources

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

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