Valve SteamOS 1.0 Authentication Username/Password hard-coded credentials
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.0 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Valve SteamOS 1.0. It has been classified as critical. This impacts an unknown function of the component Authentication. This manipulation of the argument Username/Password with the input steam causes hard-coded credentials.
Furthermore, there is an exploit available.
You should change the configuration settings.
Details
A vulnerability was found in Valve SteamOS 1.0. It has been declared as critical. Affected by this vulnerability is an unknown code block of the component Authentication. The manipulation of the argument Username/Password with the input value steam leads to a hard-coded credentials vulnerability. The CWE definition for the vulnerability is CWE-798. The product contains hard-coded credentials, such as a password or cryptographic key, which it uses for its own inbound authentication, outbound communication to external components, or encryption of internal data. As an impact it is known to affect confidentiality, and integrity.
The weakness was shared 12/16/2013 by Tim Brown with Portcullis Computer Security Ltd. as Evaluating SteamOS’s security posture (a first look) as confirmed posting (Blog). It is possible to read the advisory at labs.portcullis.co.uk. The attack can be launched remotely. Technical details and also a public exploit are known. The attack technique deployed by this issue is T1110.001 according to MITRE ATT&CK.
After immediately, there has been an exploit disclosed. It is possible to download the exploit at labs.portcullis.co.uk. It is declared as proof-of-concept.
It is possible to mitigate the problem by applying the configuration setting Change Password. A possible mitigation has been published immediately after the disclosure of the vulnerability.
The vulnerability is also documented in the vulnerability database at OSVDB (101848†). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.4VulDB Meta Temp Score: 5.0
VulDB Base Score: 5.4
VulDB Temp Score: 5.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Hard-coded credentialsCWE: CWE-798 / CWE-259 / CWE-255
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: ConfigStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Exploit Delay Time: 🔍
Config: Change Password
Timeline
12/16/2013 🔍12/16/2013 🔍
12/16/2013 🔍
01/09/2014 🔍
03/24/2019 🔍
Sources
Advisory: Evaluating SteamOS’s security posture (a first look)Researcher: Tim Brown
Organization: Portcullis Computer Security Ltd.
Status: Confirmed
GCVE (VulDB): GCVE-100-11779
OSVDB: 101848
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 01/09/2014 13:41Updated: 03/24/2019 10:45
Changes: 01/09/2014 13:41 (50), 03/24/2019 10:45 (1)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.