Simple Single Sign On: Cleartext Transmission of Sensitive Information
CVE-2022-2083 is a high-severity cleartext transmission of sensitive information vulnerability in Simple Single Sign On, 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 Simple Single Sign On versions: 4.1.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.8% chance of exploitation within 30 days, higher than 57% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of Simple Single Sign On you run against the affected versions below, and install the vendor's latest release.
- 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 |
|---|---|---|---|
| Simple Single Sign On | Simple Single Sign On | 4.1.0 and earlier | Not stated |
| Simple Sign On Project | Simple Sign On | 4.1.0 and earlier | Not stated |
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
- HighAll data handled by the component can be read.
- Integrity
- NoneNothing can be modified.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N. Scored by NVD.
Official description
The Simple Single Sign On WordPress plugin through 4.1.0 leaks its OAuth client_secret, which could be used by attackers to gain unauthorized access to the site.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Cleartext Transmission of Sensitive Information
The product transmits sensitive or security-critical data in cleartext in a communication channel that can be sniffed by unauthorized actors.
How developers prevent this class of flaw
- Before transmitting, encrypt the data using reliable, confidentiality-protecting cryptographic protocols.
- When using web applications with SSL, use SSL for the entire session from login to logout, not just for the initial login page.
- When designing hardware platforms, ensure that approved encryption algorithms (such as those recommended by NIST) protect paths from security critical data to trusted user applications.
More Cleartext Transmission of Sensitive Information vulnerabilities (CWE-319)
Timeline
- CVE record published.
- Record last changed materially (score, affected products, status or references).
References
Technical write-ups (may include proof of concept)
- lana.codes/lanavdb/0bab7575-45fc-432d-945e-6100c35c574c/Exploit, Third Party Advisory
- wpscan.com/vulnerability/2bbfc855-6901-462f-8a93-120d7fb5d268Exploit, Third Party Advisory
Recent Cleartext Transmission of Sensitive Information vulnerabilities
- 7.5 High severity
- 7.5 High severity
- 9.1 Critical severity
- 8.2 High severity
- 7.5 High severity
- 7.5 High severity
Spotted an error? Tell us.