GSD-2020-11052
Vulnerability from gsd - Updated: 2020-05-07 00:00Details
### Impact
Brute force vulnerability when using password authentication via Sorcery.
The brute force protection submodule will prevent a brute force attack for
the defined lockout period, but once expired protection will not be re-enabled
until a user or malicious actor logs in successfully. This does not affect users
that do not use the built-in brute force protection submodule, nor users that use
permanent account lockout.
### Patches
Patched as of version `0.15.0`.
### Workarounds
Currently no workarounds, other than monkey patching the authenticate method
provided by Sorcery or upgrading to version `0.15.0`.
Aliases
Aliases
{
"GSD": {
"alias": "CVE-2020-11052",
"description": "In Sorcery before 0.15.0, there is a brute force vulnerability when using password authentication via Sorcery. The brute force protection submodule will prevent a brute force attack for the defined lockout period, but once expired, protection will not be re-enabled until a user or malicious actor logs in successfully. This does not affect users that do not use the built-in brute force protection submodule, nor users that use permanent account lockout. This has been patched in 0.15.0.",
"id": "GSD-2020-11052"
},
"gsd": {
"metadata": {
"exploitCode": "unknown",
"remediation": "unknown",
"reportConfidence": "confirmed",
"type": "vulnerability"
},
"osvSchema": {
"affected": [
{
"package": {
"ecosystem": "RubyGems",
"name": "sorcery",
"purl": "pkg:gem/sorcery"
}
}
],
"aliases": [
"CVE-2020-11052",
"GHSA-jc8m-cxhj-668x"
],
"details": "### Impact\nBrute force vulnerability when using password authentication via Sorcery.\nThe brute force protection submodule will prevent a brute force attack for\nthe defined lockout period, but once expired protection will not be re-enabled\nuntil a user or malicious actor logs in successfully. This does not affect users\nthat do not use the built-in brute force protection submodule, nor users that use\npermanent account lockout.\n\n### Patches\nPatched as of version `0.15.0`.\n\n### Workarounds\nCurrently no workarounds, other than monkey patching the authenticate method\nprovided by Sorcery or upgrading to version `0.15.0`.",
"id": "GSD-2020-11052",
"modified": "2020-05-07T00:00:00.000Z",
"published": "2020-05-07T00:00:00.000Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/Sorcery/sorcery/security/advisories/GHSA-jc8m-cxhj-668x"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": 8.3,
"type": "CVSS_V3"
}
],
"summary": "Improper Restriction of Excessive Authentication Attempts in Sorcery"
}
},
"namespaces": {
"cve.org": {
"CVE_data_meta": {
"ASSIGNER": "security-advisories@github.com",
"ID": "CVE-2020-11052",
"STATE": "PUBLIC",
"TITLE": "Improper Restriction of Excessive Authentication Attempts in Sorcery"
},
"affects": {
"vendor": {
"vendor_data": [
{
"product": {
"product_data": [
{
"product_name": "Sorcery",
"version": {
"version_data": [
{
"version_value": "\u003c 0.15.0"
}
]
}
}
]
},
"vendor_name": "Sorcery"
}
]
}
},
"data_format": "MITRE",
"data_type": "CVE",
"data_version": "4.0",
"description": {
"description_data": [
{
"lang": "eng",
"value": "In Sorcery before 0.15.0, there is a brute force vulnerability when using password authentication via Sorcery. The brute force protection submodule will prevent a brute force attack for the defined lockout period, but once expired, protection will not be re-enabled until a user or malicious actor logs in successfully. This does not affect users that do not use the built-in brute force protection submodule, nor users that use permanent account lockout. This has been patched in 0.15.0."
}
]
},
"impact": {
"cvss": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "LOW",
"baseScore": 8.3,
"baseSeverity": "HIGH",
"confidentialityImpact": "LOW",
"integrityImpact": "LOW",
"privilegesRequired": "NONE",
"scope": "CHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L",
"version": "3.1"
}
},
"problemtype": {
"problemtype_data": [
{
"description": [
{
"lang": "eng",
"value": "CWE-307: Improper Restriction of Excessive Authentication Attempts"
}
]
}
]
},
"references": {
"reference_data": [
{
"name": "https://github.com/Sorcery/sorcery/security/advisories/GHSA-jc8m-cxhj-668x",
"refsource": "CONFIRM",
"url": "https://github.com/Sorcery/sorcery/security/advisories/GHSA-jc8m-cxhj-668x"
},
{
"name": "https://github.com/Sorcery/sorcery/issues/231",
"refsource": "MISC",
"url": "https://github.com/Sorcery/sorcery/issues/231"
},
{
"name": "https://github.com/Sorcery/sorcery/pull/235",
"refsource": "MISC",
"url": "https://github.com/Sorcery/sorcery/pull/235"
},
{
"name": "https://github.com/Sorcery/sorcery/commit/0f116d223826895a73b12492f17486e5d54ab7a7",
"refsource": "MISC",
"url": "https://github.com/Sorcery/sorcery/commit/0f116d223826895a73b12492f17486e5d54ab7a7"
}
]
},
"source": {
"advisory": "GHSA-jc8m-cxhj-668x",
"discovery": "UNKNOWN"
}
},
"github.com/rubysec/ruby-advisory-db": {
"cve": "2020-11052",
"cvss_v3": 8.3,
"date": "2020-05-07",
"description": "### Impact\nBrute force vulnerability when using password authentication via Sorcery.\nThe brute force protection submodule will prevent a brute force attack for\nthe defined lockout period, but once expired protection will not be re-enabled\nuntil a user or malicious actor logs in successfully. This does not affect users\nthat do not use the built-in brute force protection submodule, nor users that use\npermanent account lockout.\n\n### Patches\nPatched as of version `0.15.0`.\n\n### Workarounds\nCurrently no workarounds, other than monkey patching the authenticate method\nprovided by Sorcery or upgrading to version `0.15.0`.",
"gem": "sorcery",
"ghsa": "jc8m-cxhj-668x",
"patched_versions": [
"\u003e= 0.15.0"
],
"title": "Improper Restriction of Excessive Authentication Attempts in Sorcery",
"url": "https://github.com/Sorcery/sorcery/security/advisories/GHSA-jc8m-cxhj-668x"
},
"gitlab.com": {
"advisories": [
{
"affected_range": "\u003c0.15.0",
"affected_versions": "All versions before 0.15.0",
"cvss_v2": "AV:N/AC:L/Au:N/C:P/I:N/A:N",
"cvss_v3": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"cwe_ids": [
"CWE-1035",
"CWE-307",
"CWE-937"
],
"date": "2020-05-13",
"description": "In Sorcery, there is a brute force vulnerability when using password authentication via Sorcery. The brute force protection submodule will prevent a brute force attack for the defined lockout period, but once expired, protection will not be re-enabled until a user or malicious actor logs in successfully. This does not affect users that do not use the built-in brute force protection submodule, nor users that use permanent account lockout.",
"fixed_versions": [
"0.15.0"
],
"identifier": "CVE-2020-11052",
"identifiers": [
"CVE-2020-11052",
"GHSA-jc8m-cxhj-668x"
],
"not_impacted": "All versions starting from 0.15.0",
"package_slug": "gem/sorcery",
"pubdate": "2020-05-07",
"solution": "Upgrade to version 0.15.0 or above.",
"title": "Improper Restriction of Excessive Authentication Attempts",
"urls": [
"https://nvd.nist.gov/vuln/detail/CVE-2020-11052"
],
"uuid": "80dc73a5-6c4b-4060-b02e-546ba41e63f3"
}
]
},
"nvd.nist.gov": {
"configurations": {
"CVE_data_version": "4.0",
"nodes": [
{
"children": [],
"cpe_match": [
{
"cpe23Uri": "cpe:2.3:a:sorcery_project:sorcery:*:*:*:*:*:ruby:*:*",
"cpe_name": [],
"versionEndExcluding": "0.15.0",
"vulnerable": true
}
],
"operator": "OR"
}
]
},
"cve": {
"CVE_data_meta": {
"ASSIGNER": "security-advisories@github.com",
"ID": "CVE-2020-11052"
},
"data_format": "MITRE",
"data_type": "CVE",
"data_version": "4.0",
"description": {
"description_data": [
{
"lang": "en",
"value": "In Sorcery before 0.15.0, there is a brute force vulnerability when using password authentication via Sorcery. The brute force protection submodule will prevent a brute force attack for the defined lockout period, but once expired, protection will not be re-enabled until a user or malicious actor logs in successfully. This does not affect users that do not use the built-in brute force protection submodule, nor users that use permanent account lockout. This has been patched in 0.15.0."
}
]
},
"problemtype": {
"problemtype_data": [
{
"description": [
{
"lang": "en",
"value": "CWE-307"
}
]
}
]
},
"references": {
"reference_data": [
{
"name": "https://github.com/Sorcery/sorcery/security/advisories/GHSA-jc8m-cxhj-668x",
"refsource": "CONFIRM",
"tags": [
"Third Party Advisory"
],
"url": "https://github.com/Sorcery/sorcery/security/advisories/GHSA-jc8m-cxhj-668x"
},
{
"name": "https://github.com/Sorcery/sorcery/issues/231",
"refsource": "MISC",
"tags": [
"Third Party Advisory"
],
"url": "https://github.com/Sorcery/sorcery/issues/231"
},
{
"name": "https://github.com/Sorcery/sorcery/commit/0f116d223826895a73b12492f17486e5d54ab7a7",
"refsource": "MISC",
"tags": [
"Patch",
"Third Party Advisory"
],
"url": "https://github.com/Sorcery/sorcery/commit/0f116d223826895a73b12492f17486e5d54ab7a7"
},
{
"name": "https://github.com/Sorcery/sorcery/pull/235",
"refsource": "MISC",
"tags": [
"Patch",
"Third Party Advisory"
],
"url": "https://github.com/Sorcery/sorcery/pull/235"
}
]
}
},
"impact": {
"baseMetricV2": {
"acInsufInfo": false,
"cvssV2": {
"accessComplexity": "LOW",
"accessVector": "NETWORK",
"authentication": "NONE",
"availabilityImpact": "NONE",
"baseScore": 5.0,
"confidentialityImpact": "PARTIAL",
"integrityImpact": "NONE",
"vectorString": "AV:N/AC:L/Au:N/C:P/I:N/A:N",
"version": "2.0"
},
"exploitabilityScore": 10.0,
"impactScore": 2.9,
"obtainAllPrivilege": false,
"obtainOtherPrivilege": false,
"obtainUserPrivilege": false,
"severity": "MEDIUM",
"userInteractionRequired": false
},
"baseMetricV3": {
"cvssV3": {
"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
}
},
"lastModifiedDate": "2020-05-13T13:59Z",
"publishedDate": "2020-05-07T21:15Z"
}
}
}
Loading…
Loading…
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
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.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
Loading…
Loading…
The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the
vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base
model, served locally by ML-Gateway.
They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Loading…
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.