dbcve.org
JamesApplication · Apache

CVE-2022-45787

MEDIUM · 5.5 CVSS v3.1 Published 2023-01-06
Fix available
A fix is available. Upgrade to 0.8.9 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Unproper laxist permissions on the temporary files used by MIME4J TempFileStorageProvider may lead to information disclosure to other local users. This issue affects Apache James MIME4J version 0.8.8 and prior versions. We recommend users to upgrade to MIME4j version 0.8.9 or later.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Apache James MIME4J versions 0.8.8 and prior create temporary files through TempFileStorageProvider with overly permissive file permissions. These temp files, which may contain sensitive MIME message content, are readable by other local users on the same system, leading to information disclosure.

MitigationUpgrade MIME4J to version 0.8.9 or later, which implements proper restricted permissions on temporary files.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
JamesApplication
Affected:< 0.8.9

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify mime4j version in use
    Check the mime4j library version by inspecting your dependency management (Maven pom.xml, Gradle build file, or JAR manifest). Look for the version of org.apache.james:apache-mime4j-core or similar mime4j artifacts.
    Affected if The version is 0.8.8 or prior.
  2. Confirm TempFileStorageProvider is active
    Check the James configuration (typically in spring.xml or conf.xml) for the TempFileStorageProvider bean. If using defaults, file-based temp storage is likely active.
    Affected if TempFileStorageProvider is enabled (this is the default behavior in affected versions).
  3. Examine temp file permissions
    Locate the temporary directory used by James (check config for 'tempDirectory' setting, commonly /var/tmp or /tmp). Create a test message, then inspect the permissions of any newly created temp files using 'ls -la' or 'getfacl'.
    Affected if Temp files are readable by other users (permissions show 'r--r--r--' or similar world-readable mode).
  4. Check umask setting
    Check the umask value applied to the Java process running James. Run 'ps aux | grep java' to find the process, then check /proc/<pid>/environ for UMASK or inspect startup scripts.
    Affected if The umask is 0022 or less restrictive, allowing world-readable permissions on created files.

You are affected if mime4j version is 0.8.8 or prior, TempFileStorageProvider is in use, and temp files created by the application are readable by other local users on the system.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 0.8.9 or later
Fixed in 0.8.9
Interim mitigation

Upgrade MIME4J to version 0.8.9 or later, which implements proper restricted permissions on temporary files.

Recommended fix High confidence

MIME4J version 0.8.9

  1. Identify all Maven/Gradle dependencies that include org.apache.james:apache-mime4j-core or org.apache.james:apache-mime4j-dom
  2. Update the version of org.apache.james:apache-mime4j-core (and related modules if used) to version 0.8.9 or later in your dependency management
  3. Run your build tool (mvn or gradle) to resolve the new dependencies
  4. Rebuild and redeploy your application to apply the upgrade
  5. Verify the application functions correctly with the upgraded MIME4J library

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in James Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-45787 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-45787 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data