# CVE-2012-1799: Auth bypass in n/a

> Remote attackers can brute-force administrative passwords due to missing rate limiting on the web server, leading to unauthorized access.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Apr 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-jv75-q996-4qm5

## What is CVE-2012-1799?

CVE-2012-1799 is a critical authentication bypass vulnerability in n/a, published on 18 Apr 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The web server on the Siemens Scalance S Security Module firewall S602 V2, S612 V2, and S613 V2 with firmware before 2.3.0.3 does not limit the rate of authentication attempts, which makes it easier for remote attackers to obtain access via a brute-force attack on the administrative password.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2012-1799?

It affects 4 products.


Products: Siemens Scalance S602, Siemens Scalance S612, Siemens Scalance S613, Siemens Scalance S Firmware.

## How do I fix CVE-2012-1799?

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

## Is CVE-2012-1799 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-1800](https://insights.sbomify.com/CVE-2012-1800/): Memory corruption in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-1799 and fix it if it is affected.

What it is: CVE-2012-1799 is a critical authentication bypass vulnerability in n/a, published on 18 Apr 2012. 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-2012-1799 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-2012-1799/ (Markdown: https://insights.sbomify.com/CVE-2012-1799/index.md)
```

## Sources

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

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