AuthPress: Reliance on Cookies without Validation and Integrity Checking
CVE-2024-9820 is a high-severity reliance on cookies without validation and integrity checking vulnerability in AuthPress from Dueclic, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected AuthPress versions: 3.0 and earlier. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.4% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update WP 2fa With Telegram to 3.1 or a later version.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Dueclic | AuthPress | 3.0 and earlier | Not stated |
| Dueclic | WP 2fa With Telegram | before 3.1 | 3.1 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- NoneNo data is disclosed.
- Integrity
- HighData or code can be modified at will.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 6.5 | Medium | CNA (wordfence.com) |
| CVSS 3.1 | 7.5 | High | NVD |
Official description
The WP 2FA with Telegram plugin for WordPress is vulnerable to Two-Factor Authentication Bypass in versions up to, and including, 3.0. This is due to the two-factor code being stored in a cookie, which makes it possible to bypass two-factor authentication.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Reliance on Cookies without Validation and Integrity Checking
The product relies on the existence or values of cookies when performing security-critical operations, but it does not properly ensure that the setting is valid for the associated user.
How developers prevent this class of flaw
- Avoid using cookie data for a security-related decision.
- Perform thorough input validation (i.e.: server side validation) on the cookie data if you're going to use it for a security related decision.
- Add integrity checks to detect tampering.
More Reliance on Cookies without Validation and Integrity Checking vulnerabilities (CWE-565)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Third-party and government advisories
Other references
Other vulnerabilities in AuthPress
- 8.8 High severity
Recent Reliance on Cookies without Validation and Integrity Checking vulnerabilities
- 8.8 High severity
- 9.8 Critical severity
- 8.8 High severity
- 7.5 High severity
- 9.8 Critical severity
- 8.8 High severity
Spotted an error? Tell us.