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

> Remote blocked users can bypass access restrictions and log in due to improper status checks in the Shibboleth authentication module for Drupal.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/A:N`)
- **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:** 31 Oct 2012
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-rxjf-96xg-p55g

## What is CVE-2012-4494?

CVE-2012-4494 is a medium-severity authentication bypass vulnerability in n/a, published on 31 Oct 2012. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Shibboleth authentication module 7.x-4.0 for Drupal does not properly check the active status of users, which allows remote blocked users to access bypass intended access restrictions and possibly have other impacts by logging in.

Weakness: CWE-264

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

It affects 1 product.


Products: Niif Shibb Auth.

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

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

## Is CVE-2012-4494 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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