mirror of
https://github.com/fkie-cad/nvd-json-data-feeds.git
synced 2025-05-28 17:21:36 +00:00
143 lines
8.2 KiB
JSON
143 lines
8.2 KiB
JSON
{
|
|
"id": "CVE-2021-21271",
|
|
"sourceIdentifier": "security-advisories@github.com",
|
|
"published": "2021-01-26T21:15:12.503",
|
|
"lastModified": "2021-02-08T21:23:08.820",
|
|
"vulnStatus": "Analyzed",
|
|
"cveTags": [],
|
|
"descriptions": [
|
|
{
|
|
"lang": "en",
|
|
"value": "Tendermint Core is an open source Byzantine Fault Tolerant (BFT) middleware that takes a state transition machine - written in any programming language - and securely replicates it on many machines. Tendermint Core v0.34.0 introduced a new way of handling evidence of misbehavior. As part of this, we added a new Timestamp field to Evidence structs. This timestamp would be calculated using the same algorithm that is used when a block is created and proposed. (This algorithm relies on the timestamp of the last commit from this specific block.) In Tendermint Core v0.34.0-v0.34.2, the consensus reactor is responsible for forming DuplicateVoteEvidence whenever double signs are observed. However, the current block is still \u201cin flight\u201d when it is being formed by the consensus reactor. It hasn\u2019t been finalized through network consensus yet. This means that different nodes in the network may observe different \u201clast commits\u201d when assigning a timestamp to DuplicateVoteEvidence. In turn, different nodes could form DuplicateVoteEvidence objects at the same height but with different timestamps. One DuplicateVoteEvidence object (with one timestamp) will then eventually get finalized in the block, but this means that any DuplicateVoteEvidence with a different timestamp is considered invalid. Any node that formed invalid DuplicateVoteEvidence will continue to propose invalid evidence; its peers may see this, and choose to disconnect from this node. This bug means that double signs are DoS vectors in Tendermint Core v0.34.0-v0.34.2. Tendermint Core v0.34.3 is a security release which fixes this bug. As of v0.34.3, DuplicateVoteEvidence is no longer formed by the consensus reactor; rather, the consensus reactor passes the Votes themselves into the EvidencePool, which is now responsible for forming DuplicateVoteEvidence. The EvidencePool has timestamp info that should be consistent across the network, which means that DuplicateVoteEvidence formed in this reactor should have consistent timestamps. This release changes the API between the consensus and evidence reactors."
|
|
},
|
|
{
|
|
"lang": "es",
|
|
"value": "Tendermint Core es un middleware Byzantine Fault Tolerant (BFT) de c\u00f3digo abierto que toma una m\u00e1quina de transici\u00f3n de estado, escrita en cualquier lenguaje de programaci\u00f3n, y la replica de forma segura en muchas m\u00e1quinas. Tendermint Core versi\u00f3n v0.34.0 introdujo una nueva forma de manejar la evidencia de mal comportamiento. Como parte de esto, agregamos un nuevo campo Timestamp a las estructuras Evidence. Esta marca de tiempo se calcular\u00eda usando el mismo algoritmo que se utiliza cuando un bloque sea creado y propuesto. (Este algoritmo se basa en la marca de tiempo del \u00faltimo commit de este bloque espec\u00edfico). En Tendermint Core versiones v0.34.0-v0.34.2, el reactor de consenso es responsable de formar un DuplicateVoteEvidence siempre que se observen signos dobles. Sin embargo, el bloque actual todav\u00eda est\u00e1 \"in flight\" cuando lo est\u00e1 formando el reactor de consenso. A\u00fan no se ha finalizado mediante el consenso de la red. Esto significa que diferentes nodos en la red pueden observar diferentes \"last commits\" al asignar una marca de tiempo a DuplicateVoteEvidence. A su vez, diferentes nodos podr\u00edan formar objetos DuplicateVoteEvidence a la misma altura pero con diferentes marcas de tiempo. Un objeto DuplicateVoteEvidence (con una marca de tiempo) finalmente se finalizar\u00e1 en el bloque, pero esto significa que cualquier DuplicateVoteEvidence con una marca de tiempo diferente se considera inv\u00e1lido. Cualquier nodo que form\u00f3 un DuplicateVoteEvidence inv\u00e1lido continuar\u00e1 proponiendo evidencia inv\u00e1lida; sus peers pueden visualizar esto y optar por desconectarse de este nodo. Este error significa que los signos dobles son vectores de DoS en Tendermint Core versiones v0.34.0-v0.34.2. Tendermint Core versi\u00f3n v0.34.3 es una versi\u00f3n de seguridad que corrige este error. A partir de la versi\u00f3n 0.34.3, DuplicateVoteEvidence ya no est\u00e1 formado por el reactor de consenso; m\u00e1s bien, el reactor de consenso pasa los Votos mismos al EvidencePool, que ahora es responsable de formar un DuplicateVoteEvidence. EvidencePool posee informaci\u00f3n de marca de tiempo que debe ser consistente en toda la red, lo que significa que un DuplicateVoteEvidence formado en este reactor debe tener marcas de tiempo consistentes. Esta versi\u00f3n cambia la API entre los reactores de consenso y evidencia"
|
|
}
|
|
],
|
|
"metrics": {
|
|
"cvssMetricV31": [
|
|
{
|
|
"source": "nvd@nist.gov",
|
|
"type": "Primary",
|
|
"cvssData": {
|
|
"version": "3.1",
|
|
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
|
|
"attackVector": "NETWORK",
|
|
"attackComplexity": "LOW",
|
|
"privilegesRequired": "LOW",
|
|
"userInteraction": "NONE",
|
|
"scope": "UNCHANGED",
|
|
"confidentialityImpact": "NONE",
|
|
"integrityImpact": "NONE",
|
|
"availabilityImpact": "HIGH",
|
|
"baseScore": 6.5,
|
|
"baseSeverity": "MEDIUM"
|
|
},
|
|
"exploitabilityScore": 2.8,
|
|
"impactScore": 3.6
|
|
},
|
|
{
|
|
"source": "security-advisories@github.com",
|
|
"type": "Secondary",
|
|
"cvssData": {
|
|
"version": "3.1",
|
|
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
|
|
"attackVector": "NETWORK",
|
|
"attackComplexity": "LOW",
|
|
"privilegesRequired": "LOW",
|
|
"userInteraction": "NONE",
|
|
"scope": "UNCHANGED",
|
|
"confidentialityImpact": "NONE",
|
|
"integrityImpact": "NONE",
|
|
"availabilityImpact": "HIGH",
|
|
"baseScore": 6.5,
|
|
"baseSeverity": "MEDIUM"
|
|
},
|
|
"exploitabilityScore": 2.8,
|
|
"impactScore": 3.6
|
|
}
|
|
],
|
|
"cvssMetricV2": [
|
|
{
|
|
"source": "nvd@nist.gov",
|
|
"type": "Primary",
|
|
"cvssData": {
|
|
"version": "2.0",
|
|
"vectorString": "AV:N/AC:L/Au:S/C:N/I:N/A:P",
|
|
"accessVector": "NETWORK",
|
|
"accessComplexity": "LOW",
|
|
"authentication": "SINGLE",
|
|
"confidentialityImpact": "NONE",
|
|
"integrityImpact": "NONE",
|
|
"availabilityImpact": "PARTIAL",
|
|
"baseScore": 4.0
|
|
},
|
|
"baseSeverity": "MEDIUM",
|
|
"exploitabilityScore": 8.0,
|
|
"impactScore": 2.9,
|
|
"acInsufInfo": false,
|
|
"obtainAllPrivilege": false,
|
|
"obtainUserPrivilege": false,
|
|
"obtainOtherPrivilege": false,
|
|
"userInteractionRequired": false
|
|
}
|
|
]
|
|
},
|
|
"weaknesses": [
|
|
{
|
|
"source": "security-advisories@github.com",
|
|
"type": "Primary",
|
|
"description": [
|
|
{
|
|
"lang": "en",
|
|
"value": "CWE-400"
|
|
}
|
|
]
|
|
}
|
|
],
|
|
"configurations": [
|
|
{
|
|
"nodes": [
|
|
{
|
|
"operator": "OR",
|
|
"negate": false,
|
|
"cpeMatch": [
|
|
{
|
|
"vulnerable": true,
|
|
"criteria": "cpe:2.3:a:tendermint:tendermint:*:*:*:*:*:*:*:*",
|
|
"versionStartIncluding": "0.34.0",
|
|
"versionEndIncluding": "0.34.2",
|
|
"matchCriteriaId": "E506A553-4EE9-4251-8C60-DF2EA5EB2E98"
|
|
}
|
|
]
|
|
}
|
|
]
|
|
}
|
|
],
|
|
"references": [
|
|
{
|
|
"url": "https://github.com/tendermint/tendermint/blob/v0.34.3/CHANGELOG.md#v0.34.3",
|
|
"source": "security-advisories@github.com",
|
|
"tags": [
|
|
"Release Notes",
|
|
"Third Party Advisory"
|
|
]
|
|
},
|
|
{
|
|
"url": "https://github.com/tendermint/tendermint/commit/a2a6852ab99e4a0f9e79f0ea8c1726e262e25c76",
|
|
"source": "security-advisories@github.com",
|
|
"tags": [
|
|
"Patch",
|
|
"Third Party Advisory"
|
|
]
|
|
},
|
|
{
|
|
"url": "https://github.com/tendermint/tendermint/security/advisories/GHSA-p658-8693-mhvg",
|
|
"source": "security-advisories@github.com",
|
|
"tags": [
|
|
"Third Party Advisory"
|
|
]
|
|
}
|
|
]
|
|
} |