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

> Remote attackers can change the administrator password on Seagate BlackArmor devices via a management web server vulnerability, leading to full device compromise.

- **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:** 25 May 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-836w-w693-xm8f

## What is CVE-2012-2568?

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

### Official description

d41d8cd98f00b204e9800998ecf8427e.php in the management web server on the Seagate BlackArmor device allows remote attackers to change the administrator password via unspecified vectors.

Weakness: CWE-264

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

It affects 1 product.


Products: Seagate Blackarmor Nas.

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

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

## Is CVE-2012-2568 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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