fkie_cve-2022-46337
Vulnerability from fkie_nvd
Published
2023-11-20 09:15
Modified
2024-11-21 07:30
Severity ?
9.8 (Critical) - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Summary
A cleverly devised username might bypass LDAP authentication checks. In LDAP-authenticated Derby installations, this could let an attacker fill up the disk by creating junk Derby databases. In LDAP-authenticated Derby installations, this could also allow the attacker to execute malware which was visible to and executable by the account which booted the Derby server. In LDAP-protected databases which weren't also protected by SQL GRANT/REVOKE authorization, this vulnerability could also let an attacker view and corrupt sensitive data and run sensitive database functions and procedures. Mitigation: Users should upgrade to Java 21 and Derby 10.17.1.0. Alternatively, users who wish to remain on older Java versions should build their own Derby distribution from one of the release families to which the fix was backported: 10.16, 10.15, and 10.14. Those are the releases which correspond, respectively, with Java LTS versions 17, 11, and 8.
References
security@apache.orghttps://lists.apache.org/thread/q23kvvtoohgzwybxpwozmvvk17rp0td3Mailing List
af854a3a-2127-422b-91ae-364da2661108https://lists.apache.org/thread/q23kvvtoohgzwybxpwozmvvk17rp0td3Mailing List
Impacted products
Vendor Product Version
apache derby *
apache derby *
apache derby 10.16.1.1


To clipboard 

{
   configurations: [
      {
         nodes: [
            {
               cpeMatch: [
                  {
                     criteria: "cpe:2.3:a:apache:derby:*:*:*:*:*:*:*:*",
                     matchCriteriaId: "ECA644FF-857A-4B43-BED5-9528613284F4",
                     versionEndExcluding: "10.14.3.0",
                     versionStartIncluding: "10.1.1.0",
                     vulnerable: true,
                  },
                  {
                     criteria: "cpe:2.3:a:apache:derby:*:*:*:*:*:*:*:*",
                     matchCriteriaId: "1A4C2868-1FF3-46C7-9C21-DA9C1C8268B4",
                     versionEndExcluding: "10.15.2.1",
                     versionStartIncluding: "10.15.1.3",
                     vulnerable: true,
                  },
                  {
                     criteria: "cpe:2.3:a:apache:derby:10.16.1.1:*:*:*:*:*:*:*",
                     matchCriteriaId: "80549185-7AB5-447C-9B9D-59B0E1156758",
                     vulnerable: true,
                  },
               ],
               negate: false,
               operator: "OR",
            },
         ],
      },
   ],
   cveTags: [],
   descriptions: [
      {
         lang: "en",
         value: "A cleverly devised username might bypass LDAP authentication checks. In \nLDAP-authenticated Derby installations, this could let an attacker fill \nup the disk by creating junk Derby databases. In LDAP-authenticated \nDerby installations, this could also allow the attacker to execute \nmalware which was visible to and executable by the account which booted \nthe Derby server. In LDAP-protected databases which weren't also \nprotected by SQL GRANT/REVOKE authorization, this vulnerability could \nalso let an attacker view and corrupt sensitive data and run sensitive \ndatabase functions and procedures.\n\nMitigation:\n\nUsers should upgrade to Java 21 and Derby 10.17.1.0.\n\nAlternatively, users who wish to remain on older Java versions should \nbuild their own Derby distribution from one of the release families to \nwhich the fix was backported: 10.16, 10.15, and 10.14. Those are the \nreleases which correspond, respectively, with Java LTS versions 17, 11, \nand 8.\n\n",
      },
      {
         lang: "es",
         value: "Un nombre de usuario inteligentemente diseñado podría omitir las comprobaciones de autenticación LDAP. En instalaciones Derby autenticadas por LDAP, esto podría permitir que un atacante llene el disco creando bases de datos Derby basura. En instalaciones de Derby autenticadas por LDAP, esto también podría permitir al atacante ejecutar malware que era visible y ejecutable por la cuenta que arrancó el servidor Derby. En bases de datos protegidas por LDAP que tampoco estaban protegidas por la autorización SQL GRANT/REVOKE, esta vulnerabilidad también podría permitir que un atacante vea y corrompa datos confidenciales y ejecute funciones y procedimientos de bases de datos confidenciales. Mitigación: los usuarios deben actualizar a Java 21 y Derby 10.17.1.0. Alternativamente, los usuarios que deseen permanecer en versiones anteriores de Java deben crear su propia distribución Derby a partir de una de las familias de versiones a las que se admitió la solución: 10.16, 10.15 y 10.14. Esas son las versiones que corresponden, respectivamente, a las versiones 17, 11 y 8 de Java LTS.",
      },
   ],
   id: "CVE-2022-46337",
   lastModified: "2024-11-21T07:30:24.783",
   metrics: {
      cvssMetricV31: [
         {
            cvssData: {
               attackComplexity: "LOW",
               attackVector: "NETWORK",
               availabilityImpact: "HIGH",
               baseScore: 9.8,
               baseSeverity: "CRITICAL",
               confidentialityImpact: "HIGH",
               integrityImpact: "HIGH",
               privilegesRequired: "NONE",
               scope: "UNCHANGED",
               userInteraction: "NONE",
               vectorString: "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
               version: "3.1",
            },
            exploitabilityScore: 3.9,
            impactScore: 5.9,
            source: "nvd@nist.gov",
            type: "Primary",
         },
      ],
   },
   published: "2023-11-20T09:15:07.180",
   references: [
      {
         source: "security@apache.org",
         tags: [
            "Mailing List",
         ],
         url: "https://lists.apache.org/thread/q23kvvtoohgzwybxpwozmvvk17rp0td3",
      },
      {
         source: "af854a3a-2127-422b-91ae-364da2661108",
         tags: [
            "Mailing List",
         ],
         url: "https://lists.apache.org/thread/q23kvvtoohgzwybxpwozmvvk17rp0td3",
      },
   ],
   sourceIdentifier: "security@apache.org",
   vulnStatus: "Modified",
   weaknesses: [
      {
         description: [
            {
               lang: "en",
               value: "CWE-74",
            },
         ],
         source: "nvd@nist.gov",
         type: "Primary",
      },
   ],
}


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.