Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-34320: CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in BASIS International Ltd. BASIS BBj

0
Critical
VulnerabilityCVE-2025-34320cvecve-2025-34320cwe-22
Published: Thu Nov 20 2025 (11/20/2025, 15:31:38 UTC)
Source: CVE Database V5
Vendor/Project: BASIS International Ltd.
Product: BASIS BBj

Description

BASIS BBj versions prior to 25.00 contain a Jetty-served web endpoint that fails to properly validate or canonicalize input path segments. This allows unauthenticated directory traversal sequences to cause the server to read arbitrary system files accessible to the account running the service. Retrieved configuration artifacts may contain account credentials used for BBj Enterprise Manager; possession of these credentials enables administrative access and use of legitimate management functionality that can result in execution of system commands under the service account. Depending on the operating system and the privileges of the BBj service account, this issue may also allow access to other sensitive files on the host, including operating system or application data, potentially exposing additional confidential information.

AI-Powered Analysis

AILast updated: 11/20/2025, 15:57:53 UTC

Technical Analysis

CVE-2025-34320 is a critical security vulnerability classified under CWE-22 (Improper Limitation of a Pathname to a Restricted Directory, commonly known as path traversal) affecting BASIS International Ltd.'s BASIS BBj software versions prior to 25.00. The vulnerability arises from a Jetty-served web endpoint that fails to properly validate or canonicalize input path segments, allowing an unauthenticated attacker to craft directory traversal sequences (e.g., '../') to access arbitrary files on the server filesystem. Because the BBj service runs under an account with certain privileges, attackers can read sensitive configuration files that may contain credentials for the BBj Enterprise Manager. With these credentials, attackers can gain administrative access to the management interface and execute system commands with the service account's privileges. The impact varies depending on the operating system and the privileges of the BBj service account but can include exposure of confidential data, unauthorized command execution, and potential full compromise of the host system. The vulnerability requires no authentication or user interaction and can be exploited remotely over the network, making it highly dangerous. Although no known exploits are currently reported in the wild, the high CVSS score (9.3) and critical severity rating indicate a significant risk. The vulnerability was published on November 20, 2025, and affects all versions prior to 25.00, with no patch links currently available, emphasizing the need for urgent vendor response and mitigation.

Potential Impact

For European organizations using BASIS BBj, this vulnerability poses a severe risk to confidentiality, integrity, and availability of critical systems. Unauthorized access to configuration files can lead to credential theft, enabling attackers to escalate privileges and execute arbitrary commands, potentially resulting in full system compromise. This can disrupt business operations, lead to data breaches involving sensitive personal or corporate data, and cause regulatory compliance violations under GDPR. The ability to exploit the vulnerability without authentication or user interaction increases the likelihood of automated attacks and widespread exploitation. Organizations in sectors such as finance, healthcare, manufacturing, and government—where BASIS BBj may be used for enterprise management—are particularly vulnerable. The exposure of administrative credentials could also facilitate lateral movement within networks, amplifying the impact. Additionally, the potential disclosure of operating system or application data could reveal further sensitive information, compounding the damage. The lack of known exploits in the wild currently provides a window for proactive mitigation but also underscores the urgency to act before attackers develop and deploy exploit code.

Mitigation Recommendations

1. Immediately restrict network access to the Jetty-served web endpoint in BASIS BBj to trusted internal IP addresses or VPN users only, using firewall rules or network segmentation. 2. Monitor and analyze web server logs for suspicious path traversal patterns (e.g., '../') and unusual file access attempts. 3. Implement Web Application Firewall (WAF) rules to detect and block directory traversal payloads targeting the vulnerable endpoint. 4. Disable or remove any unnecessary web endpoints or services in BASIS BBj that are not required for business operations. 5. Regularly audit and rotate credentials stored in configuration files to limit the impact of potential credential exposure. 6. Follow BASIS International Ltd.'s advisories closely and apply security patches or updates as soon as they become available. 7. Employ host-based intrusion detection systems (HIDS) to alert on unauthorized file access or command execution attempts. 8. Conduct internal penetration testing to verify the effectiveness of mitigations and identify any residual risks. 9. Educate IT and security teams about this vulnerability and ensure incident response plans include steps for potential exploitation scenarios. 10. Consider isolating the BBj service account with minimal privileges necessary to limit the scope of compromise if exploited.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
VulnCheck
Date Reserved
2025-04-15T19:15:22.585Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 691f3714b661599aeb20f31a

Added to database: 11/20/2025, 3:43:16 PM

Last enriched: 11/20/2025, 3:57:53 PM

Last updated: 11/21/2025, 1:48:36 PM

Views: 15

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats