GHSA-r657-3wqh-g2x9 CVE-2023-5318
Microweber uses hard coded credentials
High
Packagist
- Severity
- 5.8 / 10
- High · CVSS 3.0
- Exploit chance (EPSS)
- 0.65%
- Chance of exploitation in the next 30 days. Higher than 51.31% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-798 Use of Hard-coded Credentials
- Fix
- None yet
- No fixed version published
Description
Use of Hard-coded Credentials in GitHub repository microweber/microweber 1.3.4 and prior. A patch is available and anticipated to be part of version 2.0.
Affected versions
Packagist
| Package | Vulnerable | Fixed in |
|---|---|---|
| microweber/microweber | <= 1.3.4 |
No fix yet |
How to fix
No fixed version has been published yet. Until one is, remove or replace the package, or turn off or isolate the affected feature. This page updates when a fix ships.
Severity breakdown
CVSS 3.0 5.8
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
Weakness
CWE-798: Use of Hard-coded Credentials
The product contains hard-coded credentials, such as a password or cryptographic key.
How to prevent it
- Architecture and Design: For outbound authentication: store passwords, keys, and other credentials outside of the code in a strongly-protected, encrypted configuration file or database that is protected from access by all outsiders, including other local users on the same system. Properly protect the key (CWE-320). If you cannot use encryption to protect the file, then make sure that the permissions are as restrictive as possible [REF-7]. In Windows environments, the Encrypted File System (EFS) may provide some protection.
- Architecture and Design: For inbound authentication: Rather than hard-code a default username and password, key, or other authentication credentials for first time logins, utilize a "first login" mode that requires the user to enter a unique strong password or key.
- Architecture and Design: If the product must contain hard-coded credentials or they cannot be removed, perform access control checks and limit which entities can access the feature that requires the hard-coded credentials. For example, a feature might only be enabled through the system console instead of through a network connection.
- Architecture and Design: For inbound authentication using passwords: apply strong one-way hashes to passwords and store those hashes in a configuration file or database with appropriate access control. That way, theft of the file/database still requires the attacker to try to crack the password. When handling an incoming password during authentication, take the hash of the password and compare it to the saved hash. Use randomly assigned salts for each separate hash that is generated. This increases the amount of computation that an attacker needs to conduct a brute-force attack, possibly limiting the effectiveness of the rainbow table method.
- Architecture and Design: For front-end to back-end connections: Three solutions are possible, although none are complete. The first suggestion involves the use of generated passwords or keys that are changed automatically and must be entered at given time intervals by a system administrator. These passwords will be held in memory and only be valid for the time intervals. Next, the passwords or keys should be limited at the back end to only performing actions valid for the front end, as opposed to having full access. Finally, the messages sent should be tagged and checksummed with time sensitive values so as to prevent replay-style attacks.
References
Advisories
Packages
Other links
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-vv4x-qcpq-wgrg Microweber vulnerable to Path Traversal | High | Also affects microweber/microweber |
| GHSA-6w5w-jx4x-vjvw Microweber Cross-site Scripting vulnerability | Medium | Also affects microweber/microweber |
| GHSA-5jg5-xqfw-rv92 Microweber has a Cross-site Scripting vulnerability | Medium | Also affects microweber/microweber |
| GHSA-2x2j-3c2v-g3c2 Microweber XSS Vulnerability in the homepage Endpoint | High | Also affects microweber/microweber |
| GHSA-mvj3-hc7j-vp74 Microweber has Reflected XSS Vulnerability in the layout Parameter | Medium | Also affects microweber/microweber |
| GHSA-8357-fjvx-xrm8 Microweber has Reflected XSS Vulnerability in the id Parameter | Medium | Also affects microweber/microweber |
| GHSA-782f-gxj5-xvqc Microweber Has Stored XSS Vulnerability in User Profile Fields | High | Also affects microweber/microweber |
| GHSA-j64v-xh5w-8hqj Microweber CMS API has authenticated local file inclusion vulnerability | High | Also affects microweber/microweber |
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor