# Which version of elasticsearch solve the CVE-2022-1471(snakeyaml need bump to 2.0 version)

**URL:** <https://discuss.elastic.co/t/which-version-of-elasticsearch-solve-the-cve-2022-1471-snakeyaml-need-bump-to-2-0-version/355162>\
**Category:** Kibana\
**Created:** [March 11, 2024, 1:36pm UTC](https://discuss.elastic.co/t/which-version-of-elasticsearch-solve-the-cve-2022-1471-snakeyaml-need-bump-to-2-0-version/355162 "2024-03-11T13:36:16Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![DeBruyne2020](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/debruyne2020/32/132520_2.png) [@DeBruyne2020](https://discuss.elastic.co/u/DeBruyne2020)\
**Post date:** [March 11, 2024, 1:36pm UTC](https://discuss.elastic.co/t/which-version-of-elasticsearch-solve-the-cve-2022-1471-snakeyaml-need-bump-to-2-0-version/355162/1 "2024-03-11T13:36:16Z")

</div>

I have a question ：  
the elasticsearch that I use now( version 7.11.2) has CVE-2022-1471 (about snakeyaml), which version of elasticsearch solve this problem ? (As I know, snakeyaml need bump to 2.0 version which solve the CVE-2022-1471 ) ,

or can anybody provide some solution idea?

---

<div class="post-metadata">

**Author:** ![carly.richmond](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/carly.richmond/32/104935_2.png) [@carly.richmond](https://discuss.elastic.co/u/carly.richmond)\
**Post date:** [March 12, 2024, 10:12am UTC](https://discuss.elastic.co/t/which-version-of-elasticsearch-solve-the-cve-2022-1471-snakeyaml-need-bump-to-2-0-version/355162/2 "2024-03-12T10:12:03Z")

</div>

Hi @DeBruyne2020,

Welcome! I suggest looking at the [security announcement here for the details](https://discuss.elastic.co/t/elasticsearch-security-statement-regarding-cve-2022-1471/343006). It states that in general, Elasticsearch does not use Snakeyaml to parse YAML, but does note that it was removed as a direct dependency in v8.3.0 and the transitive dependency was upgraded to snakeyaml 2.0 in v8.8.0:

> In 8.3.0 and onwards, snakeyaml has been removed as a direct dependency in ["Remove direct snakeyaml dependency from launcher tools"](https://github.com/elastic/elasticsearch/pull/86248) and switched to using X-Content , which is backed by [jackson-dataformats-text](https://github.com/FasterXML/jackson-dataformats-text). Snakeyaml is bundled in Elasticsearch only as a transitive dependency of [jackson-dataformats-text](https://github.com/FasterXML/jackson-dataformats-text) but [jackson-dataformats-text](https://github.com/FasterXML/jackson-dataformats-text) does not use snakeyaml for YAML parsing either, but uses other parts of the library in a supportive fashion. The developers of [jackson-dataformats-text](https://github.com/FasterXML/jackson-dataformats-text) [**attest**](https://github.com/FasterXML/jackson-dataformats-text/issues/361) that their YAML parsing is not in any way affected by CVE-2022-1471.

> In 8.8.0 and onwards, this transitive snakeyaml dependency has nevertheless been upgraded to 2.0, as part of Elastic standard maintenance efforts.

Hope that helps!

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [April 9, 2024, 10:12am UTC](https://discuss.elastic.co/t/which-version-of-elasticsearch-solve-the-cve-2022-1471-snakeyaml-need-bump-to-2-0-version/355162/3 "2024-04-09T10:12:31Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.