GHSA-86jq-pwgx-6vrq CVE-2023-1463
Improper Authorization in nilsteampassnet/teampass
Medium
Packagist
- Severity
- 5.4 / 10
- Medium · CVSS 3.1
- Exploit chance (EPSS)
- 0.52%
- Chance of exploitation in the next 30 days. Higher than 44.38% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Fix
3.0.0.23- Upgrade nilsteampassnet/teampass to this version or later
Description
Improper Authorization in GitHub repository nilsteampassnet/teampass prior to 3.0.0.23.
Affected versions
Packagist
| Package | Vulnerable | Fixed in |
|---|---|---|
| nilsteampassnet/teampass | < 3.0.0.23 |
3.0.0.23 |
How to fix
Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.
nilsteampassnet/teampass Packagist → 3.0.0.23
- composer
composer require nilsteampassnet/teampass:^3.0.0.23
Severity breakdown
CVSS 3.1 5.4
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- Low
Weakness
CWE-285: Improper Authorization
The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action.
How to prevent it
- Architecture and Design: Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries. Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
- Architecture and Design: Ensure that you perform access control checks related to your business logic. These checks may be different than the access control checks that you apply to more generic resources such as files, connections, processes, memory, and database records. For example, a database may restrict access for medical records to a specific database user, but each record might only be intended to be accessible to the patient and the patient's doctor.
- Architecture and Design: Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using authorization frameworks such as the JAAS Authorization Framework [REF-233] and the OWASP ESAPI Access Control feature [REF-45].
- Architecture and Design: For web applications, make sure that the access control mechanism is enforced correctly at the server side on every page. Users should not be able to access any unauthorized functionality or information by simply requesting direct access to that page. One way to do this is to ensure that all pages containing sensitive information are not cached, and that all such pages restrict access to requests that are accompanied by an active and authenticated session token associated with a user who has the required permissions to access that page.
- System Configuration, Installation: Use the access control capabilities of your operating system and server environment and define your access control lists accordingly. Use a "default deny" policy when defining these ACLs.
CWE-639: Authorization Bypass Through User-Controlled Key
The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.
How to prevent it
- Architecture and Design: For each and every data access, ensure that the user has sufficient privilege to access the record that is being requested.
- Architecture and Design, Implementation: Make sure that the key that is used in the lookup of a specific user's record is not controllable externally by the user or that any tampering can be detected.
- Architecture and Design: Use encryption in order to make it more difficult to guess other legitimate values of the key or associate a digital signature with the key so that the server can verify that there has been no tampering.
References
Advisories
Packages
Other links
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-9wmc-988h-2mv2 TeamPass privileges issue | High | Also affects nilsteampassnet/teampass |
| GHSA-7rm3-4w6j-8xx4 TeamPass mail_me operation authorization issue | Medium | Also affects nilsteampassnet/teampass |
| GHSA-2697-96mv-3gfm TeamPass does not properly check whether a folder is in a user's allowed folders list | Medium | Also affects nilsteampassnet/teampass |
| GHSA-524r-w8fx-hqg3 TeamPass Cross-site Scripting vulnerability | Medium | Also affects nilsteampassnet/teampass |
| GHSA-2rhg-hqq9-8xjh TeamPass information exposure vulnerability | High | Also affects nilsteampassnet/teampass |
| GHSA-2cv5-qvq3-6276 TeamPass vulnerable to Improper Encoding or Escaping of Output | Medium | Also affects nilsteampassnet/teampass |
| GHSA-97hm-2mfr-2p97 TeamPass Code Injection vulnerability | High | Also affects nilsteampassnet/teampass |
| GHSA-pwrw-g29q-3mp8 TeamPass Cross-site Scripting vulnerability | Medium | Also affects nilsteampassnet/teampass |
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