What is the CVSS score of CVE-2013-7322?

CVE-2013-7322 has a CVSS 2.0 base score of 4.9 (Medium). CVSS vector: AV:N/AC:M/Au:S/C:P/I:P/A:N. EPSS exploitation probability: 0.4%.

Oath Toolkit CVE-2013-7322

MEDIUM

Improper Authentication (CWE-287)

2014-03-09 cve@mitre.org

Authentication Bypass Oath Toolkit

4.9

CVSS 2.0 · NVD

Severity by source

NVD PRIMARY

4.9 MEDIUM

AV:N/AC:M/Au:S/C:P/I:P/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

AV:N/AC:M/Au:S/C:P/I:P/A:N

Attack Vector

Network

Attack Complexity

Confidentiality

Integrity

Availability

None

Lifecycle Timeline

CVE Published

Mar 09, 2014 - 13:16 cve.org

MEDIUM 4.9

DescriptionCVE.org

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.

AnalysisAI

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. Rated medium severity (CVSS 4.9), this vulnerability is remotely exploitable. No vendor patch available.

Technical ContextAI

This vulnerability is classified as Improper Authentication (CWE-287), which allows attackers to bypass authentication mechanisms to gain unauthorized access. 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. Affected products include: Nongnu Oath Toolkit. Version information: before 2.4.1.

RemediationAI

No vendor patch is available at time of analysis. Monitor vendor advisories for updates. Implement multi-factor authentication, enforce strong password policies, use proven authentication frameworks.