FKIE_CVE-2022-26388

Vulnerability from fkie_nvd - Published: 2025-02-07 17:15 - Updated: 2025-02-07 17:15
Summary
A use of hard-coded password vulnerability may allow authentication abuse.This issue affects ELI 380 Resting Electrocardiograph: Versions 2.6.0 and prior; ELI 280/BUR280/MLBUR 280 Resting Electrocardiograph: Versions 2.3.1 and prior; ELI 250c/BUR 250c Resting Electrocardiograph: Versions 2.1.2 and prior; ELI 150c/BUR 150c/MLBUR 150c Resting Electrocardiograph: Versions 2.2.0 and prior.
Impacted products
Vendor Product Version

{
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "A use of hard-coded password vulnerability may allow authentication abuse.This issue affects ELI 380 Resting Electrocardiograph: \n\nVersions 2.6.0 and prior; ELI 280/BUR280/MLBUR 280 Resting Electrocardiograph:\n\nVersions 2.3.1 and prior; ELI 250c/BUR 250c Resting Electrocardiograph:\n\nVersions 2.1.2 and prior; ELI 150c/BUR 150c/MLBUR 150c Resting Electrocardiograph: \n\nVersions 2.2.0 and prior."
    },
    {
      "lang": "es",
      "value": "Una vulnerabilidad en el uso de contrase\u00f1as codificadas de forma r\u00edgida puede permitir el abuso de la autenticaci\u00f3n. Este problema afecta al electrocardi\u00f3grafo en reposo ELI 380: versiones 2.6.0 y anteriores; al electrocardi\u00f3grafo en reposo ELI 280/BUR280/MLBUR 280: versiones 2.3.1 y anteriores; al electrocardi\u00f3grafo en reposo ELI 250c/BUR 250c: versiones 2.1.2 y anteriores; al electrocardi\u00f3grafo en reposo ELI 150c/BUR 150c/MLBUR 150c: versiones 2.2.0 y anteriores."
    }
  ],
  "id": "CVE-2022-26388",
  "lastModified": "2025-02-07T17:15:21.960",
  "metrics": {
    "cvssMetricV31": [
      {
        "cvssData": {
          "attackComplexity": "LOW",
          "attackVector": "PHYSICAL",
          "availabilityImpact": "LOW",
          "baseScore": 6.4,
          "baseSeverity": "MEDIUM",
          "confidentialityImpact": "HIGH",
          "integrityImpact": "HIGH",
          "privilegesRequired": "NONE",
          "scope": "UNCHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L",
          "version": "3.1"
        },
        "exploitabilityScore": 0.9,
        "impactScore": 5.5,
        "source": "productsecurity@baxter.com",
        "type": "Secondary"
      }
    ]
  },
  "published": "2025-02-07T17:15:21.960",
  "references": [
    {
      "source": "productsecurity@baxter.com",
      "url": "https://hillrom.com/en/responsible-disclosures/"
    },
    {
      "source": "productsecurity@baxter.com",
      "url": "https://www.cisa.gov/news-events/ics-medical-advisories/icsma-22-167-01"
    }
  ],
  "sourceIdentifier": "productsecurity@baxter.com",
  "vulnStatus": "Awaiting Analysis",
  "weaknesses": [
    {
      "description": [
        {
          "lang": "en",
          "value": "CWE-259"
        }
      ],
      "source": "productsecurity@baxter.com",
      "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…