# CVE-2013-6492: Auth bypass in n/a

> Remote attackers can bypass authentication to read or modify LVS configuration in the Piranha Configuration Tool via HTTP POST requests.

- **Severity:** Medium 5.8 (`AV:A/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Feb 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-4hq3-p5rp-7qxv, RHSA-2014:0174, RHSA-2014:0175

## What is CVE-2013-6492?

CVE-2013-6492 is a medium-severity authentication bypass vulnerability in n/a, published on 14 Feb 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Piranha Configuration Tool in Piranha 0.8.6 does not properly restrict access to webpages, which allows remote attackers to bypass authentication and read or modify the LVS configuration via an HTTP POST request.

Weakness: CWE-264

## Which versions are affected by CVE-2013-6492?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `piranha` | Red Hat:enterprise_linux:6::server | All versions | 0:0.8.6-4.el6_5.2 |
| `piranha-debuginfo` | Red Hat:enterprise_linux:6::server | All versions | 0:0.8.6-4.el6_5.2 |
| `piranha` | Red Hat:rhel_cluster:5 | All versions | 0:0.8.4-26.el5_10.1 |
| `piranha-debuginfo` | Red Hat:rhel_cluster:5 | All versions | 0:0.8.4-26.el5_10.1 |

Products: Ryan Ohara Piranha.

## How do I fix CVE-2013-6492?

Apply the vendor's patch.

## Is CVE-2013-6492 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2013-6492 exists.

Public exploit code:

- RedHat Piranha - Remote Security Bypass (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-6492 and fix it if it is affected.

What it is: CVE-2013-6492 is a medium-severity authentication bypass vulnerability in n/a, published on 14 Feb 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2013-6492 exists.

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-2013-6492/ (Markdown: https://insights.sbomify.com/CVE-2013-6492/index.md)
```

## Sources

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

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