# CVE-2006-1257: Auth bypass in n/a

> Remote attackers can bypass authentication in Microsoft Commerce Server by exploiting sample files, allowing unauthorized access to the main site.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Mar 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-j7hg-4m8w-qjr3

## What is CVE-2006-1257?

CVE-2006-1257 is a high-severity authentication bypass vulnerability in n/a, published on 19 Mar 2006. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The sample files in the authfiles directory in Microsoft Commerce Server 2002 before SP2 allow remote attackers to bypass authentication by logging in to authfiles/login.asp with a valid username and any password, then going to the main site twice.

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

It affects 1 product.


Products: Microsoft Commerce Server.

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

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

## Is CVE-2006-1257 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-1856](https://insights.sbomify.com/CVE-2012-1856/): Microsoft Office MSCOMCTL.OCX Remote Code Execution (high 8.8, exploited in the wild)
- [CVE-2002-0622](https://insights.sbomify.com/CVE-2002-0622/): Command injection in n/a (high 7.5)
- [CVE-2002-0623](https://insights.sbomify.com/CVE-2002-0623/): Memory corruption in n/a (high 7.5)
- [CVE-2002-0050](https://insights.sbomify.com/CVE-2002-0050/): Memory corruption in n/a (high 7.5)
- [CVE-2002-0621](https://insights.sbomify.com/CVE-2002-0621/): Memory corruption in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-1257 is a high-severity authentication bypass vulnerability in n/a, published on 19 Mar 2006. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-1257 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-2006-1257/ (Markdown: https://insights.sbomify.com/CVE-2006-1257/index.md)
```

## Sources

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

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