Apache Allura

Submit a proposal Propose CVE/GCVE/GHSA reference

Approved changes feed: RSS · Atom

cpe:2.3:a:apache_software_foundation:apache_allura:*:*:*:*:*:*:*:*

part: a version: * update: *

VendorApache Software Foundation (f563070d-e18f-561b-b86c-987936937e8a)
ProductApache Allura (3c36a3b8-ab73-5cb9-b43c-ca1f635801d0)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*
NotesImported from gcve-enriched-dumps CVE data

PURL mappings

PURLSourceLast updated
No PURL mappings for this CPE yet.

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2024-38379 vulnerable 2026-06-08 06:41:45.160470 Apache Allura: Stored authenticated XSS
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.
Published: 2024-06-22T09:09:32.464Z
Updated: 2025-03-19T14:35:10.998Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2024-36471 vulnerable 2026-06-08 06:39:45.057768 Apache Allura: sensitive information exposure via DNS rebinding
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.
Published: 2024-06-10T21:55:06.170Z
Updated: 2024-09-13T16:03:21.981Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2023-46851 vulnerable 2026-06-08 06:14:23.603420 Apache Allura: sensitive information exposure via import
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.
Published: 2023-11-07T08:56:35.172Z
Updated: 2024-09-04T20:12:28.257Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2018-1319 vulnerable 2026-06-08 05:11:17.680708 Details available
In Apache Allura prior to 1.8.1, attackers may craft URLs that cause HTTP response splitting. If a victim goes to a maliciously crafted URL, unwanted results may occur including XSS or service denial for the victim's browsing session.
Published: 2018-03-15T20:00:00.000Z
Updated: 2024-09-17T01:41:55.447Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2018-1299 vulnerable 2026-06-08 05:11:17.564315 Details available
In Apache Allura before 1.8.0, unauthenticated attackers may retrieve arbitrary files through the Allura web application. Some webservers used with Allura, such as Nginx, Apache/mod_wsgi or paster may prevent the attack from succeeding. Others, such as gunicorn do not prevent it and leave Allura vulnerable.
Published: 2018-02-06T19:00:00.000Z
Updated: 2024-09-16T21:07:54.673Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.