CVE-2022-22931: Path Traversal in Apache James Server

Summary

08/02/2022
Yes i
Moderate
Not published

CVE-2022-22931: Path Traversal in Apache James Server. Affects org.apache.james:james-server versions < 3.6.2. Fixed in 3.6.2. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Apache James Server is an open-source email server that provides a platform for sending, receiving, and storing email messages. It offers various features such as maildir mailbox store and Sieve file repository. These implementations allow users to manage their email data effectively. However, a path traversal vulnerability has been identified in Apache James Server prior to version 3.6.2.

Vulnerability Detail

The path traversal vulnerability in Apache James Server arises due to a flaw in the fix for CVE-2021-40525. The fix fails to prepend delimiters during valid directory validations. This oversight enables an authenticated user to access other users' data stores, with the limitation that the user names must be prefixed by the value of the username being used. This vulnerability poses a moderate risk as it allows unauthorized access to sensitive data and compromises the confidentiality of user information.

How To Fix

Latest published version: 3.9.1 as of 22 Oct 2026

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

3.6.2

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no known workaround for this vulnerability. It is essential to apply the official fix by upgrading to Apache James Server version 3.6.2 or later.

Conclusion

The path traversal vulnerability in Apache James Server prior to version 3.6.2 allows authenticated users to access other users' data stores. It is crucial to upgrade to the fixed version to mitigate the risk of unauthorized data access. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for org.apache.james:james-server →

Share this vulnerability

FAQ

Apache James Server is an open-source email server that provides email management capabilities.

This vulnerability allows an authenticated user to access other users' data stores, compromising the confidentiality of sensitive information.

Versions prior to 3.6.2 are affected by this vulnerability.

No, there is no known workaround. It is necessary to upgrade to the fixed version.

To fix this vulnerability, upgrade to Apache James Server version 3.6.2 or later.

Related vulnerabilities

Recent vulnerabilities recorded for org.apache.james:james-server.

How To Fix

Latest published version: 3.9.1 as of 22 Oct 2026

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

3.6.2

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback