GCVE Workshop - 22 September 2026 (14:00-18:00), Luxembourg Before The Vulnopticon Conference - Registration

FKIE_CVE-2024-41733

Vulnerability from fkie_nvd - Published: 2024-08-13 04:15 - Updated: 2026-06-17 07:48
Severity
5.3 (Medium) - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
5.3 (Medium) - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Summary
In SAP Commerce, valid user accounts can be identified during the customer registration and login processes. This allows a potential attacker to learn if a given e-mail is used for an account, but does not grant access to any customer data beyond this knowledge. The attacker must already know the e-mail that they wish to test for. The impact on confidentiality therefore is low and no impact to integrity or availability
References
cna@sap.comhttps://me.sap.com/notes/3471450Permissions Required
cna@sap.comhttps://url.sap/sapsecuritypatchdayVendor Advisory
Impacted products
Vendor Product Version
sap commerce com_cloud_2211
sap commerce hy_com_2205
To clipboard 

{
  "affected": [
    {
      "affectedData": [
        {
          "defaultStatus": "unaffected",
          "product": "SAP Commerce",
          "vendor": "SAP_SE",
          "versions": [
            {
              "status": "affected",
              "version": "HY_COM 2205"
            },
            {
              "status": "affected",
              "version": "COM_CLOUD 2211"
            }
          ]
        }
      ],
      "source": "cna@sap.com"
    },
    {
      "affectedData": [
        {
          "cpes": [
            "cpe:2.3:a:sap:commerce_cloud:2211:*:*:*:*:*:*:*"
          ],
          "defaultStatus": "unaffected",
          "product": "commerce_cloud",
          "vendor": "sap",
          "versions": [
            {
              "status": "affected",
              "version": "2211"
            }
          ]
        },
        {
          "cpes": [
            "cpe:2.3:a:sap:commerce_hycom:2205:*:*:*:*:*:*:*"
          ],
          "defaultStatus": "unaffected",
          "product": "commerce_hycom",
          "vendor": "sap",
          "versions": [
            {
              "status": "affected",
              "version": "2205"
            }
          ]
        }
      ],
      "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0"
    }
  ],
  "configurations": [
    {
      "nodes": [
        {
          "cpeMatch": [
            {
              "criteria": "cpe:2.3:a:sap:commerce:com_cloud_2211:*:*:*:*:*:*:*",
              "matchCriteriaId": "9675EB72-CE1B-44EB-830C-5EE3760B4E8C",
              "vulnerable": true
            },
            {
              "criteria": "cpe:2.3:a:sap:commerce:hy_com_2205:*:*:*:*:*:*:*",
              "matchCriteriaId": "1D604185-AD43-4C48-8B43-ADC9560A677E",
              "vulnerable": true
            }
          ],
          "negate": false,
          "operator": "OR"
        }
      ]
    }
  ],
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "In SAP Commerce, valid user accounts can be\nidentified during the customer registration and login processes. This allows a\npotential attacker to learn if a given e-mail is used for an account, but does\nnot grant access to any customer data beyond this knowledge. The attacker must\nalready know the e-mail that they wish to test for. The impact on\nconfidentiality therefore is low and no impact to integrity or availability"
    },
    {
      "lang": "es",
      "value": "En SAP Commerce, las cuentas de usuario v\u00e1lidas se pueden identificar durante los procesos de registro e inicio de sesi\u00f3n del cliente. Esto permite a un atacante potencial saber si un correo electr\u00f3nico determinado se utiliza para una cuenta, pero no otorga acceso a ning\u00fan dato del cliente m\u00e1s all\u00e1 de este conocimiento. El atacante ya debe conocer el correo electr\u00f3nico que desea probar. Por lo tanto, el impacto sobre la confidencialidad es bajo y no afecta la integridad o la disponibilidad."
    }
  ],
  "id": "CVE-2024-41733",
  "lastModified": "2026-06-17T07:48:09.203",
  "metrics": {
    "cvssMetricV31": [
      {
        "cvssData": {
          "attackComplexity": "LOW",
          "attackVector": "NETWORK",
          "availabilityImpact": "NONE",
          "baseScore": 5.3,
          "baseSeverity": "MEDIUM",
          "confidentialityImpact": "LOW",
          "integrityImpact": "NONE",
          "privilegesRequired": "NONE",
          "scope": "UNCHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N",
          "version": "3.1"
        },
        "exploitabilityScore": 3.9,
        "impactScore": 1.4,
        "source": "cna@sap.com",
        "type": "Secondary"
      },
      {
        "cvssData": {
          "attackComplexity": "LOW",
          "attackVector": "NETWORK",
          "availabilityImpact": "NONE",
          "baseScore": 5.3,
          "baseSeverity": "MEDIUM",
          "confidentialityImpact": "LOW",
          "integrityImpact": "NONE",
          "privilegesRequired": "NONE",
          "scope": "UNCHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N",
          "version": "3.1"
        },
        "exploitabilityScore": 3.9,
        "impactScore": 1.4,
        "source": "nvd@nist.gov",
        "type": "Primary"
      }
    ],
    "ssvcV203": [
      {
        "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
        "ssvcData": {
          "id": "CVE-2024-41733",
          "options": [
            {
              "exploitation": "none"
            },
            {
              "automatable": "no"
            },
            {
              "technicalImpact": "total"
            }
          ],
          "role": "CISA Coordinator",
          "timestamp": "2024-08-13T14:36:37.582079Z",
          "version": "2.0.3"
        }
      }
    ]
  },
  "published": "2024-08-13T04:15:08.987",
  "references": [
    {
      "source": "cna@sap.com",
      "tags": [
        "Permissions Required"
      ],
      "url": "https://me.sap.com/notes/3471450"
    },
    {
      "source": "cna@sap.com",
      "tags": [
        "Vendor Advisory"
      ],
      "url": "https://url.sap/sapsecuritypatchday"
    }
  ],
  "sourceIdentifier": "cna@sap.com",
  "vulnStatus": "Analyzed",
  "weaknesses": [
    {
      "description": [
        {
          "lang": "en",
          "value": "CWE-200"
        }
      ],
      "source": "cna@sap.com",
      "type": "Secondary"
    },
    {
      "description": [
        {
          "lang": "en",
          "value": "NVD-CWE-noinfo"
        }
      ],
      "source": "nvd@nist.gov",
      "type": "Primary"
    }
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

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.


Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.