Skip to content

GHSA-g3jr-6vj4-3x82 CVE-2023-3095

TeamPass vulnerable to Improper Access Control

Medium Packagist
Severity
6.5 / 10
Medium · CVSS 3.1
Exploit chance (EPSS)
0.38%
Chance of exploitation in the next 30 days. Higher than 32.12% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-284 Improper Access Control
Fix
3.0.9
Upgrade nilsteampassnet/teampass to this version or later

Description

Improper Access Control in GitHub repository nilsteampassnet/teampass prior to 3.0.9.

Affected versions

Packagist

PackageVulnerableFixed in
nilsteampassnet/teampass
< 3.0.9
3.0.9

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.9

composer
composer require nilsteampassnet/teampass:^3.0.9

Severity breakdown

CVSS 3.1 6.5

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

Weakness

CWE-284: Improper Access Control

The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.

How to prevent it
  • Architecture and Design, Operation: Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
  • Architecture and Design: Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy 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
Is this in your code?

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