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

> Attackers can bypass authentication via replay attacks due to improper handling of invalid OTP types in the OATH Toolkit library.

- **Severity:** Medium 4.9 (`AV:N/AC:M/Au:S/C:P/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 Mar 2014
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2013-7322, GHSA-2xxx-v399-cp66, MGASA-2014-0101, openSUSE-SU-2024:11104-1

## What is CVE-2013-7322?

CVE-2013-7322 is a medium-severity authentication bypass vulnerability in n/a, published on 7 Mar 2014. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

usersfile.c in liboath in OATH Toolkit before 2.4.1 does not properly handle lines containing an invalid one-time-password (OTP) type and a user name in /etc/users.oath, which causes the wrong line to be updated when invalidating an OTP and allows context-dependent attackers to conduct replay attacks, as demonstrated by a commented out line when using libpam-oath.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `oath-toolkit` | openSUSE:Tumbleweed | All versions | 2.6.7-1.3 |

Products: Nongnu Oath Toolkit.

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

Upgrade to a fixed version.

## Is CVE-2013-7322 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2013-7322 is a medium-severity authentication bypass vulnerability in n/a, published on 7 Mar 2014. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-7322 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-2013-7322/ (Markdown: https://insights.sbomify.com/CVE-2013-7322/index.md)
```

## Sources

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

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