org.apache.james:james-server vulnerabilities
Apache James Mail Server
- Registry
- Maven
- Latest
- 3.9.1
11 known advisories
The latest version, 3.9.1, is not affected by any of them. Projects on older versions may be.
mvn versions:use-dep-version -Dincludes=org.apache.james:james-server -DdepVersion=3.9.1 -DforceVersion=trueIs your project on an affected org.apache.james:james-server?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for org.apache.james:james-server
SMTP smuggling in Apache James
- Affected
- <3.7.5 · >=3.8.0 <3.8.1
- Fixed in
- 3.7.5, 3.8.1
Apache James server: Privilege escalation via JMX pre-authentication deserialization
- Affected
- <3.7.5 · >=3.8.0 <3.8.1
- Fixed in
- 3.7.5, 3.8.1
Apache James server allows an attacker with local access to access private user data in transit
- Affected
- <=3.7.2
- Fixed in
- No fix released
Apache James vulnerable to buffering attack
- Affected
- <3.6.3 · >=3.7.0 <3.7.1
- Fixed in
- 3.6.3, 3.7.1
Apache James Server OS Command Injection
- Affected
- <2.3.2.1
- Fixed in
- 2.3.2.1
Apache James Denial of Service
- Affected
- <2.2.0
- Fixed in
- 2.2.0
Path Traversal in Apache James Server
- Affected
- <3.6.2
- Fixed in
- 3.6.2
Path traversal in Apache James
- Affected
- <3.6.1
- Fixed in
- 3.6.1
Infinite Loop in Apache James
- Affected
- <3.6.1
- Fixed in
- 3.6.1
Command Injection in Apache James
- Affected
- <3.6.1
- Fixed in
- 3.6.1
Denial of Service in Apache James
- Affected
- >=3.1.0 <3.6.1
- Fixed in
- 3.6.1
Is your org.apache.james:james-server version vulnerable?
- org.apache.james:james-server 3.9No known advisories in 3.9.1
- org.apache.james:james-server 3.8No known advisories in 3.8.2
- org.apache.james:james-server 3.7No known advisories in 3.7.6
- org.apache.james:james-server 3.64 advisories in 3.6.2
- org.apache.james:james-server 3.59 advisories in 3.5.0
- org.apache.james:james-server 3.49 advisories in 3.4.0
Which of your client projects still run an old org.apache.james:james-server?
NPMscan reads the pom.xml, build.gradle and gradle.lockfile in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other Maven packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the Maven registry.