OAuth client Single Sign On for WordPress (…: Improper Authentication
CVE-2022-3119 is a high-severity improper authentication vulnerability in OAuth client Single Sign On for WordPress ( OAuth 2.0 SSO ), 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. The record lists version 3.0.4 as the first without the flaw, so updating OAuth client Single Sign On for WordPress ( OAuth 2.0 SSO ) to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.44% 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 OAuth client Single Sign On for WordPress ( OAuth 2.0 SSO ) to 3.0.4 or a later version.
- Update Oauth Client Single Sign On to 3.0.4 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 |
|---|---|---|---|
| OAuth client Single Sign On for WordPress ( OAuth 2.0 SSO ) | OAuth client Single Sign On for WordPress ( OAuth 2.0 SSO ) | 3.0.4 up to, but not including, 3.0.4 | 3.0.4 |
| Oauth Client Single Sign On Project | Oauth Client Single Sign On | before 3.0.4 | 3.0.4 |
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 | 7.5 | High | NVD |
| CVSS 3.1 | 7.5 | High | CISA (ADP) |
Official description
The OAuth client Single Sign On WordPress plugin before 3.0.4 does not have authorisation and CSRF when updating its settings, which could allow unauthenticated attackers to update them and change the OAuth endpoints to ones they controls, allowing them to then be authenticated as admin if they know the correct email address
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Authentication
When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.
How developers prevent this class of flaw
- Use an authentication framework or library such as the OWASP ESAPI Authentication feature.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: poc, automatable: no, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Technical write-ups (may include proof of concept)
- wpscan.com/vulnerability/55b83cee-a8a5-4f9d-a976-a3eed9a558e5Exploit, Third Party Advisory
Recent Improper Authentication vulnerabilities
- 8.8 High severity
- 8.8 High severity
- 8.1 High severity
- 9.8 Critical severity
- 9.8 Critical severity
- 9.8 Critical severity
Spotted an error? Tell us.