FKIE_CVE-2024-4844

Vulnerability from fkie_nvd - Published: 2024-05-16 07:15 - Updated: 2024-11-21 09:43
Severity ?
7.5 (High) - CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Summary
Hardcoded credentials vulnerability in Trellix ePolicy Orchestrator (ePO) on Premise prior to 5.10 Service Pack 1 Update 2 allows an attacker with admin privileges on the ePO server to read the contents of the orion.keystore file, allowing them to access the ePO database encryption key. This was possible through using a hard coded password for the keystore. Access Control restrictions on the file mean this would not be exploitable unless the user is the system admin for the server that ePO is running on.
References
trellixpsirt@trellix.comhttps://thrive.trellix.com/s/article/000013505
af854a3a-2127-422b-91ae-364da2661108https://thrive.trellix.com/s/article/000013505
Impacted products
Vendor Product Version
To clipboard 

{
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "Hardcoded credentials vulnerability in Trellix ePolicy Orchestrator (ePO) on Premise prior to 5.10 Service Pack 1 Update 2 allows an attacker with admin privileges on the ePO server to read the contents of the orion.keystore file, allowing them to access the ePO database encryption key.  This was possible through using a hard coded password for the keystore.  Access Control restrictions on the file mean this would not be exploitable unless the user is the system admin for the server that ePO is running on."
    },
    {
      "lang": "es",
      "value": "La vulnerabilidad de credenciales codificadas de forma r\u00edgida en Trellix ePolicy Orchestrator (ePO) on Premise anterior a la versi\u00f3n 5.10 Service Pack 1 Update 2 permite a un atacante con privilegios de administrador en el servidor ePO leer el contenido del archivo orion.keystore, lo que le permite acceder a la clave de cifrado de la base de datos de ePO. Esto era posible mediante el uso de una contrase\u00f1a codificada de forma r\u00edgida para el almac\u00e9n de claves. Las restricciones de control de acceso en el archivo significan que esto no ser\u00eda explotable a menos que el usuario sea el administrador del sistema del servidor en el que se ejecuta ePO."
    }
  ],
  "id": "CVE-2024-4844",
  "lastModified": "2024-11-21T09:43:43.280",
  "metrics": {
    "cvssMetricV31": [
      {
        "cvssData": {
          "attackComplexity": "HIGH",
          "attackVector": "NETWORK",
          "availabilityImpact": "HIGH",
          "baseScore": 7.5,
          "baseSeverity": "HIGH",
          "confidentialityImpact": "HIGH",
          "integrityImpact": "HIGH",
          "privilegesRequired": "LOW",
          "scope": "UNCHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H",
          "version": "3.1"
        },
        "exploitabilityScore": 1.6,
        "impactScore": 5.9,
        "source": "trellixpsirt@trellix.com",
        "type": "Secondary"
      }
    ]
  },
  "published": "2024-05-16T07:15:50.743",
  "references": [
    {
      "source": "trellixpsirt@trellix.com",
      "url": "https://thrive.trellix.com/s/article/000013505"
    },
    {
      "source": "af854a3a-2127-422b-91ae-364da2661108",
      "url": "https://thrive.trellix.com/s/article/000013505"
    }
  ],
  "sourceIdentifier": "trellixpsirt@trellix.com",
  "vulnStatus": "Awaiting Analysis",
  "weaknesses": [
    {
      "description": [
        {
          "lang": "en",
          "value": "CWE-798"
        }
      ],
      "source": "trellixpsirt@trellix.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.