Skip to content
Heist/ feed
Back to feed
Unrated

Apache Allura: sensitive information exposure via import

Type: advisorySources: OSV

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.

Products
Not specified
Affected versions
Not specified
Fixed versions
Not specified
CVEs
CVE-2023-46851
Confirmed fixed CVEs
Not specified
Updated in this feed
7 Nov 2026, 16:45 UTC · Revision 1

Source evidence

Apache Allura: sensitive information exposure via import

core-osv · Original source

Published 7 Nov 2023, 08:56 UTC

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.

osv:CVE-2023-46851
Complete source record
{
  "id": "8ae5bcfa16b3e8f02e0c0ef2909d96cd66ccba107d06444c215151f337eaac1a",
  "url": "https://osv.dev/vulnerability/CVE-2023-46851",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "Apache Allura: sensitive information exposure via import",
    "summary": "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.",
    "evidence": "osv:CVE-2023-46851",
    "products": [],
    "severity": "unknown",
    "structured": {
      "id": "CVE-2023-46851",
      "aliases": [
        "CVE-2023-46851"
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://github.com/apache/allura",
              "type": "GIT",
              "events": [
                {
                  "introduced": "924e0204706aeb5367e60df19ba38b26ac4474a3"
                },
                {
                  "fixed": "705f6d38c47347113eb7b7032aa4932f4ef645bc"
                }
              ],
              "database_specific": {
                "extracted_events": [
                  {
                    "cpe": "cpe:2.3:a:apache:allura:*:*:*:*:*:*:*:*",
                    "range": [
                      {
                        "introduced": "1.0.1"
                      },
                      {
                        "fixed": "1.16.0"
                      }
                    ],
                    "source": "CPE_RANGE"
                  }
                ]
              }
            }
          ],
          "versions": [
            "rel/1.15.0",
            "rel/1.14.0",
            "rel/1.13.0",
            "rel/1.12.0",
            "rel/1.11.1",
            "rel/1.11.0",
            "rel/1.10.0",
            "rel/1.9.0",
            "rel/1.8.1",
            "rel/1.8.0",
            "rel/1.7.0",
            "rel/1.6.0",
            "rel/1.5.0",
            "rel/1.4.0",
            "rel/1.3.2",
            "asf_release_1.3.2",
            "rel/1.3.1",
            "asf_release_1.3.1",
            "rel/1.3.0",
            "asf_release_1.3.0",
            "rel/1.2.1",
            "asf_release_1.2.1",
            "rel/1.2.0",
            "asf_release_1.2.0",
            "rel/1.1.0",
            "asf_release_1.1.0",
            "rel/1.0.1",
            "asf_release_1.0.1"
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2023-46851.json"
          }
        }
      ],
      "modified": "2026-10-28T02:30:51.063053385Z",
      "provider": "osv",
      "references": [
        "https://allura.apache.org/posts/2023-allura-1.16.0.html",
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2023/46xxx/CVE-2023-46851.json",
        "https://lists.apache.org/thread/hqk0vltl7qgrq215zgwjfoj0khbov0gx",
        "https://nvd.nist.gov/vuln/detail/CVE-2023-46851"
      ],
      "provider_metadata": {
        "cwe_ids": [
          "CWE-20",
          "CWE-200",
          "CWE-73"
        ],
        "cna_assigner": "apache",
        "unresolved_ranges": [
          {
            "extracted_events": [
              {
                "range": [
                  {
                    "introduced": "1.0.1"
                  },
                  {
                    "last_affected": "1.15.0"
                  }
                ],
                "source": "AFFECTED_FIELD",
                "strategy": "StandardRange"
              }
            ]
          }
        ],
        "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2023/46xxx/CVE-2023-46851.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2023-46851",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": null
  },
  "source_id": "core-osv",
  "document_id": 519905,
  "published_at": "2023-11-07T08:56:35.172+00:00"
}