# CVE-2007-1169: Information disclosure in n/a

> Remote attackers can sniff unencrypted HTTP logon requests to steal credentials for Trend Micro ServerProtect for Linux.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/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:** 28 Feb 2007
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-2245-5h8g-6r6m

## What is CVE-2007-1169?

CVE-2007-1169 is a medium-severity vulnerability in n/a, published on 28 Feb 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The web interface in Trend Micro ServerProtect for Linux (SPLX) 1.25, 1.3, and 2.5 before 20070216 accepts logon requests through unencrypted HTTP, which might allow remote attackers to obtain credentials by sniffing the network.

## Which versions are affected by CVE-2007-1169?

It affects 1 product.


Products: Trend Micro Serverprotect.

## How do I fix CVE-2007-1169?

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

## Is CVE-2007-1169 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-5268](https://insights.sbomify.com/CVE-2006-5268/): Auth bypass in n/a (critical 10.0)
- [CVE-2006-5269](https://insights.sbomify.com/CVE-2006-5269/): Memory corruption in n/a (critical 10.0)
- [CVE-2007-0072](https://insights.sbomify.com/CVE-2007-0072/): Memory corruption in n/a (critical 10.0)
- [CVE-2007-0073](https://insights.sbomify.com/CVE-2007-0073/): Memory corruption in n/a (critical 10.0)
- [CVE-2007-0074](https://insights.sbomify.com/CVE-2007-0074/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-1169 and fix it if it is affected.

What it is: CVE-2007-1169 is a medium-severity vulnerability in n/a, published on 28 Feb 2007. 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-2007-1169 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-2007-1169/ (Markdown: https://insights.sbomify.com/CVE-2007-1169/index.md)
```

## Sources

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

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