Apache Allura security advisories

Security information for Apache Allura

Reporting

Do you want disclose a potential security issue for Apache Allura? Send your report to the Apache Security Team.

Advisories

This section is experimental: it provides advisories since 2023 and may lag behind the official CVE publications. If you have any feedback on how you would like this data to be provided, you are welcome to reach out on our public mailinglist or privately on security@apache.org

Stored authenticated XSS

CVE-2024-38379 [CVE] [CVE json] [OSV json]

Last updated: 2025-02-06T14:32:32.361Z

Affected

  • Apache Allura from 1.4.0 through 1.17.0

Description

Apache Allura's neighborhood settings are vulnerable to a stored XSS attack.  Only neighborhood admins can access these settings, so the scope of risk is limited to configurations where neighborhood admins are not fully trusted.

This issue affects Apache Allura: from 1.4.0 through 1.17.0.

Users are recommended to upgrade to version 1.17.1, which fixes the issue.

References

Credits

  • Ömer “WASP” Akincir (finder)

sensitive information exposure via DNS rebinding

CVE-2024-36471 [CVE] [CVE json] [OSV json]

Last updated: 2024-06-10T21:55:03.113Z

Affected

  • Apache Allura from 1.0.1 through 1.16.0

Description

Import functionality is vulnerable to DNS rebinding attacks between verification and processing of the URL.  Project administrators can run these imports, which could cause Allura to read from internal services and expose them.

This issue affects Apache Allura from 1.0.1 through 1.16.0.

Users are recommended to upgrade to version 1.17.0, which fixes the issue. If you are unable to upgrade, set "disable_entry_points.allura.importers = forge-tracker, forge-discussion" in your .ini config file.


References

Credits

sensitive information exposure via import

CVE-2023-46851 [CVE] [CVE json] [OSV json]

Last updated: 2023-11-07T08:56:30.662Z

Affected

  • Apache Allura from 1.0.1 through 1.15.0

Description

Allura Discussion and Allura Forum importing does not restrict URL values specified in attachments. Project administrators can run these imports, which could cause Allura to read local files and expose them.  Exposing internal files then can lead to other exploits, like session hijacking, or remote code execution.

This issue affects Apache Allura from 1.0.1 through 1.15.0.

Users are recommended to upgrade to version 1.16.0, which fixes the issue.  If you are unable to upgrade, set "disable_entry_points.allura.importers = forge-tracker, forge-discussion" in your .ini config file.

References

Credits

  • Stefan Schiller (Sonar) (finder)