CVE-2023-3553

7.5 HIGH

📋 TL;DR

This vulnerability in TeamPass (a password manager) allows unauthorized actors to access sensitive information stored in the application. It affects all TeamPass installations running versions prior to 3.0.10. The exposure occurs through improper access controls in the application's API or web interface.

💻 Affected Systems

Products:
  • TeamPass
Versions: All versions prior to 3.0.10
Operating Systems: All
Default Config Vulnerable: ⚠️ Yes
Notes: All TeamPass deployments are affected regardless of configuration.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete compromise of all stored passwords, credentials, and sensitive data managed by TeamPass, potentially leading to lateral movement and full organizational compromise.

🟠

Likely Case

Unauthorized access to subsets of stored credentials and sensitive information, potentially enabling account takeovers and data breaches.

🟢

If Mitigated

Limited exposure of non-critical information or no impact if proper network segmentation and access controls are implemented.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ✅ No
Complexity: LOW

The vulnerability requires some level of access to the application but does not require authentication to the vulnerable component.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 3.0.10

Vendor Advisory: https://github.com/nilsteampassnet/teampass/commit/e9f90b746fdde135da3c7fbe4fa22fe2bd32e66b

Restart Required: Yes

Instructions:

1. Backup your TeamPass database and configuration. 2. Download TeamPass 3.0.10 or later from the official repository. 3. Replace existing files with the new version. 4. Run any database migration scripts if provided. 5. Restart your web server.

🔧 Temporary Workarounds

Network Access Restriction

all

Restrict network access to TeamPass to only trusted IP addresses or internal networks.

# Example using iptables for Linux: iptables -A INPUT -p tcp --dport 80 -s TRUSTED_IP -j ACCEPT
# Example using Windows Firewall: New-NetFirewallRule -DisplayName "TeamPass Access" -Direction Inbound -Protocol TCP -LocalPort 80 -RemoteAddress TRUSTED_IP -Action Allow

🧯 If You Can't Patch

  • Implement strict network access controls to limit who can reach the TeamPass application.
  • Monitor application logs for unusual access patterns or unauthorized information retrieval attempts.

🔍 How to Verify

Check if Vulnerable:

Check your TeamPass version by viewing the application's about page or checking the version file in the installation directory.

Check Version:

grep -r "version" /path/to/teampass/includes/version.php 2>/dev/null || cat /path/to/teampass/includes/version.php

Verify Fix Applied:

Verify that the version is 3.0.10 or higher and test that sensitive information is no longer accessible through unauthorized means.

📡 Detection & Monitoring

Log Indicators:

  • Unusual access patterns to sensitive API endpoints
  • Requests for information without proper authentication tokens
  • Access from unexpected IP addresses to sensitive data endpoints

Network Indicators:

  • Unusual traffic patterns to TeamPass API endpoints
  • Requests for sensitive data without authentication headers

SIEM Query:

source="teampass.log" AND (uri_path="/api/*" OR uri_path="/sources/*") AND NOT (user_agent="legitimate_client" OR src_ip IN (trusted_ips))

🔗 References

📤 Share & Export