fkie_cve-2025-0714
Vulnerability from fkie_nvd
Published
2025-02-17 12:15
Modified
2025-02-19 09:15
Severity ?
6.5 (Medium) - CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
Summary
The vulnerability exists in the password storage of Mobateks MobaXterm in versions below 25.0. MobaXTerm uses an initialisation vector (IV) consisting only of zero bytes and a master key to encrypt each password individually. In the default configuration, on opening MobaXTerm, the user is prompted for their password. A derivative of the password is used as the master key. As both the master key and the IV are the same for each stored password, the AES CFB ciphertext depends only on the plaintext (the password). The static IV and master key make it easier to obtain sensitive information and to decrypt data when it is stored at rest.
References
a341c0d1-ebf7-493f-a84e-38cf86618674https://www.cirosec.de/sa/sa-2024-012
Impacted products
Vendor Product Version


To clipboard 

{
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "The vulnerability exists in the password storage of Mobateks MobaXterm in versions below 25.0. MobaXTerm uses an initialisation vector (IV) consisting only of zero bytes and a master key to encrypt each password individually. In the default configuration, on opening MobaXTerm, the user is prompted for their password. A derivative of the password is used as the master key. As both the master key and the IV are the same for each stored password, the AES CFB ciphertext depends only on the plaintext (the password). The static IV and master key make it easier to obtain sensitive information and to decrypt data when it is stored at rest."
    },
    {
      "lang": "es",
      "value": "La vulnerabilidad exist\u00eda en el almacenamiento de contrase\u00f1as de MobaXterm de Mobatek en versiones anteriores a 25.0. MobaXTerm utiliza un vector de inicializaci\u00f3n (IV) que se genera cifrando bytes nulos con un derivado de la clave maestra del usuario. Como la clave maestra es est\u00e1tica y AES ECB produce la misma salida con la misma entrada, el IV para AES CFB es siempre el mismo. El IV est\u00e1tico facilita la obtenci\u00f3n de informaci\u00f3n confidencial y el descifrado de datos si estos se almacenan en reposo."
    }
  ],
  "id": "CVE-2025-0714",
  "lastModified": "2025-02-19T09:15:09.863",
  "metrics": {
    "cvssMetricV31": [
      {
        "cvssData": {
          "attackComplexity": "LOW",
          "attackVector": "LOCAL",
          "availabilityImpact": "NONE",
          "baseScore": 6.5,
          "baseSeverity": "MEDIUM",
          "confidentialityImpact": "HIGH",
          "integrityImpact": "NONE",
          "privilegesRequired": "LOW",
          "scope": "CHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N",
          "version": "3.1"
        },
        "exploitabilityScore": 2.0,
        "impactScore": 4.0,
        "source": "a341c0d1-ebf7-493f-a84e-38cf86618674",
        "type": "Secondary"
      }
    ]
  },
  "published": "2025-02-17T12:15:27.570",
  "references": [
    {
      "source": "a341c0d1-ebf7-493f-a84e-38cf86618674",
      "url": "https://www.cirosec.de/sa/sa-2024-012"
    }
  ],
  "sourceIdentifier": "a341c0d1-ebf7-493f-a84e-38cf86618674",
  "vulnStatus": "Awaiting Analysis",
  "weaknesses": [
    {
      "description": [
        {
          "lang": "en",
          "value": "CWE-1204"
        }
      ],
      "source": "a341c0d1-ebf7-493f-a84e-38cf86618674",
      "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 seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.