Overview
The CVE-2025-33093 vulnerability affects IBM Sterling Partner Engagement Manager versions 6.1.0, 6.2.0, and 6.2.2. This vulnerability can potentially lead to severe system compromise or data leakage due to the exposure of JWT secrets in public Helm Charts. These secrets are not stored as Kubernetes secrets, making it a significant cybersecurity issue.
Vulnerability Summary
CVE ID: CVE-2025-33093
Severity: High (CVSS: 7.5)
Attack Vector: Network
Privileges Required: Low
User Interaction: None
Impact: Potential system compromise or data leakage
Affected Products
A new way to communicate
Ameeba Chat is built on encrypted identity, not personal profiles.
Message, call, share files, and coordinate with identities kept separate.
- • Encrypted identity
- • Ameeba Chat authenticates access
- • Aliases and categories
- • End-to-end encrypted chat, calls, and files
- • Secure notes for sensitive information
Private communication, rethought.
Product | Affected Versions
IBM Sterling Partner Engagement Manager | 6.1.0
IBM Sterling Partner Engagement Manager | 6.2.0
IBM Sterling Partner Engagement Manager | 6.2.2
How the Exploit Works
An attacker can exploit this vulnerability by accessing the exposed JWT secrets in the public Helm Charts. This access potentially allows an attacker to impersonate legitimate services within the Kubernetes environment, thereby gaining unauthorized access to sensitive data or systems.
Conceptual Example Code
Here is a conceptual example of how the vulnerability might be exploited. This example assumes the attacker is able to access the Helm Chart:
# Access the Helm Chart
kubectl get helmchart sterling -o jsonpath='{.data.JWT_SECRET}'
# The output will be the JWT secret
eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...Please note that this is a simplified example and actual exploitation might require additional steps depending on the security controls in place.
Mitigation Guidance
For mitigation, it is recommended to apply the vendor patch once it becomes available. In the interim, using WAF or IDS can serve as a temporary mitigation. Always ensure that secrets are properly managed and stored securely, not in public or accessible locations.