Apache

James

15 Schwachstellen gefunden.

Hinweis: Diese Liste kann unvollständig sein. Daten werden ohne Gewähr im Ursprungsformat bereitgestellt.
  • EPSS 0.56%
  • Veröffentlicht 04.01.2022 09:15:07
  • Zuletzt bearbeitet 21.11.2024 06:23:35

In Apache James, while fuzzing with Jazzer the IMAP parsing stack, we discover that crafted APPEND and STATUS IMAP command could be used to trigger infinite loops resulting in expensive CPU computations and OutOfMemory exceptions. This can be used fo...

  • EPSS 3.83%
  • Veröffentlicht 04.01.2022 09:15:07
  • Zuletzt bearbeitet 21.11.2024 06:24:19

Apache James ManagedSieve implementation alongside with the file storage for sieve scripts is vulnerable to path traversal, allowing reading and writing any file. This vulnerability had been patched in Apache James 3.6.1 and higher. We recommend the ...

  • EPSS 7.84%
  • Veröffentlicht 17.04.2019 15:29:00
  • Zuletzt bearbeitet 21.11.2024 04:16:32

Apache PDFBox 2.0.14 does not properly initialize the XML parser, which allows context-dependent attackers to conduct XML External Entity (XXE) attacks via a crafted XFDF.

Exploit
  • EPSS 5.41%
  • Veröffentlicht 05.06.2006 17:02:00
  • Zuletzt bearbeitet 03.04.2025 01:03:51

The SMTP server in Apache Java Mail Enterprise Server (aka Apache James) 2.2.0 allows remote attackers to cause a denial of service (CPU consumption) via a long argument to the MAIL command.

  • EPSS 0.07%
  • Veröffentlicht 31.12.2004 05:00:00
  • Zuletzt bearbeitet 03.04.2025 01:03:51

Spooler in Apache Foundation James 2.2.0 allows local users to cause a denial of service (memory consumption) by triggering various error conditions in the retrieve function, which prevents a lock from being released and causes a memory leak.