fkie_cve-2024-11022
Vulnerability from fkie_nvd
Published
2024-12-06 13:15
Modified
2024-12-06 13:15
Severity ?
5.6 (Medium) - CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L
Summary
The authentication process to the web server uses a challenge response procedure which inludes the nonce and additional information. This challenge can be used several times for login and is therefore vulnerable for a replay attack.
References
psirt@sick.dehttps://cdn.sick.com/media/docs/1/11/411/Special_information_CYBERSECURITY_BY_SICK_en_IM0084411.PDF
psirt@sick.dehttps://sick.com/psirt
psirt@sick.dehttps://www.cisa.gov/resources-tools/resources/ics-recommended-practices
psirt@sick.dehttps://www.first.org/cvss/calculator/3.1
psirt@sick.dehttps://www.sick.com/.well-known/csaf/white/2024/sca-2024-0006.json
psirt@sick.dehttps://www.sick.com/.well-known/csaf/white/2024/sca-2024-0006.pdf
Impacted products
Vendor Product Version


To clipboard 

{
   cveTags: [],
   descriptions: [
      {
         lang: "en",
         value: "The authentication process to the web server uses a challenge response procedure which\ninludes the nonce and additional information. This challenge can be used several times for login and is\ntherefore vulnerable for a replay attack.",
      },
      {
         lang: "es",
         value: "El proceso de autenticación en el servidor web utiliza un procedimiento de desafío-respuesta que incluye el nonce y otra información adicional. Este desafío se puede utilizar varias veces para iniciar sesión y, por lo tanto, es vulnerable a un ataque de repetición.",
      },
   ],
   id: "CVE-2024-11022",
   lastModified: "2024-12-06T13:15:06.267",
   metrics: {
      cvssMetricV31: [
         {
            cvssData: {
               attackComplexity: "HIGH",
               attackVector: "NETWORK",
               availabilityImpact: "LOW",
               baseScore: 5.6,
               baseSeverity: "MEDIUM",
               confidentialityImpact: "LOW",
               integrityImpact: "LOW",
               privilegesRequired: "NONE",
               scope: "UNCHANGED",
               userInteraction: "NONE",
               vectorString: "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L",
               version: "3.1",
            },
            exploitabilityScore: 2.2,
            impactScore: 3.4,
            source: "psirt@sick.de",
            type: "Secondary",
         },
      ],
   },
   published: "2024-12-06T13:15:06.267",
   references: [
      {
         source: "psirt@sick.de",
         url: "https://cdn.sick.com/media/docs/1/11/411/Special_information_CYBERSECURITY_BY_SICK_en_IM0084411.PDF",
      },
      {
         source: "psirt@sick.de",
         url: "https://sick.com/psirt",
      },
      {
         source: "psirt@sick.de",
         url: "https://www.cisa.gov/resources-tools/resources/ics-recommended-practices",
      },
      {
         source: "psirt@sick.de",
         url: "https://www.first.org/cvss/calculator/3.1",
      },
      {
         source: "psirt@sick.de",
         url: "https://www.sick.com/.well-known/csaf/white/2024/sca-2024-0006.json",
      },
      {
         source: "psirt@sick.de",
         url: "https://www.sick.com/.well-known/csaf/white/2024/sca-2024-0006.pdf",
      },
   ],
   sourceIdentifier: "psirt@sick.de",
   vulnStatus: "Awaiting Analysis",
   weaknesses: [
      {
         description: [
            {
               lang: "en",
               value: "CWE-323",
            },
         ],
         source: "psirt@sick.de",
         type: "Secondary",
      },
   ],
}


Log in or create an account to share your comment.

Security Advisory comment format.

This schema specifies the format of a comment related to a security advisory.

UUIDv4 of the comment
UUIDv4 of the Vulnerability-Lookup instance
When the comment was created originally
When the comment was last updated
Title of the comment
Description of the comment
The identifier of the vulnerability (CVE ID, GHSA-ID, PYSEC ID, etc.).



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.