FKIE_CVE-2023-41044

Vulnerability from fkie_nvd - Published: 2023-08-31 18:15 - Updated: 2024-11-21 08:20
Severity ?
3.3 (Low) - CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:N
3.8 (Low) - CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N
Summary
Graylog is a free and open log management platform. A partial path traversal vulnerability exists in Graylog's `Support Bundle` feature. The vulnerability is caused by incorrect user input validation in an HTTP API resource. Graylog's Support Bundle feature allows an attacker with valid Admin role credentials to download or delete files in sibling directories of the support bundle directory. The default `data_dir` in operating system packages (DEB, RPM) is set to `/var/lib/graylog-server`. The data directory for the Support Bundle feature is always `<data_dir>/support-bundle`. Due to the partial path traversal vulnerability, an attacker with valid Admin role credentials can read or delete files in directories that start with a `/var/lib/graylog-server/support-bundle` directory name. The vulnerability would allow the download or deletion of files in the following example directories: `/var/lib/graylog-server/support-bundle-test` and `/var/lib/graylog-server/support-bundlesdirectory`. For the Graylog Docker images, the `data_dir` is set to `/usr/share/graylog/data` by default. This vulnerability is fixed in Graylog version 5.1.3 and later. Users are advised to upgrade. Users unable to upgrade should block all HTTP requests to the following HTTP API endpoints by using a reverse proxy server in front of Graylog. `GET /api/system/debug/support/bundle/download/{filename}` and `DELETE /api/system/debug/support/bundle/{filename}`.
References
security-advisories@github.comhttps://github.com/Graylog2/graylog2-server/commit/02b8792e6f4b829f0c1d87fcbf2d58b73458b938Patch
security-advisories@github.comhttps://github.com/Graylog2/graylog2-server/security/advisories/GHSA-2q4p-f6gf-mqr5Exploit, Mitigation, Vendor Advisory
security-advisories@github.comhttps://go2docs.graylog.org/5-1/making_sense_of_your_log_data/cluster_support_bundle.htmProduct
af854a3a-2127-422b-91ae-364da2661108https://github.com/Graylog2/graylog2-server/commit/02b8792e6f4b829f0c1d87fcbf2d58b73458b938Patch
af854a3a-2127-422b-91ae-364da2661108https://github.com/Graylog2/graylog2-server/security/advisories/GHSA-2q4p-f6gf-mqr5Exploit, Mitigation, Vendor Advisory
af854a3a-2127-422b-91ae-364da2661108https://go2docs.graylog.org/5-1/making_sense_of_your_log_data/cluster_support_bundle.htmProduct
Impacted products
Vendor Product Version
graylog graylog *
To clipboard 

{
  "configurations": [
    {
      "nodes": [
        {
          "cpeMatch": [
            {
              "criteria": "cpe:2.3:a:graylog:graylog:*:*:*:*:*:*:*:*",
              "matchCriteriaId": "E213B603-847C-439D-86AA-D77E59653492",
              "versionEndExcluding": "5.1.3",
              "versionStartIncluding": "5.1.0",
              "vulnerable": true
            }
          ],
          "negate": false,
          "operator": "OR"
        }
      ]
    }
  ],
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "Graylog is a free and open log management platform. A partial path traversal vulnerability exists in Graylog\u0027s `Support Bundle` feature. The vulnerability is caused by incorrect user input validation in an HTTP API resource. Graylog\u0027s Support Bundle feature allows an attacker with valid Admin role credentials to download or delete files in sibling directories of the support bundle directory. The default `data_dir` in operating system packages (DEB, RPM) is set to `/var/lib/graylog-server`. The data directory for the Support Bundle feature is always `\u003cdata_dir\u003e/support-bundle`. Due to the partial path traversal vulnerability, an attacker with valid Admin role credentials can read or delete files in directories that start with a `/var/lib/graylog-server/support-bundle` directory name. The vulnerability would allow the download or deletion of files in the following example directories: `/var/lib/graylog-server/support-bundle-test` and `/var/lib/graylog-server/support-bundlesdirectory`. For the Graylog Docker images, the `data_dir` is set to `/usr/share/graylog/data` by default. This vulnerability is fixed in Graylog version 5.1.3 and later. Users are advised to upgrade. Users unable to upgrade should block all HTTP requests to the following HTTP API endpoints by using a reverse proxy server in front of Graylog. `GET /api/system/debug/support/bundle/download/{filename}` and `DELETE /api/system/debug/support/bundle/{filename}`.\n"
    },
    {
      "lang": "es",
      "value": "Graylog es una plataforma de gesti\u00f3n de logs gratuita y de c\u00f3digo abierto. Una vulnerabilidad de salto de ruta parcial existe en la caracter\u00edstica \u0027Support Bundle\u0027 de Graylog. La vulnerabilidad es causada por una validaci\u00f3n de entrada de usuario incorrecta en un recurso de API HTTP. La caracter\u00edstica Support Bundle de Graylog permite a un atacante con credenciales v\u00e1lidas de rol de Administrador descargar o eliminar archivos en directorios hermanos del directorio del paquete de soporte. El \u0027data_dir\u0027 predeterminado en los paquetes del sistema operativo (DEB, RPM) est\u00e1 configurado en \u0027/var/lib/graylog-server\u0027. El directorio de datos para la caracter\u00edstica Support Bundle es siempre \u0027/support-bundle\u0027. Debido a la vulnerabilidad de salto de ruta parcial, un atacante con credenciales v\u00e1lidas de rol de Administrador puede leer o eliminar archivos en directorios que comienzan con un nombre de directorio \u0027/var/lib/graylog-server/support-bundle\u0027. La vulnerabilidad permitir\u00eda la descarga o eliminaci\u00f3n de archivos en los siguientes directorios de ejemplo: \u0027/var/lib/graylog-server/support-bundle-test\u0027 y \u0027/var/lib/graylog-server/support-bundlesdirectory\u0027. Para las im\u00e1genes de Docker de Graylog, el \u0027data_dir\u0027 est\u00e1 configurado en \u0027/usr/share/graylog/data\u0027 por defecto. Esta vulnerabilidad est\u00e1 corregida en Graylog versi\u00f3n 5.1.3 y posteriores. Se aconseja a los usuarios que actualicen. Los usuarios que no puedan actualizar deben bloquear todas las solicitudes HTTP a los siguientes puntos finales de la API HTTP utilizando un servidor proxy inverso delante de Graylog. \u0027GET /api/system/debug/support/bundle/download/{filename}\u0027 y \u0027DELETE /api/system/debug/support/bundle/{filename}\u0027."
    }
  ],
  "id": "CVE-2023-41044",
  "lastModified": "2024-11-21T08:20:26.770",
  "metrics": {
    "cvssMetricV31": [
      {
        "cvssData": {
          "attackComplexity": "HIGH",
          "attackVector": "NETWORK",
          "availabilityImpact": "NONE",
          "baseScore": 3.3,
          "baseSeverity": "LOW",
          "confidentialityImpact": "LOW",
          "integrityImpact": "LOW",
          "privilegesRequired": "HIGH",
          "scope": "UNCHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:N",
          "version": "3.1"
        },
        "exploitabilityScore": 0.7,
        "impactScore": 2.5,
        "source": "security-advisories@github.com",
        "type": "Secondary"
      },
      {
        "cvssData": {
          "attackComplexity": "LOW",
          "attackVector": "NETWORK",
          "availabilityImpact": "NONE",
          "baseScore": 3.8,
          "baseSeverity": "LOW",
          "confidentialityImpact": "LOW",
          "integrityImpact": "LOW",
          "privilegesRequired": "HIGH",
          "scope": "UNCHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N",
          "version": "3.1"
        },
        "exploitabilityScore": 1.2,
        "impactScore": 2.5,
        "source": "nvd@nist.gov",
        "type": "Primary"
      }
    ]
  },
  "published": "2023-08-31T18:15:09.187",
  "references": [
    {
      "source": "security-advisories@github.com",
      "tags": [
        "Patch"
      ],
      "url": "https://github.com/Graylog2/graylog2-server/commit/02b8792e6f4b829f0c1d87fcbf2d58b73458b938"
    },
    {
      "source": "security-advisories@github.com",
      "tags": [
        "Exploit",
        "Mitigation",
        "Vendor Advisory"
      ],
      "url": "https://github.com/Graylog2/graylog2-server/security/advisories/GHSA-2q4p-f6gf-mqr5"
    },
    {
      "source": "security-advisories@github.com",
      "tags": [
        "Product"
      ],
      "url": "https://go2docs.graylog.org/5-1/making_sense_of_your_log_data/cluster_support_bundle.htm"
    },
    {
      "source": "af854a3a-2127-422b-91ae-364da2661108",
      "tags": [
        "Patch"
      ],
      "url": "https://github.com/Graylog2/graylog2-server/commit/02b8792e6f4b829f0c1d87fcbf2d58b73458b938"
    },
    {
      "source": "af854a3a-2127-422b-91ae-364da2661108",
      "tags": [
        "Exploit",
        "Mitigation",
        "Vendor Advisory"
      ],
      "url": "https://github.com/Graylog2/graylog2-server/security/advisories/GHSA-2q4p-f6gf-mqr5"
    },
    {
      "source": "af854a3a-2127-422b-91ae-364da2661108",
      "tags": [
        "Product"
      ],
      "url": "https://go2docs.graylog.org/5-1/making_sense_of_your_log_data/cluster_support_bundle.htm"
    }
  ],
  "sourceIdentifier": "security-advisories@github.com",
  "vulnStatus": "Modified",
  "weaknesses": [
    {
      "description": [
        {
          "lang": "en",
          "value": "CWE-22"
        }
      ],
      "source": "security-advisories@github.com",
      "type": "Secondary"
    }
  ]
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.



Detection rules are retrieved from Rulezet.