FKIE_CVE-2025-26486

Vulnerability from fkie_nvd - Published: 2025-03-19 16:15 - Updated: 2025-07-02 15:15
Summary
Broken or Risky Cryptographic Algorithm, Use of Password Hash With Insufficient Computational Effort, Use of Weak Hash, Use of a One-Way Hash with a Predictable Salt vulnerabilities in Beta80 "Life 1st Identity Manager" enable an attacker with access to password hashes to bruteforce user passwords or find a collision to ultimately while attempting to gain access to a target application that uses "Life 1st Identity Manager" as a service for authentication. This issue affects Life 1st: 1.5.2.14234.
Impacted products
Vendor Product Version

{
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "Broken or Risky Cryptographic Algorithm, Use of Password Hash \nWith Insufficient Computational Effort, Use of Weak Hash, Use of a \nOne-Way Hash with a Predictable Salt vulnerabilities in Beta80 \"Life 1st Identity Manager\"\nenable an attacker with access to\npassword hashes\nto bruteforce user passwords or find a collision to ultimately while attempting to gain access to a target application that uses \"Life 1st Identity Manager\" as a service for authentication.\nThis issue affects Life 1st: 1.5.2.14234."
    },
    {
      "lang": "es",
      "value": "El uso de un algoritmo criptogr\u00e1fico roto o riesgoso, el uso de un hash de contrase\u00f1a con un esfuerzo computacional insuficiente, el uso de un hash d\u00e9bil, el uso de un hash unidireccional con una vulnerabilidad de sal predecible en Beta80 Life 1st permite a un atacante usar la fuerza bruta de las contrase\u00f1as de los usuarios o encontrar una colisi\u00f3n para obtener acceso a una aplicaci\u00f3n de destino que utiliza BETA80 \"Life 1st Identity Manager\" como un servicio para la autenticaci\u00f3n. Este problema afecta a Life 1st: 1.5.2.14234."
    }
  ],
  "id": "CVE-2025-26486",
  "lastModified": "2025-07-02T15:15:25.807",
  "metrics": {
    "cvssMetricV31": [
      {
        "cvssData": {
          "attackComplexity": "LOW",
          "attackVector": "LOCAL",
          "availabilityImpact": "NONE",
          "baseScore": 6.0,
          "baseSeverity": "MEDIUM",
          "confidentialityImpact": "HIGH",
          "integrityImpact": "NONE",
          "privilegesRequired": "HIGH",
          "scope": "CHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N",
          "version": "3.1"
        },
        "exploitabilityScore": 1.5,
        "impactScore": 4.0,
        "source": "a6d3dc9e-0591-4a13-bce7-0f5b31ff6158",
        "type": "Secondary"
      }
    ]
  },
  "published": "2025-03-19T16:15:31.457",
  "references": [
    {
      "source": "a6d3dc9e-0591-4a13-bce7-0f5b31ff6158",
      "url": "https://euvd.enisa.europa.eu/vulnerability/CVE-2025-26486"
    },
    {
      "source": "a6d3dc9e-0591-4a13-bce7-0f5b31ff6158",
      "url": "https://www.cvcn.gov.it/cvcn/cve/CVE-2025-26486"
    }
  ],
  "sourceIdentifier": "a6d3dc9e-0591-4a13-bce7-0f5b31ff6158",
  "vulnStatus": "Awaiting Analysis",
  "weaknesses": [
    {
      "description": [
        {
          "lang": "en",
          "value": "CWE-327"
        },
        {
          "lang": "en",
          "value": "CWE-328"
        },
        {
          "lang": "en",
          "value": "CWE-760"
        },
        {
          "lang": "en",
          "value": "CWE-916"
        }
      ],
      "source": "a6d3dc9e-0591-4a13-bce7-0f5b31ff6158",
      "type": "Secondary"
    }
  ]
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

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.


Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…