gsd-2022-46337
Vulnerability from gsd
Modified
2023-12-13 01:19
Details
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.
Aliases
Aliases
{ "GSD": { "alias": "CVE-2022-46337", "id": "GSD-2022-46337" }, "gsd": { "metadata": { "exploitCode": "unknown", "remediation": "unknown", "reportConfidence": "confirmed", "type": "vulnerability" }, "osvSchema": { "aliases": [ "CVE-2022-46337" ], "details": "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\u0027t 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", "id": "GSD-2022-46337", "modified": "2023-12-13T01:19:38.213103Z", "schema_version": "1.4.0" } }, "namespaces": { "cve.org": { "CVE_data_meta": { "ASSIGNER": "security@apache.org", "ID": "CVE-2022-46337", "STATE": "PUBLIC" }, "affects": { "vendor": { "vendor_data": [ { "product": { "product_data": [ { "product_name": "Apache Derby", "version": { "version_data": [ { "version_affected": "\u003c=", "version_name": "10.1.1.0", "version_value": "10.1.3.1" }, { "version_affected": "\u003c=", "version_name": "10.2.1.6", "version_value": "10.2.2.0" }, { "version_affected": "\u003c=", "version_name": "10.3.1.4", "version_value": "10.3.3.0" }, { "version_affected": "\u003c=", "version_name": "10.4.1.3", "version_value": "10.4.2.0" }, { "version_affected": "\u003c=", "version_name": "10.5.1.1", "version_value": "10.5.3.0" }, { "version_affected": "\u003c=", "version_name": "10.6.1.0", "version_value": "10.6.2.1" }, { "version_affected": "=", "version_value": "10.7.1.1" }, { "version_affected": "\u003c=", "version_name": "10.8.1.2", "version_value": "10.8.3.0" }, { "version_affected": "=", "version_value": "10.9.1.0" }, { "version_affected": "\u003c=", "version_name": "10.10.1.1", "version_value": "10.10.2.0" }, { "version_affected": "=", "version_value": "10.11.1.1" }, { "version_affected": "=", "version_value": "10.12.1.1" }, { "version_affected": "=", "version_value": "10.13.1.1" }, { "version_affected": "=", "version_value": "10.14.2.0" }, { "version_affected": "\u003c=", "version_name": "10.15.1.3", "version_value": "10.15.2.0" }, { "version_affected": "=", "version_value": "10.16.1.1" } ] } } ] }, "vendor_name": "Apache Software Foundation" } ] } }, "credits": [ { "lang": "en", "value": "This issue was discovered by \ufeff4ra1n and Y4tacker, who also proposed the fix." } ], "data_format": "MITRE", "data_type": "CVE", "data_version": "4.0", "description": { "description_data": [ { "lang": "eng", "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\u0027t 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" } ] }, "generator": { "engine": "Vulnogram 0.1.0-dev" }, "problemtype": { "problemtype_data": [ { "description": [ { "lang": "eng", "value": "LDAP Injection" } ] } ] }, "references": { "reference_data": [ { "name": "https://lists.apache.org/thread/q23kvvtoohgzwybxpwozmvvk17rp0td3", "refsource": "MISC", "url": "https://lists.apache.org/thread/q23kvvtoohgzwybxpwozmvvk17rp0td3" } ] }, "source": { "defect": [ "DERBY-7147" ], "discovery": "UNKNOWN" } }, "nvd.nist.gov": { "cve": { "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" } ] } ], "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\u0027t 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\u00f1ado podr\u00eda omitir las comprobaciones de autenticaci\u00f3n LDAP. En instalaciones Derby autenticadas por LDAP, esto podr\u00eda permitir que un atacante llene el disco creando bases de datos Derby basura. En instalaciones de Derby autenticadas por LDAP, esto tambi\u00e9n podr\u00eda permitir al atacante ejecutar malware que era visible y ejecutable por la cuenta que arranc\u00f3 el servidor Derby. En bases de datos protegidas por LDAP que tampoco estaban protegidas por la autorizaci\u00f3n SQL GRANT/REVOKE, esta vulnerabilidad tambi\u00e9n podr\u00eda permitir que un atacante vea y corrompa datos confidenciales y ejecute funciones y procedimientos de bases de datos confidenciales. Mitigaci\u00f3n: 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\u00f3n Derby a partir de una de las familias de versiones a las que se admiti\u00f3 la soluci\u00f3n: 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-04-26T16:08:12.950", "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" } ], "sourceIdentifier": "security@apache.org", "vulnStatus": "Analyzed", "weaknesses": [ { "description": [ { "lang": "en", "value": "CWE-74" } ], "source": "nvd@nist.gov", "type": "Primary" } ] } } } }
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.