# CVE-2012-2062: Open redirect in n/a

> Remote attackers can redirect users to arbitrary sites for phishing via the Drupal Redirecting click bouncer module.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:N/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 17 Sep 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-qm25-w56j-5qh8

## What is CVE-2012-2062?

CVE-2012-2062 is a medium-severity vulnerability in n/a, published on 17 Sep 2012. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Open redirect vulnerability in the Redirecting click bouncer module for Drupal allows remote attackers to redirect users to arbitrary web sites and conduct phishing attacks via unspecified vectors.

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

It affects 1 product.


Products: Sami Kiminki Redirecting Click Bouncer.

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

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

## Is CVE-2012-2062 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2012-2062 is a medium-severity vulnerability in n/a, published on 17 Sep 2012. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2012-2062 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-2062/ (Markdown: https://insights.sbomify.com/CVE-2012-2062/index.md)
```

## Sources

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

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