cve-2021-33845
Vulnerability from cvelistv5
Published
2022-05-06 16:35
Modified
2024-08-04 00:05
Severity ?
EPSS score ?
Summary
Username enumeration through lockout message in REST API
References
Impacted products
Vendor | Product | Version | |
---|---|---|---|
▼ | Splunk | Splunk Enterprise |
Version: Version(s) before 8.1.7 |
|
{ "containers": { "adp": [ { "providerMetadata": { "dateUpdated": "2024-08-04T00:05:51.041Z", "orgId": "af854a3a-2127-422b-91ae-364da2661108", "shortName": "CVE" }, "references": [ { "tags": [ "x_refsource_MISC", "x_transferred" ], "url": "https://www.splunk.com/en_us/product-security/announcements/svd-2022-0502.html" }, { "tags": [ "x_refsource_MISC", "x_transferred" ], "url": "https://research.splunk.com/application/splunk_user_enumeration_attempt/" } ], "title": "CVE Program Container" } ], "cna": { "affected": [ { "product": "Splunk Enterprise", "vendor": "Splunk", "versions": [ { "status": "affected", "version": "Version(s) before 8.1.7" } ] } ], "credits": [ { "lang": "en", "value": "Kyle Bambrick" } ], "descriptions": [ { "lang": "en", "value": "The Splunk Enterprise REST API allows enumeration of usernames via the lockout error message. The potential vulnerability impacts Splunk Enterprise instances before 8.1.7 when configured to repress verbose login errors." } ], "metrics": [ { "cvssV3_1": { "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" } } ], "problemTypes": [ { "descriptions": [ { "cweId": "CWE-203", "description": "CWE-203", "lang": "en", "type": "CWE" } ] } ], "providerMetadata": { "dateUpdated": "2022-05-06T16:35:58", "orgId": "42b59230-ec95-491e-8425-5a5befa1a469", "shortName": "Splunk" }, "references": [ { "tags": [ "x_refsource_MISC" ], "url": "https://www.splunk.com/en_us/product-security/announcements/svd-2022-0502.html" }, { "tags": [ "x_refsource_MISC" ], "url": "https://research.splunk.com/application/splunk_user_enumeration_attempt/" } ], "source": { "advisory": "SVD-2022-0502", "discovery": "EXTERNAL" }, "title": "Username enumeration through lockout message in REST API", "x_generator": { "engine": "advisoriator" }, "x_legacyV4Record": { "CVE_data_meta": { "ASSIGNER": "prodsec@splunk.com", "ID": "CVE-2021-33845", "STATE": "PUBLIC", "TITLE": "Username enumeration through lockout message in REST API" }, "affects": { "vendor": { "vendor_data": [ { "product": { "product_data": [ { "product_name": "Splunk Enterprise", "version": { "version_data": [ { "version_value": "Version(s) before 8.1.7" } ] } } ] }, "vendor_name": "Splunk" } ] } }, "credit": [ { "lang": "eng", "value": "Kyle Bambrick" } ], "data_format": "MITRE", "data_type": "CVE", "data_version": "4.0", "description": { "description_data": [ { "lang": "eng", "value": "The Splunk Enterprise REST API allows enumeration of usernames via the lockout error message. The potential vulnerability impacts Splunk Enterprise instances before 8.1.7 when configured to repress verbose login errors." } ] }, "generator": { "engine": "advisoriator" }, "impact": { "cvss": { "baseScore": "5.3", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N", "version": "3.1" } }, "problemtype": { "problemtype_data": [ { "description": [ { "lang": "eng", "value": "CWE-203" } ] } ] }, "references": { "reference_data": [ { "name": "https://www.splunk.com/en_us/product-security/announcements/svd-2022-0502.html", "refsource": "MISC", "url": "https://www.splunk.com/en_us/product-security/announcements/svd-2022-0502.html" }, { "name": "https://research.splunk.com/application/splunk_user_enumeration_attempt/", "refsource": "MISC", "url": "https://research.splunk.com/application/splunk_user_enumeration_attempt/" } ] }, "source": { "advisory": "SVD-2022-0502", "discovery": "EXTERNAL" } } } }, "cveMetadata": { "assignerOrgId": "42b59230-ec95-491e-8425-5a5befa1a469", "assignerShortName": "Splunk", "cveId": "CVE-2021-33845", "datePublished": "2022-05-06T16:35:58", "dateReserved": "2021-11-03T00:00:00", "dateUpdated": "2024-08-04T00:05:51.041Z", "state": "PUBLISHED" }, "dataType": "CVE_RECORD", "dataVersion": "5.1", "meta": { "nvd": "{\"cve\":{\"id\":\"CVE-2021-33845\",\"sourceIdentifier\":\"prodsec@splunk.com\",\"published\":\"2022-05-06T17:15:08.577\",\"lastModified\":\"2024-11-21T06:09:41.023\",\"vulnStatus\":\"Modified\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"The Splunk Enterprise REST API allows enumeration of usernames via the lockout error message. The potential vulnerability impacts Splunk Enterprise instances before 8.1.7 when configured to repress verbose login errors.\"},{\"lang\":\"es\",\"value\":\"La API REST de Splunk Enterprise permite enumerar los nombres de usuario por medio del mensaje de error de bloqueo. La vulnerabilidad potencial afecta a las instancias de Splunk Enterprise anteriores a 8.1.7 cuando est\u00e1n configuradas para reprimir los errores de inicio de sesi\u00f3n verboso\"}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"prodsec@splunk.com\",\"type\":\"Secondary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N\",\"baseScore\":5.3,\"baseSeverity\":\"MEDIUM\",\"attackVector\":\"NETWORK\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"NONE\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"LOW\",\"integrityImpact\":\"NONE\",\"availabilityImpact\":\"NONE\"},\"exploitabilityScore\":3.9,\"impactScore\":1.4},{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N\",\"baseScore\":5.3,\"baseSeverity\":\"MEDIUM\",\"attackVector\":\"NETWORK\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"NONE\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"LOW\",\"integrityImpact\":\"NONE\",\"availabilityImpact\":\"NONE\"},\"exploitabilityScore\":3.9,\"impactScore\":1.4}],\"cvssMetricV2\":[{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"cvssData\":{\"version\":\"2.0\",\"vectorString\":\"AV:N/AC:L/Au:N/C:P/I:N/A:N\",\"baseScore\":5.0,\"accessVector\":\"NETWORK\",\"accessComplexity\":\"LOW\",\"authentication\":\"NONE\",\"confidentialityImpact\":\"PARTIAL\",\"integrityImpact\":\"NONE\",\"availabilityImpact\":\"NONE\"},\"baseSeverity\":\"MEDIUM\",\"exploitabilityScore\":10.0,\"impactScore\":2.9,\"acInsufInfo\":false,\"obtainAllPrivilege\":false,\"obtainUserPrivilege\":false,\"obtainOtherPrivilege\":false,\"userInteractionRequired\":false}]},\"weaknesses\":[{\"source\":\"prodsec@splunk.com\",\"type\":\"Secondary\",\"description\":[{\"lang\":\"en\",\"value\":\"CWE-203\"}]},{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"description\":[{\"lang\":\"en\",\"value\":\"CWE-203\"}]}],\"configurations\":[{\"nodes\":[{\"operator\":\"OR\",\"negate\":false,\"cpeMatch\":[{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:splunk:splunk:*:*:*:*:enterprise:*:*:*\",\"versionStartIncluding\":\"8.1.0\",\"versionEndExcluding\":\"8.1.7\",\"matchCriteriaId\":\"B4BE0BC2-6E5C-4A45-80BE-E2DB4C536AA2\"}]}]}],\"references\":[{\"url\":\"https://research.splunk.com/application/splunk_user_enumeration_attempt/\",\"source\":\"prodsec@splunk.com\",\"tags\":[\"Vendor Advisory\"]},{\"url\":\"https://www.splunk.com/en_us/product-security/announcements/svd-2022-0502.html\",\"source\":\"prodsec@splunk.com\",\"tags\":[\"Vendor Advisory\"]},{\"url\":\"https://research.splunk.com/application/splunk_user_enumeration_attempt/\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\",\"tags\":[\"Vendor Advisory\"]},{\"url\":\"https://www.splunk.com/en_us/product-security/announcements/svd-2022-0502.html\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\",\"tags\":[\"Vendor Advisory\"]}]}}" } }
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.