pysec-2023-261
Vulnerability from pysec
Published
2023-12-12 02:15
Modified
2024-09-29 00:37
Severity ?
Details

SAP BTP Security Services Integration Library ([Python] sap-xssec) - versions < 4.1.0, allow under certain conditions an escalation of privileges. On successful exploitation, an unauthenticated attacker can obtain arbitrary permissions within the application.

Impacted products
Name purl
sap-xssec pkg:pypi/sap-xssec



{
   affected: [
      {
         package: {
            ecosystem: "PyPI",
            name: "sap-xssec",
            purl: "pkg:pypi/sap-xssec",
         },
         ranges: [
            {
               events: [
                  {
                     introduced: "0",
                  },
                  {
                     fixed: "4.1.0",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
         versions: [
            "1.1.8",
            "2.0.1",
            "2.0.10",
            "2.0.11",
            "2.0.12",
            "2.0.2",
            "2.0.3",
            "2.0.4",
            "2.0.5",
            "2.0.6",
            "2.0.7",
            "2.0.8",
            "2.0.9",
            "2.1.0",
            "3.0.0",
            "3.1.0",
            "3.2.0",
            "3.3.0",
            "4.0.0",
            "4.0.1",
         ],
      },
   ],
   aliases: [
      "CVE-2023-50423",
      "GHSA-6mjg-37cp-42x5",
   ],
   details: "SAP BTP Security Services Integration Library ([Python] sap-xssec) - versions < 4.1.0, allow under certain conditions an escalation of privileges. On successful exploitation, an unauthenticated attacker can obtain arbitrary permissions within the application.",
   id: "PYSEC-2023-261",
   modified: "2024-09-29T00:37:11.092461+00:00",
   published: "2023-12-12T02:15:00+00:00",
   references: [
      {
         type: "WEB",
         url: "https://me.sap.com/notes/3411067",
      },
      {
         type: "ADVISORY",
         url: "https://www.sap.com/documents/2022/02/fa865ea4-167e-0010-bca6-c68f7e60039b.html",
      },
      {
         type: "PACKAGE",
         url: "https://pypi.org/project/sap-xssec/",
      },
      {
         type: "ADVISORY",
         url: "https://blogs.sap.com/2023/12/12/unveiling-critical-security-updates-sap-btp-security-note-3411067/",
      },
      {
         type: "ADVISORY",
         url: "https://github.com/SAP/cloud-pysec/security/advisories/GHSA-6mjg-37cp-42x5",
      },
      {
         type: "WEB",
         url: "https://github.com/SAP/cloud-pysec/",
      },
   ],
   severity: [
      {
         score: "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
         type: "CVSS_V3",
      },
   ],
}


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.


Loading…

Loading…

Loading…

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.