기계 번역으로 제공되는 번역입니다. 제공된 번역과 원본 영어의 내용이 상충하는 경우에는 영어 버전이 우선합니다.
# Amazon EMR 7.x 릴리스 버전
이 섹션에는 각 Amazon EMR 7.x 릴리스 버전에 제공되는 애플리케이션 버전, 릴리스 정보, 구성 요소 버전 및 구성 분류가 포함되어 있습니다.
클러스터를 시작할 때 Amazon EMR의 여러 릴리스 중에서 선택할 수 있습니다. 이를 통해 호환성 요구 사항에 맞는 애플리케이션 버전을 테스트하고 사용할 수 있습니다. *릴리스 레이블*과 함께 릴리스 번호를 지정합니다. 릴리스 레이블은 `emr-x.x.x` 형식입니다. 예를 들어 `emr-7.12.0`입니다.
새 Amazon EMR 릴리스는 최초 릴리스 날짜에 첫 번째 리전부터 시작하여 일정 기간에 걸쳐 여러 리전에 사용 가능해집니다. 이 기간에는 사용자 리전에서 최신 릴리스 버전이 제공되지 않을 수도 있습니다.
모든 Amazon EMR 7.x 릴리스에서 애플리케이션 버전의 전체 테이블은 [Amazon EMR 7.x 릴리스의 애플리케이션 버전](emr-release-app-versions-7.x.md) 섹션을 참조하세요.
**Topics**
+ [Amazon EMR 7.x 릴리스의 애플리케이션 버전](emr-release-app-versions-7.x.md)
+ [Amazon EMR 릴리스 7.12.0](emr-7120-release.md)
+ [Amazon EMR 릴리스 7.11.0](emr-7110-release.md)
+ [Amazon EMR 릴리스 7.10.0](emr-7100-release.md)
+ [Amazon EMR 릴리스 7.9.0](emr-790-release.md)
+ [Amazon EMR 릴리스 7.8.0](emr-780-release.md)
+ [Amazon EMR 릴리스 7.7.0](emr-770-release.md)
+ [Amazon EMR 릴리스 7.6.0](emr-760-release.md)
+ [Amazon EMR 릴리스 7.5.0](emr-750-release.md)
+ [Amazon EMR 릴리스 7.4.0](emr-740-release.md)
+ [Amazon EMR 릴리스 7.3.0](emr-730-release.md)
+ [Amazon EMR 릴리스 7.2.0](emr-720-release.md)
+ [Amazon EMR 릴리스 7.1.0](emr-710-release.md)
+ [Amazon EMR 릴리스 7.0.0](emr-700-release.md)
# Amazon EMR 7.x 릴리스의 애플리케이션 버전
다음 테이블에는 각 Amazon EMR 7.x 릴리스에서 사용할 수 있는 애플리케이션 버전이 나와 있습니다.
**애플리케이션 버전 정보**
| | emr-7.12.0 | emr-7.11.0 | emr-7.10.0 | emr-7.9.0 | emr-7.8.0 | emr-7.7.0 | emr-7.6.0 | emr-7.5.0 | emr-7.4.0 | emr-7.3.0 | emr-7.2.0 | emr-7.1.0 | emr-7.0.0 |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| AWS Java용 SDK | 2.35.5, 1.12.792 | 2.35.5, 1.12.792 | 2.31.48, 1.12.782 | 2.31.16, 1.12.782 | 2.29.52, 1.12.780 | 2.29.44, 1.12.780 | 2.29.25, 1.12.779 | 2.28.8, 1.12.772 | 2.28.8, 1.12.772 | 2.25.70, 1.12.747 | 2.23.18, 1.12.705 | 2.23.18, 1.12.656 | 2.20.160-amzn-0, 1.12.569 |
| Python | 3.9, 3.11 | 3.9, 3.11 | 3.9, 3.11 | 3.9, 3.11 | 3.9, 3.11 | 3.9, 3.11 | 3.9, 3.11 | 3.9, 3.11 | 3.9, 3.11 | 3.9, 3.11 | 3.9, 3.11 | 3.9, 3.11 | 3.9 |
| Scala | 2.12.18 | 2.12.18 | 2.12.18 | 2.12.18 | 2.12.18 | 2.12.18 | 2.12.18 | 2.12.18 | 2.12.18 | 2.12.18 | 2.12.17 | 2.12.17 | 2.12.17 |
| AmazonCloudWatchAgent | 1.300032.2-amzn-0 | 1.300032.2-amzn-0 | 1.300032.2-amzn-0 | 1.300032.2-amzn-0 | 1.300032.2-amzn-0 | 1.300032.2-amzn-0 | 1.300032.2-amzn-0 | 1.300032.2-amzn-0 | 1.300032.2-amzn-0 | 1.300032.2-amzn-0 | 1.300032.2-amzn-0 | 1.300032.2-amzn-0 | 1.300031.1-amzn-0 |
| Delta | 3.3.2-amzn-1 | 3.3.2-amzn-0 | 3.3.0-amzn-2 | 3.3.0-amzn-1 | 3.3.0-amzn-0 | 3.2.1-amzn-2 | 3.2.1-amzn-1 | 3.2.1-amzn-0 | 3.2.0-amzn-1 | 3.2.0-amzn-0 | 3.1.0 | 3.0.0 | 3.0.0 |
| Flink | 1.20.0-amzn-6 | 1.20.0-amzn-5 | 1.20.0-amzn-4 | 1.20.0-amzn-3 | 1.20.0-amzn-2 | 1.20.0-amzn-1 | 1.20.0-amzn-0 | 1.19.1-amzn-1 | 1.19.1-amzn-0 | 1.18.1-amzn-2 | 1.18.1-amzn-1 | 1.18.1-amzn-0 | 1.18.0-amzn-0 |
| Ganglia | - | - | - | - | - | - | - | - | - | - | - | - | - |
| HBase | 2.6.2-amzn-3 | 2.6.2-amzn-2 | 2.6.2-amzn-1 | 2.6.2-amzn-0 | 2.6.1-amzn-2 | 2.6.1-amzn-1 | 2.6.1-amzn-0 | 2.5.10-amzn-0 | 2.5.5-amzn-0 | 2.4.17-amzn-7 | 2.4.17-amzn-6 | 2.4.17-amzn-5 | 2.4.17-amzn-4 |
| HCatalog | 3.1.3-amzn-21 | 3.1.3-amzn-20 | 3.1.3-amzn-19 | 3.1.3-amzn-18 | 3.1.3-amzn-17 | 3.1.3-amzn-16 | 3.1.3-amzn-15 | 3.1.3-amzn-14 | 3.1.3-amzn-13 | 3.1.3-amzn-12 | 3.1.3-amzn-11 | 3.1.3-amzn-10 | 3.1.3-amzn-9 |
| Hadoop | 3.4.1-amzn-4 | 3.4.1-amzn-3 | 3.4.1-amzn-2 | 3.4.1-amzn-1 | 3.4.1-amzn-0 | 3.4.0-amzn-3 | 3.4.0-amzn-2 | 3.4.0-amzn-1 | 3.4.0-amzn-0 | 3.3.6-amzn-5 | 3.3.6-amzn-4 | 3.3.6-amzn-3 | 3.3.6-amzn-2 |
| Hive | 3.1.3-amzn-21 | 3.1.3-amzn-20 | 3.1.3-amzn-19 | 3.1.3-amzn-18 | 3.1.3-amzn-17 | 3.1.3-amzn-16 | 3.1.3-amzn-15 | 3.1.3-amzn-14 | 3.1.3-amzn-13 | 3.1.3-amzn-12 | 3.1.3-amzn-11 | 3.1.3-amzn-10 | 3.1.3-amzn-9 |
| Hudi | 1.0.2-amzn-1 | 1.0.2-amzn-0 | 0.15.0-amzn-7 | 0.15.0-amzn-6 | 0.15.0-amzn-5 | 0.15.0-amzn-4 | 0.15.0-amzn-3 | 0.15.0-amzn-2 | 0.15.0-amzn-1 | 0.15.0-amzn-0 | 0.14.1-amzn-1 | 0.14.1-amzn-0 | 0.14.0-amzn-1 |
| Hue | 4.11.0 | 4.11.0 | 4.11.0 | 4.11.0 | 4.11.0 | 4.11.0 | 4.11.0 | 4.11.0 | 4.11.0 | 4.11.0 | 4.11.0 | 4.11.0 | 4.11.0 |
| Iceberg | 1.10.0-amzn-0 | 1.9.1-amzn-0 | 1.8.1-amzn-0 | 1.7.1-amzn-2 | 1.7.1-amzn-1 | 1.7.1-amzn-0 | 1.6.1-amzn-2 | 1.6.1-amzn-1 | 1.6.1-amzn-0 | 1.5.2-amzn-0 | 1.5.0-amzn-0 | 1.4.3-amzn-0 | 1.4.2-amzn-0 |
| JupyterEnterpriseGateway | 2.6.0 | 2.6.0 | 2.6.0 | 2.6.0 | 2.6.0 | 2.6.0 | 2.6.0 | 2.6.0 | 2.6.0 | 2.6.0 | 2.6.0 | 2.6.0 | 2.6.0 |
| JupyterHub | 1.5.0 | 1.5.0 | 1.5.0 | 1.5.0 | 1.5.0 | 1.5.0 | 1.5.0 | 1.5.0 | 1.5.0 | 1.5.0 | 1.5.0 | 1.5.0 | 1.5.0 |
| Livy | 0.8.0-incubating | 0.8.0-incubating | 0.8.0-incubating | 0.8.0-incubating | 0.8.0-incubating | 0.8.0-incubating | 0.8.0-incubating | 0.8.0-incubating | 0.8.0-incubating | 0.8.0-incubating | 0.8.0-incubating | 0.8.0-incubating | 0.7.1-incubating |
| MXNet | - | - | - | - | - | - | - | - | - | - | 1.9.1 | 1.9.1 | 1.9.1 |
| Mahout | - | - | - | - | - | - | - | - | - | - | - | - | - |
| Oozie | 5.2.1 | 5.2.1 | 5.2.1 | 5.2.1 | 5.2.1 | 5.2.1 | 5.2.1 | 5.2.1 | 5.2.1 | 5.2.1 | 5.2.1 | 5.2.1 | 5.2.1 |
| Phoenix | 5.2.1 | 5.2.1 | 5.2.1 | 5.2.1 | 5.2.1 | 5.2.1 | 5.2.0 | 5.2.0 | 5.2.0 | 5.1.3 | 5.1.3 | 5.1.3 | 5.1.3 |
| Pig | 0.17.0 | 0.17.0 | 0.17.0 | 0.17.0 | 0.17.0 | 0.17.0 | 0.17.0 | 0.17.0 | 0.17.0 | 0.17.0 | 0.17.0 | 0.17.0 | 0.17.0 |
| Presto | 0.287-amzn-6 | 0.287-amzn-5 | 0.287-amzn-4 | 0.287-amzn-3 | 0.287-amzn-2 | 0.287-amzn-1 | 0.287-amzn-1 | 0.287-amzn-0 | 0.287-amzn-0 | 0.285-amzn-1 | 0.285-amzn-0 | 0.284-amzn-0 | 0.283-amzn-1 |
| Spark | 3.5.6-amzn-1 | 3.5.6-amzn-0 | 3.5.5-amzn-1 | 3.5.5-amzn-0 | 3.5.4-amzn-0 | 3.5.3-amzn-1 | 3.5.3-amzn-0 | 3.5.2-amzn-1 | 3.5.2-amzn-0 | 3.5.1-amzn-1 | 3.5.1-amzn-0 | 3.5.0-amzn-1 | 3.5.0-amzn-0 |
| Sqoop | - | - | - | - | - | - | - | - | 1.4.7 | 1.4.7 | 1.4.7 | 1.4.7 | 1.4.7 |
| TensorFlow | 2.19.0 | 2.19.0 | 2.18.0 | 2.16.1 | 2.16.1 | 2.16.1 | 2.16.1 | 2.16.1 | 2.16.1 | 2.16.1 | 2.11.0 | 2.11.0 | 2.11.0 |
| Tez | 0.10.2-amzn-19 | 0.10.2-amzn-18 | 0.10.2-amzn-17 | 0.10.2-amzn-16 | 0.10.2-amzn-15 | 0.10.2-amzn-14 | 0.10.2-amzn-13 | 0.10.2-amzn-12 | 0.10.2-amzn-11 | 0.10.2-amzn-10 | 0.10.2-amzn-9 | 0.10.2-amzn-8 | 0.10.2-amzn-7 |
| Trino (PrestoSQL) | 476-amzn-1 | 475-amzn-0 | 470-amzn-0 | 467-amzn-2 | 467-amzn-1 | 467-amzn-0 | 457-amzn-0 | 446-amzn-0 | 446-amzn-0 | 442-amzn-0 | 436-amzn-0 | 435-amzn-0 | 426-amzn-1 |
| Zeppelin | 0.11.1 | 0.11.1 | 0.11.1 | 0.11.1 | 0.11.1 | 0.11.1 | 0.11.1 | 0.11.1 | 0.11.1 | 0.11.1 | 0.10.1 | 0.10.1 | 0.10.1 |
| ZooKeeper | 3.9.3-amzn-4 | 3.9.3-amzn-3 | 3.9.3-amzn-2 | 3.9.3-amzn-1 | 3.9.3-amzn-0 | 3.9.2-amzn-1 | 3.9.2-amzn-0 | 3.9.2-amzn-0 | 3.9.2-amzn-0 | 3.9.1-amzn-1 | 3.9.1-amzn-1 | 3.9.1-amzn-0 | 3.5.10 |
# Amazon EMR 릴리스 7.12.0
## 7.12.0 지원 수명 주기
다음 표에서는 Amazon EMR 릴리스 7.12.0에 지원되는 수명 주기 날짜를 설명합니다.
| 지원 단계 | Date |
| --- | --- |
| 초기 릴리스 날짜 | 2025년 11월 21일 |
| 표준 지원 종료 시점 | 2027년 11월 21일 |
| 지원 종료 | 2027년 11월 22일 |
| 수명 종료 | 2028년 11월 21일 |
## 7.12.0 애플리케이션 버전
이 릴리스에 포함된 애플리케이션은 [https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Install-CloudWatch-Agent.html](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Install-CloudWatch-Agent.html), [https://delta.io/](https://delta.io/), [https://flink.apache.org/](https://flink.apache.org/), [http://hbase.apache.org/](http://hbase.apache.org/), [https://cwiki.apache.org/confluence/display/Hive/HCatalog](https://cwiki.apache.org/confluence/display/Hive/HCatalog), [http://hadoop.apache.org/docs/current/](http://hadoop.apache.org/docs/current/), [http://hive.apache.org/](http://hive.apache.org/), [https://hudi.apache.org](https://hudi.apache.org), [http://gethue.com/](http://gethue.com/), [https://iceberg.apache.org/](https://iceberg.apache.org/), [https://jupyter-enterprise-gateway.readthedocs.io/en/latest/](https://jupyter-enterprise-gateway.readthedocs.io/en/latest/), [https://jupyterhub.readthedocs.io/en/latest/#](https://jupyterhub.readthedocs.io/en/latest/#), [https://livy.incubator.apache.org/](https://livy.incubator.apache.org/), [http://oozie.apache.org/](http://oozie.apache.org/), [https://phoenix.apache.org/](https://phoenix.apache.org/), [http://pig.apache.org/](http://pig.apache.org/), [https://prestodb.io/](https://prestodb.io/), [https://spark.apache.org/docs/latest/](https://spark.apache.org/docs/latest/), [https://www.tensorflow.org/](https://www.tensorflow.org/), [https://tez.apache.org/](https://tez.apache.org/), [https://trino.io/](https://trino.io/), [https://zeppelin.incubator.apache.org/](https://zeppelin.incubator.apache.org/), [https://zookeeper.apache.org](https://zookeeper.apache.org)입니다.
아래 테이블에는 이번 Amazon EMR 릴리스에서 사용할 수 있는 애플리케이션 버전과 이전 세 가지 Amazon EMR 릴리스(해당하는 경우)의 애플리케이션 버전이 나와 있습니다.
각 Amazon EMR 릴리스에서 애플리케이션 버전의 전체 기록은 다음 주제를 참조하세요.
+ [Amazon EMR 7.x 릴리스의 애플리케이션 버전](emr-release-app-versions-7.x.md)
+ [Amazon EMR 6.x 릴리스의 애플리케이션 버전](emr-release-app-versions-6.x.md)
+ [Amazon EMR 5.x 릴리스의 애플리케이션 버전](emr-release-app-versions-5.x.md)
+ [Amazon EMR 4.x 릴리스의 애플리케이션 버전](emr-release-app-versions-4.x.md)
**애플리케이션 버전 정보**
| | emr-7.12.0 | emr-7.11.0 | emr-7.10.0 | emr-7.9.0 |
| --- | --- | --- | --- | --- |
| AWS Java용 SDK | 2.35.5, 1.12.792 | 2.35.5, 1.12.792 | 2.31.48, 1.12.782 | 2.31.16, 1.12.782 |
| Python | 3.9, 3.11 | 3.9, 3.11 | 3.9, 3.11 | 3.9, 3.11 |
| Scala | 2.12.18 | 2.12.18 | 2.12.18 | 2.12.18 |
| AmazonCloudWatchAgent | 1.300032.2-amzn-0 | 1.300032.2-amzn-0 | 1.300032.2-amzn-0 | 1.300032.2-amzn-0 |
| Delta | 3.3.2-amzn-1 | 3.3.2-amzn-0 | 3.3.0-amzn-2 | 3.3.0-amzn-1 |
| Flink | 1.20.0-amzn-6 | 1.20.0-amzn-5 | 1.20.0-amzn-4 | 1.20.0-amzn-3 |
| Ganglia | - | - | - | - |
| HBase | 2.6.2-amzn-3 | 2.6.2-amzn-2 | 2.6.2-amzn-1 | 2.6.2-amzn-0 |
| HCatalog | 3.1.3-amzn-21 | 3.1.3-amzn-20 | 3.1.3-amzn-19 | 3.1.3-amzn-18 |
| Hadoop | 3.4.1-amzn-4 | 3.4.1-amzn-3 | 3.4.1-amzn-2 | 3.4.1-amzn-1 |
| Hive | 3.1.3-amzn-21 | 3.1.3-amzn-20 | 3.1.3-amzn-19 | 3.1.3-amzn-18 |
| Hudi | 1.0.2-amzn-1 | 1.0.2-amzn-0 | 0.15.0-amzn-7 | 0.15.0-amzn-6 |
| Hue | 4.11.0 | 4.11.0 | 4.11.0 | 4.11.0 |
| Iceberg | 1.10.0-amzn-0 | 1.9.1-amzn-0 | 1.8.1-amzn-0 | 1.7.1-amzn-2 |
| JupyterEnterpriseGateway | 2.6.0 | 2.6.0 | 2.6.0 | 2.6.0 |
| JupyterHub | 1.5.0 | 1.5.0 | 1.5.0 | 1.5.0 |
| Livy | 0.8.0-incubating | 0.8.0-incubating | 0.8.0-incubating | 0.8.0-incubating |
| MXNet | - | - | - | - |
| Mahout | - | - | - | - |
| Oozie | 5.2.1 | 5.2.1 | 5.2.1 | 5.2.1 |
| Phoenix | 5.2.1 | 5.2.1 | 5.2.1 | 5.2.1 |
| Pig | 0.17.0 | 0.17.0 | 0.17.0 | 0.17.0 |
| Presto | 0.287-amzn-6 | 0.287-amzn-5 | 0.287-amzn-4 | 0.287-amzn-3 |
| Spark | 3.5.6-amzn-1 | 3.5.6-amzn-0 | 3.5.5-amzn-1 | 3.5.5-amzn-0 |
| Sqoop | - | - | - | - |
| TensorFlow | 2.19.0 | 2.19.0 | 2.18.0 | 2.16.1 |
| Tez | 0.10.2-amzn-19 | 0.10.2-amzn-18 | 0.10.2-amzn-17 | 0.10.2-amzn-16 |
| Trino (PrestoSQL) | 476-amzn-1 | 475-amzn-0 | 470-amzn-0 | 467-amzn-2 |
| Zeppelin | 0.11.1 | 0.11.1 | 0.11.1 | 0.11.1 |
| ZooKeeper | 3.9.3-amzn-4 | 3.9.3-amzn-3 | 3.9.3-amzn-2 | 3.9.3-amzn-1 |
# 7.12.0 일반적인 취약성 및 노출
다음 표에는 Amazon EMR 7.12.0의 권장 구성에서 실행되는 EMR 클러스터에 영향을 주지 않는 모든 CVEs가 나열되어 있습니다. Amazon EMR은 업스트림 오픈 소스의 수정 사항 가용성에 종속되어 있으며, Amazon EMR이 수정 사항을 확인한 후 90일 이내에 코어 엔진 구성 요소의 일부로 안정적인 최신 버전을 제공합니다.
이 표는 2025년 11월 13일에 업데이트되었습니다.
| CVE ID | 심각도 | CVE 세부 정보 URL |
| --- | --- | --- |
| CVE-2015-1832 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2015-1832](https://nvd.nist.gov/vuln/detail/CVE-2015-1832) |
| CVE-2016-5018 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2016-5018](https://nvd.nist.gov/vuln/detail/CVE-2016-5018) |
| CVE-2017-15095 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2017-15095](https://nvd.nist.gov/vuln/detail/CVE-2017-15095) |
| CVE-2017-17485 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2017-17485](https://nvd.nist.gov/vuln/detail/CVE-2017-17485) |
| CVE-2017-7525 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2017-7525](https://nvd.nist.gov/vuln/detail/CVE-2017-7525) |
| CVE-2018-11307 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-11307](https://nvd.nist.gov/vuln/detail/CVE-2018-11307) |
| CVE-2018-11307 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-11307](https://nvd.nist.gov/vuln/detail/CVE-2018-11307) |
| CVE-2018-14718 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-14718](https://nvd.nist.gov/vuln/detail/CVE-2018-14718) |
| CVE-2018-14718 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-14718](https://nvd.nist.gov/vuln/detail/CVE-2018-14718) |
| CVE-2018-14719 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-14719](https://nvd.nist.gov/vuln/detail/CVE-2018-14719) |
| CVE-2018-14719 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-14719](https://nvd.nist.gov/vuln/detail/CVE-2018-14719) |
| CVE-2018-14720 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-14720](https://nvd.nist.gov/vuln/detail/CVE-2018-14720) |
| CVE-2018-14720 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-14720](https://nvd.nist.gov/vuln/detail/CVE-2018-14720) |
| CVE-2018-14721 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-14721](https://nvd.nist.gov/vuln/detail/CVE-2018-14721) |
| CVE-2018-14721 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-14721](https://nvd.nist.gov/vuln/detail/CVE-2018-14721) |
| CVE-2018-19360 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-19360](https://nvd.nist.gov/vuln/detail/CVE-2018-19360) |
| CVE-2018-19360 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-19360](https://nvd.nist.gov/vuln/detail/CVE-2018-19360) |
| CVE-2018-19361 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-19361](https://nvd.nist.gov/vuln/detail/CVE-2018-19361) |
| CVE-2018-19361 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-19361](https://nvd.nist.gov/vuln/detail/CVE-2018-19361) |
| CVE-2018-19362 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-19362](https://nvd.nist.gov/vuln/detail/CVE-2018-19362) |
| CVE-2018-19362 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-19362](https://nvd.nist.gov/vuln/detail/CVE-2018-19362) |
| CVE-2018-7489 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-7489](https://nvd.nist.gov/vuln/detail/CVE-2018-7489) |
| CVE-2018-7489 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-7489](https://nvd.nist.gov/vuln/detail/CVE-2018-7489) |
| CVE-2019-10202 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-10202](https://nvd.nist.gov/vuln/detail/CVE-2019-10202) |
| CVE-2019-14379 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14379](https://nvd.nist.gov/vuln/detail/CVE-2019-14379) |
| CVE-2019-14379 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14379](https://nvd.nist.gov/vuln/detail/CVE-2019-14379) |
| CVE-2019-14540 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14540](https://nvd.nist.gov/vuln/detail/CVE-2019-14540) |
| CVE-2019-14540 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14540](https://nvd.nist.gov/vuln/detail/CVE-2019-14540) |
| CVE-2019-14892 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14892](https://nvd.nist.gov/vuln/detail/CVE-2019-14892) |
| CVE-2019-14892 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14892](https://nvd.nist.gov/vuln/detail/CVE-2019-14892) |
| CVE-2019-14893 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14893](https://nvd.nist.gov/vuln/detail/CVE-2019-14893) |
| CVE-2019-14893 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14893](https://nvd.nist.gov/vuln/detail/CVE-2019-14893) |
| CVE-2019-16335 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-16335](https://nvd.nist.gov/vuln/detail/CVE-2019-16335) |
| CVE-2019-16335 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-16335](https://nvd.nist.gov/vuln/detail/CVE-2019-16335) |
| CVE-2019-16942 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-16942](https://nvd.nist.gov/vuln/detail/CVE-2019-16942) |
| CVE-2019-16942 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-16942](https://nvd.nist.gov/vuln/detail/CVE-2019-16942) |
| CVE-2019-16943 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-16943](https://nvd.nist.gov/vuln/detail/CVE-2019-16943) |
| CVE-2019-16943 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-16943](https://nvd.nist.gov/vuln/detail/CVE-2019-16943) |
| CVE-2019-17267 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-17267](https://nvd.nist.gov/vuln/detail/CVE-2019-17267) |
| CVE-2019-17267 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-17267](https://nvd.nist.gov/vuln/detail/CVE-2019-17267) |
| CVE-2019-17531 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-17531](https://nvd.nist.gov/vuln/detail/CVE-2019-17531) |
| CVE-2019-17531 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-17531](https://nvd.nist.gov/vuln/detail/CVE-2019-17531) |
| CVE-2019-20330 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-20330](https://nvd.nist.gov/vuln/detail/CVE-2019-20330) |
| CVE-2019-20330 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-20330](https://nvd.nist.gov/vuln/detail/CVE-2019-20330) |
| CVE-2020-8840 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8840](https://nvd.nist.gov/vuln/detail/CVE-2020-8840) |
| CVE-2020-8840 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8840](https://nvd.nist.gov/vuln/detail/CVE-2020-8840) |
| CVE-2020-9546 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-9546](https://nvd.nist.gov/vuln/detail/CVE-2020-9546) |
| CVE-2020-9546 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-9546](https://nvd.nist.gov/vuln/detail/CVE-2020-9546) |
| CVE-2020-9547 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-9547](https://nvd.nist.gov/vuln/detail/CVE-2020-9547) |
| CVE-2020-9547 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-9547](https://nvd.nist.gov/vuln/detail/CVE-2020-9547) |
| CVE-2020-9548 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-9548](https://nvd.nist.gov/vuln/detail/CVE-2020-9548) |
| CVE-2020-9548 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-9548](https://nvd.nist.gov/vuln/detail/CVE-2020-9548) |
| CVE-2022-1471 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-1471](https://nvd.nist.gov/vuln/detail/CVE-2022-1471) |
| CVE-2022-1471 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-1471](https://nvd.nist.gov/vuln/detail/CVE-2022-1471) |
| CVE-2022-37865 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-37865](https://nvd.nist.gov/vuln/detail/CVE-2022-37865) |
| CVE-2022-39135 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-39135](https://nvd.nist.gov/vuln/detail/CVE-2022-39135) |
| CVE-2022-46337 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-46337](https://nvd.nist.gov/vuln/detail/CVE-2022-46337) |
| CVE-2022-46337 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-46337](https://nvd.nist.gov/vuln/detail/CVE-2022-46337) |
| CVE-2024-51504 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2024-51504](https://nvd.nist.gov/vuln/detail/CVE-2024-51504) |
| CVE-2024-51504 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2024-51504](https://nvd.nist.gov/vuln/detail/CVE-2024-51504) |
| CVE-2024-52046 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2024-52046](https://nvd.nist.gov/vuln/detail/CVE-2024-52046) |
| CVE-2024-52046 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2024-52046](https://nvd.nist.gov/vuln/detail/CVE-2024-52046) |
| CVE-2024-53990 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2024-53990](https://nvd.nist.gov/vuln/detail/CVE-2024-53990) |
| CVE-2025-30065 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2025-30065](https://nvd.nist.gov/vuln/detail/CVE-2025-30065) |
| CVE-2025-30065 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2025-30065](https://nvd.nist.gov/vuln/detail/CVE-2025-30065) |
| CVE-2014-3643 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2014-3643](https://nvd.nist.gov/vuln/detail/CVE-2014-3643) |
| CVE-2015-5237 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2015-5237](https://nvd.nist.gov/vuln/detail/CVE-2015-5237) |
| CVE-2015-5237 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2015-5237](https://nvd.nist.gov/vuln/detail/CVE-2015-5237) |
| CVE-2016-6796 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2016-6796](https://nvd.nist.gov/vuln/detail/CVE-2016-6796) |
| CVE-2018-1000180 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-1000180](https://nvd.nist.gov/vuln/detail/CVE-2018-1000180) |
| CVE-2018-1000180 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-1000180](https://nvd.nist.gov/vuln/detail/CVE-2018-1000180) |
| CVE-2018-12022 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-12022](https://nvd.nist.gov/vuln/detail/CVE-2018-12022) |
| CVE-2018-12022 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-12022](https://nvd.nist.gov/vuln/detail/CVE-2018-12022) |
| CVE-2018-12023 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-12023](https://nvd.nist.gov/vuln/detail/CVE-2018-12023) |
| CVE-2018-12023 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-12023](https://nvd.nist.gov/vuln/detail/CVE-2018-12023) |
| CVE-2018-5968 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-5968](https://nvd.nist.gov/vuln/detail/CVE-2018-5968) |
| CVE-2019-0205 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-0205](https://nvd.nist.gov/vuln/detail/CVE-2019-0205) |
| CVE-2019-0205 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-0205](https://nvd.nist.gov/vuln/detail/CVE-2019-0205) |
| CVE-2019-10172 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-10172](https://nvd.nist.gov/vuln/detail/CVE-2019-10172) |
| CVE-2019-12086 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-12086](https://nvd.nist.gov/vuln/detail/CVE-2019-12086) |
| CVE-2019-12086 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-12086](https://nvd.nist.gov/vuln/detail/CVE-2019-12086) |
| CVE-2019-14439 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14439](https://nvd.nist.gov/vuln/detail/CVE-2019-14439) |
| CVE-2019-14439 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14439](https://nvd.nist.gov/vuln/detail/CVE-2019-14439) |
| CVE-2020-10650 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10650](https://nvd.nist.gov/vuln/detail/CVE-2020-10650) |
| CVE-2020-10650 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10650](https://nvd.nist.gov/vuln/detail/CVE-2020-10650) |
| CVE-2020-10672 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10672](https://nvd.nist.gov/vuln/detail/CVE-2020-10672) |
| CVE-2020-10672 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10672](https://nvd.nist.gov/vuln/detail/CVE-2020-10672) |
| CVE-2020-10673 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10673](https://nvd.nist.gov/vuln/detail/CVE-2020-10673) |
| CVE-2020-10673 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10673](https://nvd.nist.gov/vuln/detail/CVE-2020-10673) |
| CVE-2020-10968 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10968](https://nvd.nist.gov/vuln/detail/CVE-2020-10968) |
| CVE-2020-10968 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10968](https://nvd.nist.gov/vuln/detail/CVE-2020-10968) |
| CVE-2020-10969 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10969](https://nvd.nist.gov/vuln/detail/CVE-2020-10969) |
| CVE-2020-10969 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10969](https://nvd.nist.gov/vuln/detail/CVE-2020-10969) |
| CVE-2020-11111 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11111](https://nvd.nist.gov/vuln/detail/CVE-2020-11111) |
| CVE-2020-11111 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11111](https://nvd.nist.gov/vuln/detail/CVE-2020-11111) |
| CVE-2020-11112 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11112](https://nvd.nist.gov/vuln/detail/CVE-2020-11112) |
| CVE-2020-11112 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11112](https://nvd.nist.gov/vuln/detail/CVE-2020-11112) |
| CVE-2020-11113 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11113](https://nvd.nist.gov/vuln/detail/CVE-2020-11113) |
| CVE-2020-11113 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11113](https://nvd.nist.gov/vuln/detail/CVE-2020-11113) |
| CVE-2020-11619 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11619](https://nvd.nist.gov/vuln/detail/CVE-2020-11619) |
| CVE-2020-11619 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11619](https://nvd.nist.gov/vuln/detail/CVE-2020-11619) |
| CVE-2020-11620 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11620](https://nvd.nist.gov/vuln/detail/CVE-2020-11620) |
| CVE-2020-11620 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11620](https://nvd.nist.gov/vuln/detail/CVE-2020-11620) |
| CVE-2020-13949 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-13949](https://nvd.nist.gov/vuln/detail/CVE-2020-13949) |
| CVE-2020-13949 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-13949](https://nvd.nist.gov/vuln/detail/CVE-2020-13949) |
| CVE-2020-13949 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-13949](https://nvd.nist.gov/vuln/detail/CVE-2020-13949) |
| CVE-2020-14060 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14060](https://nvd.nist.gov/vuln/detail/CVE-2020-14060) |
| CVE-2020-14060 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14060](https://nvd.nist.gov/vuln/detail/CVE-2020-14060) |
| CVE-2020-14061 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14061](https://nvd.nist.gov/vuln/detail/CVE-2020-14061) |
| CVE-2020-14061 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14061](https://nvd.nist.gov/vuln/detail/CVE-2020-14061) |
| CVE-2020-14062 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14062](https://nvd.nist.gov/vuln/detail/CVE-2020-14062) |
| CVE-2020-14062 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14062](https://nvd.nist.gov/vuln/detail/CVE-2020-14062) |
| CVE-2020-14195 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14195](https://nvd.nist.gov/vuln/detail/CVE-2020-14195) |
| CVE-2020-14195 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14195](https://nvd.nist.gov/vuln/detail/CVE-2020-14195) |
| CVE-2020-24616 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-24616](https://nvd.nist.gov/vuln/detail/CVE-2020-24616) |
| CVE-2020-24616 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-24616](https://nvd.nist.gov/vuln/detail/CVE-2020-24616) |
| CVE-2020-24750 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-24750](https://nvd.nist.gov/vuln/detail/CVE-2020-24750) |
| CVE-2020-24750 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-24750](https://nvd.nist.gov/vuln/detail/CVE-2020-24750) |
| CVE-2020-25649 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-25649](https://nvd.nist.gov/vuln/detail/CVE-2020-25649) |
| CVE-2020-28052 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-28052](https://nvd.nist.gov/vuln/detail/CVE-2020-28052) |
| CVE-2020-35490 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-35490](https://nvd.nist.gov/vuln/detail/CVE-2020-35490) |
| CVE-2020-35490 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-35490](https://nvd.nist.gov/vuln/detail/CVE-2020-35490) |
| CVE-2020-35491 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-35491](https://nvd.nist.gov/vuln/detail/CVE-2020-35491) |
| CVE-2020-35491 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-35491](https://nvd.nist.gov/vuln/detail/CVE-2020-35491) |
| CVE-2020-35728 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-35728](https://nvd.nist.gov/vuln/detail/CVE-2020-35728) |
| CVE-2020-35728 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-35728](https://nvd.nist.gov/vuln/detail/CVE-2020-35728) |
| CVE-2020-36179 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36179](https://nvd.nist.gov/vuln/detail/CVE-2020-36179) |
| CVE-2020-36179 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36179](https://nvd.nist.gov/vuln/detail/CVE-2020-36179) |
| CVE-2020-36180 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36180](https://nvd.nist.gov/vuln/detail/CVE-2020-36180) |
| CVE-2020-36180 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36180](https://nvd.nist.gov/vuln/detail/CVE-2020-36180) |
| CVE-2020-36181 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36181](https://nvd.nist.gov/vuln/detail/CVE-2020-36181) |
| CVE-2020-36181 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36181](https://nvd.nist.gov/vuln/detail/CVE-2020-36181) |
| CVE-2020-36182 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36182](https://nvd.nist.gov/vuln/detail/CVE-2020-36182) |
| CVE-2020-36182 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36182](https://nvd.nist.gov/vuln/detail/CVE-2020-36182) |
| CVE-2020-36183 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36183](https://nvd.nist.gov/vuln/detail/CVE-2020-36183) |
| CVE-2020-36183 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36183](https://nvd.nist.gov/vuln/detail/CVE-2020-36183) |
| CVE-2020-36184 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36184](https://nvd.nist.gov/vuln/detail/CVE-2020-36184) |
| CVE-2020-36184 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36184](https://nvd.nist.gov/vuln/detail/CVE-2020-36184) |
| CVE-2020-36185 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36185](https://nvd.nist.gov/vuln/detail/CVE-2020-36185) |
| CVE-2020-36185 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36185](https://nvd.nist.gov/vuln/detail/CVE-2020-36185) |
| CVE-2020-36186 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36186](https://nvd.nist.gov/vuln/detail/CVE-2020-36186) |
| CVE-2020-36186 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36186](https://nvd.nist.gov/vuln/detail/CVE-2020-36186) |
| CVE-2020-36187 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36187](https://nvd.nist.gov/vuln/detail/CVE-2020-36187) |
| CVE-2020-36187 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36187](https://nvd.nist.gov/vuln/detail/CVE-2020-36187) |
| CVE-2020-36188 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36188](https://nvd.nist.gov/vuln/detail/CVE-2020-36188) |
| CVE-2020-36188 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36188](https://nvd.nist.gov/vuln/detail/CVE-2020-36188) |
| CVE-2020-36189 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36189](https://nvd.nist.gov/vuln/detail/CVE-2020-36189) |
| CVE-2020-36189 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36189](https://nvd.nist.gov/vuln/detail/CVE-2020-36189) |
| CVE-2020-36518 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36518](https://nvd.nist.gov/vuln/detail/CVE-2020-36518) |
| CVE-2020-36518 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36518](https://nvd.nist.gov/vuln/detail/CVE-2020-36518) |
| CVE-2021-0341 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-0341](https://nvd.nist.gov/vuln/detail/CVE-2021-0341) |
| CVE-2021-20190 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-20190](https://nvd.nist.gov/vuln/detail/CVE-2021-20190) |
| CVE-2021-20190 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-20190](https://nvd.nist.gov/vuln/detail/CVE-2021-20190) |
| CVE-2021-31684 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-31684](https://nvd.nist.gov/vuln/detail/CVE-2021-31684) |
| CVE-2021-34538 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-34538](https://nvd.nist.gov/vuln/detail/CVE-2021-34538) |
| CVE-2021-34538 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-34538](https://nvd.nist.gov/vuln/detail/CVE-2021-34538) |
| CVE-2021-34538 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-34538](https://nvd.nist.gov/vuln/detail/CVE-2021-34538) |
| CVE-2022-25647 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-25647](https://nvd.nist.gov/vuln/detail/CVE-2022-25647) |
| CVE-2022-25647 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-25647](https://nvd.nist.gov/vuln/detail/CVE-2022-25647) |
| CVE-2022-25857 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-25857](https://nvd.nist.gov/vuln/detail/CVE-2022-25857) |
| CVE-2022-3171 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3171](https://nvd.nist.gov/vuln/detail/CVE-2022-3171) |
| CVE-2022-3171 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3171](https://nvd.nist.gov/vuln/detail/CVE-2022-3171) |
| CVE-2022-3509 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3509](https://nvd.nist.gov/vuln/detail/CVE-2022-3509) |
| CVE-2022-3509 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3509](https://nvd.nist.gov/vuln/detail/CVE-2022-3509) |
| CVE-2022-3510 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3510](https://nvd.nist.gov/vuln/detail/CVE-2022-3510) |
| CVE-2022-36364 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-36364](https://nvd.nist.gov/vuln/detail/CVE-2022-36364) |
| CVE-2022-37866 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-37866](https://nvd.nist.gov/vuln/detail/CVE-2022-37866) |
| CVE-2022-40149 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-40149](https://nvd.nist.gov/vuln/detail/CVE-2022-40149) |
| CVE-2022-40149 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-40149](https://nvd.nist.gov/vuln/detail/CVE-2022-40149) |
| CVE-2022-40150 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-40150](https://nvd.nist.gov/vuln/detail/CVE-2022-40150) |
| CVE-2022-40150 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-40150](https://nvd.nist.gov/vuln/detail/CVE-2022-40150) |
| CVE-2022-41404 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-41404](https://nvd.nist.gov/vuln/detail/CVE-2022-41404) |
| CVE-2022-42003 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42003](https://nvd.nist.gov/vuln/detail/CVE-2022-42003) |
| CVE-2022-42003 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42003](https://nvd.nist.gov/vuln/detail/CVE-2022-42003) |
| CVE-2022-42003 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42003](https://nvd.nist.gov/vuln/detail/CVE-2022-42003) |
| CVE-2022-42003 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42003](https://nvd.nist.gov/vuln/detail/CVE-2022-42003) |
| CVE-2022-42004 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42004](https://nvd.nist.gov/vuln/detail/CVE-2022-42004) |
| CVE-2022-42004 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42004](https://nvd.nist.gov/vuln/detail/CVE-2022-42004) |
| CVE-2022-42004 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42004](https://nvd.nist.gov/vuln/detail/CVE-2022-42004) |
| CVE-2022-45685 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-45685](https://nvd.nist.gov/vuln/detail/CVE-2022-45685) |
| CVE-2022-45685 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-45685](https://nvd.nist.gov/vuln/detail/CVE-2022-45685) |
| CVE-2022-45693 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-45693](https://nvd.nist.gov/vuln/detail/CVE-2022-45693) |
| CVE-2022-45693 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-45693](https://nvd.nist.gov/vuln/detail/CVE-2022-45693) |
| CVE-2022-46751 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-46751](https://nvd.nist.gov/vuln/detail/CVE-2022-46751) |
| CVE-2022-46751 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-46751](https://nvd.nist.gov/vuln/detail/CVE-2022-46751) |
| CVE-2023-1370 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-1370](https://nvd.nist.gov/vuln/detail/CVE-2023-1370) |
| CVE-2023-1436 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-1436](https://nvd.nist.gov/vuln/detail/CVE-2023-1436) |
| CVE-2023-1436 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-1436](https://nvd.nist.gov/vuln/detail/CVE-2023-1436) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-6378 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-6378](https://nvd.nist.gov/vuln/detail/CVE-2023-6378) |
| CVE-2023-6378 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-6378](https://nvd.nist.gov/vuln/detail/CVE-2023-6378) |
| CVE-2023-6481 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-6481](https://nvd.nist.gov/vuln/detail/CVE-2023-6481) |
| CVE-2023-6481 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-6481](https://nvd.nist.gov/vuln/detail/CVE-2023-6481) |
| CVE-2024-13009 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-13009](https://nvd.nist.gov/vuln/detail/CVE-2024-13009) |
| CVE-2024-13009 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-13009](https://nvd.nist.gov/vuln/detail/CVE-2024-13009) |
| CVE-2024-29857 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-29857](https://nvd.nist.gov/vuln/detail/CVE-2024-29857) |
| CVE-2024-29857 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-29857](https://nvd.nist.gov/vuln/detail/CVE-2024-29857) |
| CVE-2024-29857 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-29857](https://nvd.nist.gov/vuln/detail/CVE-2024-29857) |
| CVE-2024-29857 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-29857](https://nvd.nist.gov/vuln/detail/CVE-2024-29857) |
| CVE-2024-30172 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-30172](https://nvd.nist.gov/vuln/detail/CVE-2024-30172) |
| CVE-2024-30172 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-30172](https://nvd.nist.gov/vuln/detail/CVE-2024-30172) |
| CVE-2024-34447 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-34447](https://nvd.nist.gov/vuln/detail/CVE-2024-34447) |
| CVE-2024-34447 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-34447](https://nvd.nist.gov/vuln/detail/CVE-2024-34447) |
| CVE-2024-36114 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-36114](https://nvd.nist.gov/vuln/detail/CVE-2024-36114) |
| CVE-2024-47561 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-47561](https://nvd.nist.gov/vuln/detail/CVE-2024-47561) |
| CVE-2024-7254 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-7254](https://nvd.nist.gov/vuln/detail/CVE-2024-7254) |
| CVE-2024-7254 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-7254](https://nvd.nist.gov/vuln/detail/CVE-2024-7254) |
| CVE-2024-7254 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-7254](https://nvd.nist.gov/vuln/detail/CVE-2024-7254) |
| CVE-2024-7254 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-7254](https://nvd.nist.gov/vuln/detail/CVE-2024-7254) |
| CVE-2024-7254 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-7254](https://nvd.nist.gov/vuln/detail/CVE-2024-7254) |
| CVE-2024-7254 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-7254](https://nvd.nist.gov/vuln/detail/CVE-2024-7254) |
| CVE-2024-7254 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-7254](https://nvd.nist.gov/vuln/detail/CVE-2024-7254) |
| CVE-2024-9823 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-9823](https://nvd.nist.gov/vuln/detail/CVE-2024-9823) |
| CVE-2025-24970 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-24970](https://nvd.nist.gov/vuln/detail/CVE-2025-24970) |
| CVE-2025-24970 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-24970](https://nvd.nist.gov/vuln/detail/CVE-2025-24970) |
| CVE-2025-27553 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-27553](https://nvd.nist.gov/vuln/detail/CVE-2025-27553) |
| CVE-2025-27817 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-27817](https://nvd.nist.gov/vuln/detail/CVE-2025-27817) |
| CVE-2025-46762 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-46762](https://nvd.nist.gov/vuln/detail/CVE-2025-46762) |
| CVE-2025-46762 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-46762](https://nvd.nist.gov/vuln/detail/CVE-2025-46762) |
| CVE-2025-46762 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-46762](https://nvd.nist.gov/vuln/detail/CVE-2025-46762) |
| CVE-2025-48734 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-48734](https://nvd.nist.gov/vuln/detail/CVE-2025-48734) |
| CVE-2025-52434 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-52434](https://nvd.nist.gov/vuln/detail/CVE-2025-52434) |
| CVE-2025-52999 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-52999](https://nvd.nist.gov/vuln/detail/CVE-2025-52999) |
| CVE-2025-52999 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-52999](https://nvd.nist.gov/vuln/detail/CVE-2025-52999) |
| CVE-2025-52999 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-52999](https://nvd.nist.gov/vuln/detail/CVE-2025-52999) |
| CVE-2025-52999 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-52999](https://nvd.nist.gov/vuln/detail/CVE-2025-52999) |
| CVE-2025-52999 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-52999](https://nvd.nist.gov/vuln/detail/CVE-2025-52999) |
| CVE-2025-52999 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-52999](https://nvd.nist.gov/vuln/detail/CVE-2025-52999) |
| CVE-2025-55163 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-55163](https://nvd.nist.gov/vuln/detail/CVE-2025-55163) |
| CVE-2025-58056 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-58056](https://nvd.nist.gov/vuln/detail/CVE-2025-58056) |
| CVE-2025-58057 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-58057](https://nvd.nist.gov/vuln/detail/CVE-2025-58057) |
| CVE-2025-58057 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-58057](https://nvd.nist.gov/vuln/detail/CVE-2025-58057) |
| CVE-2025-58057 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-58057](https://nvd.nist.gov/vuln/detail/CVE-2025-58057) |
| CVE-2025-59250 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-59250](https://nvd.nist.gov/vuln/detail/CVE-2025-59250) |
| CVE-2012-5783 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2012-5783](https://nvd.nist.gov/vuln/detail/CVE-2012-5783) |
| CVE-2012-5783 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2012-5783](https://nvd.nist.gov/vuln/detail/CVE-2012-5783) |
| CVE-2012-6153 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2012-6153](https://nvd.nist.gov/vuln/detail/CVE-2012-6153) |
| CVE-2012-6153 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2012-6153](https://nvd.nist.gov/vuln/detail/CVE-2012-6153) |
| CVE-2018-10237 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2018-10237](https://nvd.nist.gov/vuln/detail/CVE-2018-10237) |
| CVE-2018-10237 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2018-10237](https://nvd.nist.gov/vuln/detail/CVE-2018-10237) |
| CVE-2018-10237 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2018-10237](https://nvd.nist.gov/vuln/detail/CVE-2018-10237) |
| CVE-2018-10237 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2018-10237](https://nvd.nist.gov/vuln/detail/CVE-2018-10237) |
| CVE-2018-10237 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2018-10237](https://nvd.nist.gov/vuln/detail/CVE-2018-10237) |
| CVE-2018-11798 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2018-11798](https://nvd.nist.gov/vuln/detail/CVE-2018-11798) |
| CVE-2018-1313 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2018-1313](https://nvd.nist.gov/vuln/detail/CVE-2018-1313) |
| CVE-2019-12384 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2019-12384](https://nvd.nist.gov/vuln/detail/CVE-2019-12384) |
| CVE-2019-12384 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2019-12384](https://nvd.nist.gov/vuln/detail/CVE-2019-12384) |
| CVE-2019-12814 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2019-12814](https://nvd.nist.gov/vuln/detail/CVE-2019-12814) |
| CVE-2019-12814 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2019-12814](https://nvd.nist.gov/vuln/detail/CVE-2019-12814) |
| CVE-2020-13955 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-13955](https://nvd.nist.gov/vuln/detail/CVE-2020-13955) |
| CVE-2020-13956 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-13956](https://nvd.nist.gov/vuln/detail/CVE-2020-13956) |
| CVE-2020-15250 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-15250](https://nvd.nist.gov/vuln/detail/CVE-2020-15250) |
| CVE-2020-15250 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-15250](https://nvd.nist.gov/vuln/detail/CVE-2020-15250) |
| CVE-2020-15522 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-15522](https://nvd.nist.gov/vuln/detail/CVE-2020-15522) |
| CVE-2020-15522 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-15522](https://nvd.nist.gov/vuln/detail/CVE-2020-15522) |
| CVE-2020-15522 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-15522](https://nvd.nist.gov/vuln/detail/CVE-2020-15522) |
| CVE-2020-17521 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-17521](https://nvd.nist.gov/vuln/detail/CVE-2020-17521) |
| CVE-2020-17521 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-17521](https://nvd.nist.gov/vuln/detail/CVE-2020-17521) |
| CVE-2020-1945 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-1945](https://nvd.nist.gov/vuln/detail/CVE-2020-1945) |
| CVE-2020-26939 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-26939](https://nvd.nist.gov/vuln/detail/CVE-2020-26939) |
| CVE-2020-26939 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-26939](https://nvd.nist.gov/vuln/detail/CVE-2020-26939) |
| CVE-2020-26939 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-26939](https://nvd.nist.gov/vuln/detail/CVE-2020-26939) |
| CVE-2021-22569 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2021-22569](https://nvd.nist.gov/vuln/detail/CVE-2021-22569) |
| CVE-2021-22569 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2021-22569](https://nvd.nist.gov/vuln/detail/CVE-2021-22569) |
| CVE-2021-27568 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2021-27568](https://nvd.nist.gov/vuln/detail/CVE-2021-27568) |
| CVE-2021-28170 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2021-28170](https://nvd.nist.gov/vuln/detail/CVE-2021-28170) |
| CVE-2021-29425 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2021-29425](https://nvd.nist.gov/vuln/detail/CVE-2021-29425) |
| CVE-2021-36373 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2021-36373](https://nvd.nist.gov/vuln/detail/CVE-2021-36373) |
| CVE-2021-36374 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2021-36374](https://nvd.nist.gov/vuln/detail/CVE-2021-36374) |
| CVE-2022-38749 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2022-38749](https://nvd.nist.gov/vuln/detail/CVE-2022-38749) |
| CVE-2022-38750 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2022-38750](https://nvd.nist.gov/vuln/detail/CVE-2022-38750) |
| CVE-2022-38751 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2022-38751](https://nvd.nist.gov/vuln/detail/CVE-2022-38751) |
| CVE-2022-38752 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2022-38752](https://nvd.nist.gov/vuln/detail/CVE-2022-38752) |
| CVE-2022-41854 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2022-41854](https://nvd.nist.gov/vuln/detail/CVE-2022-41854) |
| CVE-2023-0833 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-0833](https://nvd.nist.gov/vuln/detail/CVE-2023-0833) |
| CVE-2023-33201 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-33201](https://nvd.nist.gov/vuln/detail/CVE-2023-33201) |
| CVE-2023-33201 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-33201](https://nvd.nist.gov/vuln/detail/CVE-2023-33201) |
| CVE-2023-33201 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-33201](https://nvd.nist.gov/vuln/detail/CVE-2023-33201) |
| CVE-2023-33201 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-33201](https://nvd.nist.gov/vuln/detail/CVE-2023-33201) |
| CVE-2023-33202 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-33202](https://nvd.nist.gov/vuln/detail/CVE-2023-33202) |
| CVE-2023-33202 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-33202](https://nvd.nist.gov/vuln/detail/CVE-2023-33202) |
| CVE-2023-33202 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-33202](https://nvd.nist.gov/vuln/detail/CVE-2023-33202) |
| CVE-2023-33202 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-33202](https://nvd.nist.gov/vuln/detail/CVE-2023-33202) |
| CVE-2023-42503 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-42503](https://nvd.nist.gov/vuln/detail/CVE-2023-42503) |
| CVE-2023-51074 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-51074](https://nvd.nist.gov/vuln/detail/CVE-2023-51074) |
| CVE-2024-12798 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-12798](https://nvd.nist.gov/vuln/detail/CVE-2024-12798) |
| CVE-2024-12798 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-12798](https://nvd.nist.gov/vuln/detail/CVE-2024-12798) |
| CVE-2024-12798 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-12798](https://nvd.nist.gov/vuln/detail/CVE-2024-12798) |
| CVE-2024-12798 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-12798](https://nvd.nist.gov/vuln/detail/CVE-2024-12798) |
| CVE-2024-12798 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-12798](https://nvd.nist.gov/vuln/detail/CVE-2024-12798) |
| CVE-2024-12798 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-12798](https://nvd.nist.gov/vuln/detail/CVE-2024-12798) |
| CVE-2024-23944 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-23944](https://nvd.nist.gov/vuln/detail/CVE-2024-23944) |
| CVE-2024-23945 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-23945](https://nvd.nist.gov/vuln/detail/CVE-2024-23945) |
| CVE-2024-23945 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-23945](https://nvd.nist.gov/vuln/detail/CVE-2024-23945) |
| CVE-2024-23953 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-23953](https://nvd.nist.gov/vuln/detail/CVE-2024-23953) |
| CVE-2024-23953 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-23953](https://nvd.nist.gov/vuln/detail/CVE-2024-23953) |
| CVE-2024-25710 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-25710](https://nvd.nist.gov/vuln/detail/CVE-2024-25710) |
| CVE-2024-25710 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-25710](https://nvd.nist.gov/vuln/detail/CVE-2024-25710) |
| CVE-2024-26308 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-26308](https://nvd.nist.gov/vuln/detail/CVE-2024-26308) |
| CVE-2024-26308 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-26308](https://nvd.nist.gov/vuln/detail/CVE-2024-26308) |
| CVE-2024-29025 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-29025](https://nvd.nist.gov/vuln/detail/CVE-2024-29025) |
| CVE-2024-29869 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-29869](https://nvd.nist.gov/vuln/detail/CVE-2024-29869) |
| CVE-2024-29869 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-29869](https://nvd.nist.gov/vuln/detail/CVE-2024-29869) |
| CVE-2024-30171 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-30171](https://nvd.nist.gov/vuln/detail/CVE-2024-30171) |
| CVE-2024-30171 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-30171](https://nvd.nist.gov/vuln/detail/CVE-2024-30171) |
| CVE-2024-30171 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-30171](https://nvd.nist.gov/vuln/detail/CVE-2024-30171) |
| CVE-2024-30171 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-30171](https://nvd.nist.gov/vuln/detail/CVE-2024-30171) |
| CVE-2024-31141 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-31141](https://nvd.nist.gov/vuln/detail/CVE-2024-31141) |
| CVE-2024-47535 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-47535](https://nvd.nist.gov/vuln/detail/CVE-2024-47535) |
| CVE-2024-47535 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-47535](https://nvd.nist.gov/vuln/detail/CVE-2024-47535) |
| CVE-2024-47554 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-47554](https://nvd.nist.gov/vuln/detail/CVE-2024-47554) |
| CVE-2024-47554 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-47554](https://nvd.nist.gov/vuln/detail/CVE-2024-47554) |
| CVE-2024-47554 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-47554](https://nvd.nist.gov/vuln/detail/CVE-2024-47554) |
| CVE-2024-56128 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-56128](https://nvd.nist.gov/vuln/detail/CVE-2024-56128) |
| CVE-2024-6763 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-6763](https://nvd.nist.gov/vuln/detail/CVE-2024-6763) |
| CVE-2024-6763 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-6763](https://nvd.nist.gov/vuln/detail/CVE-2024-6763) |
| CVE-2024-6763 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-6763](https://nvd.nist.gov/vuln/detail/CVE-2024-6763) |
| CVE-2024-6763 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-6763](https://nvd.nist.gov/vuln/detail/CVE-2024-6763) |
| CVE-2024-6763 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-6763](https://nvd.nist.gov/vuln/detail/CVE-2024-6763) |
| CVE-2024-8184 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-8184](https://nvd.nist.gov/vuln/detail/CVE-2024-8184) |
| CVE-2025-11226 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-11226](https://nvd.nist.gov/vuln/detail/CVE-2025-11226) |
| CVE-2025-11226 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-11226](https://nvd.nist.gov/vuln/detail/CVE-2025-11226) |
| CVE-2025-11226 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-11226](https://nvd.nist.gov/vuln/detail/CVE-2025-11226) |
| CVE-2025-25193 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-25193](https://nvd.nist.gov/vuln/detail/CVE-2025-25193) |
| CVE-2025-25193 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-25193](https://nvd.nist.gov/vuln/detail/CVE-2025-25193) |
| CVE-2025-30474 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-30474](https://nvd.nist.gov/vuln/detail/CVE-2025-30474) |
| CVE-2025-3588 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-3588](https://nvd.nist.gov/vuln/detail/CVE-2025-3588) |
| CVE-2025-46392 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-46392](https://nvd.nist.gov/vuln/detail/CVE-2025-46392) |
| CVE-2025-48924 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-48924](https://nvd.nist.gov/vuln/detail/CVE-2025-48924) |
| CVE-2025-48924 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-48924](https://nvd.nist.gov/vuln/detail/CVE-2025-48924) |
| CVE-2025-48924 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-48924](https://nvd.nist.gov/vuln/detail/CVE-2025-48924) |
| CVE-2025-48924 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-48924](https://nvd.nist.gov/vuln/detail/CVE-2025-48924) |
| CVE-2025-48924 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-48924](https://nvd.nist.gov/vuln/detail/CVE-2025-48924) |
| CVE-2025-48924 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-48924](https://nvd.nist.gov/vuln/detail/CVE-2025-48924) |
| CVE-2025-48924 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-48924](https://nvd.nist.gov/vuln/detail/CVE-2025-48924) |
| CVE-2025-48924 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-48924](https://nvd.nist.gov/vuln/detail/CVE-2025-48924) |
| CVE-2025-49128 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-49128](https://nvd.nist.gov/vuln/detail/CVE-2025-49128) |
| CVE-2025-49128 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-49128](https://nvd.nist.gov/vuln/detail/CVE-2025-49128) |
| CVE-2025-49128 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-49128](https://nvd.nist.gov/vuln/detail/CVE-2025-49128) |
| CVE-2025-53864 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-53864](https://nvd.nist.gov/vuln/detail/CVE-2025-53864) |
| CVE-2025-58457 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-58457](https://nvd.nist.gov/vuln/detail/CVE-2025-58457) |
| CVE-2025-58457 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-58457](https://nvd.nist.gov/vuln/detail/CVE-2025-58457) |
| CVE-2025-59419 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-59419](https://nvd.nist.gov/vuln/detail/CVE-2025-59419) |
| CVE-2025-59419 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-59419](https://nvd.nist.gov/vuln/detail/CVE-2025-59419) |
| CVE-2025-8885 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-8885](https://nvd.nist.gov/vuln/detail/CVE-2025-8885) |
| CVE-2025-8885 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-8885](https://nvd.nist.gov/vuln/detail/CVE-2025-8885) |
| CVE-2025-8916 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-8916](https://nvd.nist.gov/vuln/detail/CVE-2025-8916) |
| CVE-2025-8916 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-8916](https://nvd.nist.gov/vuln/detail/CVE-2025-8916) |
| CVE-2025-8916 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-8916](https://nvd.nist.gov/vuln/detail/CVE-2025-8916) |
| CVE-2025-8916 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-8916](https://nvd.nist.gov/vuln/detail/CVE-2025-8916) |
| CVE-2020-8908 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8908](https://nvd.nist.gov/vuln/detail/CVE-2020-8908) |
| CVE-2020-8908 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8908](https://nvd.nist.gov/vuln/detail/CVE-2020-8908) |
| CVE-2020-8908 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8908](https://nvd.nist.gov/vuln/detail/CVE-2020-8908) |
| CVE-2020-8908 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8908](https://nvd.nist.gov/vuln/detail/CVE-2020-8908) |
| CVE-2020-8908 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8908](https://nvd.nist.gov/vuln/detail/CVE-2020-8908) |
| CVE-2020-8908 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8908](https://nvd.nist.gov/vuln/detail/CVE-2020-8908) |
| CVE-2020-8908 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8908](https://nvd.nist.gov/vuln/detail/CVE-2020-8908) |
| CVE-2020-8908 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8908](https://nvd.nist.gov/vuln/detail/CVE-2020-8908) |
| CVE-2020-8908 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8908](https://nvd.nist.gov/vuln/detail/CVE-2020-8908) |
| CVE-2024-12801 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-12801](https://nvd.nist.gov/vuln/detail/CVE-2024-12801) |
| CVE-2024-12801 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-12801](https://nvd.nist.gov/vuln/detail/CVE-2024-12801) |
| CVE-2024-12801 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-12801](https://nvd.nist.gov/vuln/detail/CVE-2024-12801) |
| CVE-2025-46551 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-46551](https://nvd.nist.gov/vuln/detail/CVE-2025-46551) |
## 7.12.0 릴리스 정보
다음 릴리스 정보에는 Amazon EMR 릴리스 7.12.0에 대한 정보가 포함되어 있습니다.
+ **새로운 기능**
+ **EMR Serverless용 서버리스 스토리지** - Amazon EMR Serverless는 EMR 릴리스 7.12 이상과 함께 서버리스 스토리지를 도입하여 Apache Spark 워크로드에 대한 로컬 디스크 프로비저닝을 제거합니다. EMR Serverless는 스토리지 요금 없이 셔플과 같은 중간 데이터 작업을 자동으로 처리합니다. 서버리스 스토리지는 스토리지를 컴퓨팅에서 분리하므로 Spark는 임시 데이터를 보존하기 위해 활성 상태를 유지하는 대신 유휴 시 작업자를 즉시 해제할 수 있습니다. 자세한 내용은 [aws.amazon.com/serverless-storage-for-emr-serverless](aws.amazon.com/serverless-storage-for-emr-serverless)를 참조하세요.
+ **애플리케이션 업그레이드** - Amazon EMR 7.12.0 애플리케이션 업그레이드에는 Delta 3.3.2-amzn-1, Flink 1.20.0-amzn-6, HBase 2.6.2-amzn-3, HCatalog 3.1.3-amzn-21, Hadoop 3.4.1-amzn-4, Hive 3.1.3-amzn-21, Hudi 1.0.2-amzn-1, Iceberg 1.10.0-amzn-0, Presto 0.287-amzn-6, Spark 3.5.6-amzn-1, Tez 0.10.2-amzn-amzn-19, Triamzn ZooKeeper -
+ **Iceberg 구체화된 뷰** - Amazon EMR 7.12.0부터 Amazon EMR Spark는 Iceberg 구체화된 뷰(MV)의 생성 및 관리를 지원합니다.
+ **Hudi 전체 테이블 액세스** - Amazon EMR 7.12.0부터 Amazon EMR은 이제 Lake Formation에 정의된 정책을 기반으로 Apache Spark의 Apache Hudi에 대한 전체 테이블 액세스(FTA) 제어를 지원합니다. 이 기능을 사용하면 작업 역할에 전체 테이블 액세스 권한이 있을 때 Lake Formation 등록 테이블의 Amazon EMR Spark 작업에서 읽기 및 쓰기 작업을 수행할 수 있습니다.
+ **Iceberg 버전 업그레이드** - Amazon EMR 7.12.0에서 Apache Iceberg 버전 1.10 지원
+ **Lake Formation을 사용한 Spark 네이티브 FGAC 지원** - Lake Formation에 등록된 Apache Hive, Apache Iceberg 및 Delta Lake 테이블에 대한 세분화된 액세스 제어를 통해 DDL/DML 작업(예: CREATE, ALTER, DELETE, DROP)을 수행할 수 있습니다.
+ **Spark 작업에 대한 감사 컨텍스트** - Amazon EMR 7.12.0부터 Lake Formation이 활성화된 클러스터가 있는 Amazon EMR Spark 작업에 대한 감사 컨텍스트를 CloudTrail 로그의 AWS Glue 및 Lake Formation API 호출에 사용할 수 있습니다.
+ Amazon EMR 7.12.0은 GetClusterSessionCredentials 세션 자격 증명 인증 프로세스를 개선하여 이전 Amazon EMR 릴리스에 비해 IAM Identity Center 지원 클러스터에서 Livy 대화형 세션 및 클러스터 내 UI 액세스의 지연 시간을 크게 줄입니다.
+ Amazon EMR 7.12.0부터 Amazon EMR HBase on S3는 Amazon EMR 버전 업그레이드를 간소화하기 위해 읽기 전용 복제본 사전 워밍 기능을 추가했습니다. 이 기능은 Amazon EMR 버전 7.12 이상에서 기존 HBase 클러스터를 업그레이드하는 데 사용할 수 있습니다.
+ **알려진 문제 및 제한 사항**
+ **Athena SQL 호환성**
+ Athena SQL은 다음 오류로 인해 Amazon EMR Spark에서 생성한 Iceberg 테이블 유형 V3를 읽을 수 없습니다. GENERIC\$1INTERNAL\$1ERROR: 지원되지 않는 버전 3을 읽을 수 없습니다.
+ Amazon EMR Spark를 사용하여 Athena를 사용하여 생성된 Iceberg 테이블에 데이터를 쓰는 것은 속성 'write.object-storage.path'가 더 이상 사용되지 않으며 2.0에서 제거됩니다. 대신 'write.data.path'를 사용합니다.
+ **Iceberg 구체화된 뷰(MV)** - Amazon EMR 7.12.0은 구체화된 뷰 생성, 쿼리 재작성 및 증분 새로 고침을 위한 뷰 SQL 절을 제한적으로 지원합니다. 자세한 내용은 Iceberg 구체화된 뷰 기능 설명서 페이지에서 확인할 수 있습니다.
+ **Hudi FTA 쓰기**는 작업 실행 중에 자격 증명 벤딩에 HoodieCredentialedHadoopStorage를 사용해야 합니다. Hudi 작업을 실행할 때는 다음 구성을 설정합니다.
+ `hoodie.storage.class=org.apache.spark.sql.hudi.storage.HoodieCredentialedHadoopStorage`
+ Hudi FTA 쓰기 지원은 기본 Hudi 구성에서만 작동합니다. 사용자 지정이거나 기본값이 아닌 Hudi 설정은 완전히 지원되지 않을 수 있으며 예기치 않은 동작이 발생할 수 있습니다. FTA 쓰기 모드에서는 Hudi Merge-On-Read(MOR) 테이블에 대한 클러스터링도 지원되지 않습니다.
+ **변경 사항, 개선 사항 및 해결된 문제**
+ EMR 7.12.0부터 EMR은 영구 스파크 기록 서버를 통해 서비스 호스팅 스파크 로그에 대한 KMS 키 ARN을 지원합니다. 이전 EMR 버전은 KeyID만 지원했습니다.
+ EMR 7.12.0부터 EMR은 EMR 클러스터에서 Hue를 호스팅할 때 SSL 인증서 사용을 금지하는 Hue 관련 문제를 해결했습니다.
## 7.12.0 기본 Java 버전
Amazon EMR 릴리스 7.12.0은 Apache Livy를 제외하고 Corretto 17(OpenJDK)을 지원하는 애플리케이션에 기본적으로 Amazon Corretto 17(OpenJDK 기반)과 함께 제공됩니다.
다음 표에는 Amazon EMR 7.12.0의 애플리케이션에 대한 기본 Java 버전이 나와 있습니다.
| 애플리케이션 | Java 및 Amazon Corretto 버전(기본값은 굵은체로 표시) |
| --- | --- |
| 델타 | 17, 11, 8 |
| Flink | 17, 11, 8 |
| HBase | 17, 11, 8 |
| HCatalog | 17, 11, 8 |
| Hadoop | 17, 11, 8 |
| Hive | 17, 11, 8 |
| Hudi | 17, 11, 8 |
| Iceberg | 17, 11 |
| Livy | 17, 11, 8 |
| Oozie | 17, 11, 8 |
| 피닉스 | 17, 11, 8 |
| PrestoDB | 8 |
| Spark | 17, 11, 8 |
| Spark RAPIDS | 17, 11, 8 |
| Tez의 Hive 실행 시간 비교 | 17, 11, 8 |
| Trino | 21, 17 |
| Zeppelin | 17, 11, 8 |
| Pig | 17, 11, 8 |
| Zookeeper | 17, 11, 8 |
## 7.12.0 구성 요소 버전
이 릴리스를 통해 Amazon EMR이 설치하는 구성 요소는 다음과 같습니다. 일부는 빅 데이터 애플리케이션 패키지의 일부로 설치됩니다. 나머지는 Amazon EMR에 고유하며 시스템 프로세스 및 기능을 위해 설치됩니다. 이는 일반적으로 `emr` 또는 `aws`로 시작됩니다. 최근 Amazon EMR 릴리스의 빅 데이터 애플리케이션 패키지는 일반적으로 커뮤니티에서 발견된 최신 버전입니다. 가능한 한 빨리 Amazon EMR에서 커뮤니티 릴리스를 제공합니다.
Amazon EMR의 일부 구성 요소는 커뮤니티 버전과 다릅니다. 이러한 구성 요소에는 `CommunityVersion-amzn-EmrVersion` 양식의 버전 레이블이 있습니다. `EmrVersion`은 0에서 시작합니다. 예를 들어, 버전 2.2의 `myapp-component`라는 오픈 소스 커뮤니티 구성 요소가 다른 Amazon EMR 릴리스에 포함되도록 세 번 수정된 경우 해당 릴리스 버전은 `2.2-amzn-2`로 나열됩니다.
| 구성 요소 | 버전 | 설명 |
| --- | --- | --- |
| adot-java-agent | 1.31.0 | 애플리케이션 대몬(daemon)에서 지표를 수집하는 Java 에이전트입니다. |
| delta | 3.3.2-amzn-1 | Delta Lake는 방대한 분석 데이터 세트를 위한 오픈 테이블 형식입니다. |
| emr-amazon-cloudwatch-agent | 1.300032.2-amzn-0 | Amazon EC2 인스턴스에서 내부 시스템 수준 지표와 사용자 지정 애플리케이션 지표를 수집하는 애플리케이션입니다. |
| emr-ddb | 5.7.0 | 하둡 에코시스템 애플리케이션용 Amazon DynamoDB 커넥터 |
| emr-goodies | 3.21.0 | 편리한 하둡 에코시스템용 추가 라이브러리 |
| emr-kinesis | 3.25.0 | 하둡 에코시스템 애플리케이션용 Amazon Kinesis 커넥터. |
| emr-notebook-env | 1.18.0 | Jupyter Enterprise Gateway가 포함된 EMR 노트북용 Conda 환경 |
| emr-s3-dist-cp | 2.42.0 | Amazon S3용으로 최적화된 분사 복사 애플리케이션. |
| emr-s3-select | 2.21.0 | EMR S3Select 커넥터 |
| emr-wal-cli | 1.3.6 | emrwal 목록/삭제에 사용되는 CLI입니다. |
| emrfs | 2.73.0 | 하둡 에코시스템 애플리케이션용 Amazon S3 커넥터. |
| flink-client | 1.20.0-amzn-6 | Apache Flink 명령줄 클라이언트 스크립트 및 애플리케이션 |
| flink-jobmanager-config | 1.20.0-amzn-6 | Apache Flink JobManager에 대한 EMR 노드에서 리소스를 관리합니다. |
| hadoop-client | 3.4.1-amzn-4 | 'hdfs', 'hadoop', 'yarn' 등과 같은 하둡 명령줄 클라이언트 |
| hadoop-hdfs-datanode | 3.4.1-amzn-4 | 블록을 저장하는 HDFS 노드 수준 서비스 |
| hadoop-hdfs-library | 3.4.1-amzn-4 | HDFS 명령줄 클라이언트 및 라이브러리 |
| hadoop-hdfs-namenode | 3.4.1-amzn-4 | 파일 이름 및 블록 위치를 추적하는 HDFS 서비스 |
| hadoop-hdfs-zkfc | 3.4.1-amzn-4 | HA 모드의 네임노드를 추적하기 위한 ZKFC 서비스입니다. |
| hadoop-hdfs-journalnode | 3.4.1-amzn-4 | HA 클러스터에서 하둡 파일 시스템 저널을 관리하기 위한 HDFS 서비스 |
| hadoop-httpfs-server | 3.4.1-amzn-4 | HDFS 작업에 대한 HTTP 엔드포인트 |
| hadoop-kms-server | 3.4.1-amzn-4 | 하둡의 KeyProvider API를 기반으로 하는 암호화 키 관리 서버 |
| hadoop-mapred | 3.4.1-amzn-4 | MapReduce 애플리케이션을 실행하는 MapReduce 실행 엔진 라이브러리 |
| hadoop-yarn-nodemanager | 3.4.1-amzn-4 | 개별 노드의 컨테이너를 관리하는 YARN 서비스 |
| hadoop-yarn-resourcemanager | 3.4.1-amzn-4 | 클러스터 리소스 및 분산 애플리케이션을 할당 및 관리하는 YARN 서비스 |
| hadoop-yarn-timeline-server | 3.4.1-amzn-4 | YARN 애플리케이션의 현재 및 기록 정보를 가져오는 서비스 |
| hbase-hmaster | 2.6.2-amzn-3 | 리전 조정 및 관리 명령의 실행을 담당하는 HBase 클러스터용 서비스 |
| hbase-region-server | 2.6.2-amzn-3 | 한 개 이상의 HBase 리전에 서비스를 제공하는 서비스 |
| hbase-client | 2.6.2-amzn-3 | HBase 명령줄 클라이언트 |
| hbase-rest-server | 2.6.2-amzn-3 | HBase용 RESTful HTTP 엔드포인트를 제공하는 서비스 |
| hbase-thrift-server | 2.6.2-amzn-3 | HBase에 Thrift 엔드포인트를 제공하는 서비스 |
| hbase-operator-tools | 2.6.2-amzn-3 | Apache HBase 클러스터용 복구 도구. |
| hcatalog-client | 3.1.3-amzn-21 | hcatalog-server를 조정하기 위한 'hcat' 명령줄 클라이언트 |
| hcatalog-server | 3.1.3-amzn-21 | 분산 애플리케이션용 스토리지 관리 계층, 테이블 및 HCatalog를 제공하는 서비스 |
| hcatalog-webhcat-server | 3.1.3-amzn-21 | HCatalog에 REST 인터페이스를 제공하는 HTTP 엔드포인트 |
| hive-client | 3.1.3-amzn-21 | Hive 명령줄 클라이언트 |
| hive-hbase | 3.1.3-amzn-21 | Hive-hbase 클라이언트 |
| hive-metastore-server | 3.1.3-amzn-21 | 하둡 작업에 대한 SQL용 메타데이터가 저장되는 시맨틱 리포지토리인 Hive 메타스토어에 액세스하기 위한 서비스 |
| hive-server2 | 3.1.3-amzn-21 | Hive 쿼리를 웹 요청으로 수락하기 위한 서비스 |
| hudi | 1.0.2-amzn-1 | 짧은 지연 시간 및 높은 효율성으로 데이터 파이프라인을 구동하는 증분 처리 프레임워크. |
| hudi-presto | 1.0.2-amzn-1 | Hudi로 Presto를 실행하기 위한 번들 라이브러리. |
| hudi-trino | 1.0.2-amzn-1 | Hudi와 함께 Trnio를 실행하기 위한 번들 라이브러리. |
| hudi-spark | 1.0.2-amzn-1 | Hudi와 함께 Spark를 실행하기 위한 번들 라이브러리. |
| hue-server | 4.11.0 | 하둡 에코시스템 애플리케이션을 사용하여 데이터를 분석하는 웹 애플리케이션. |
| iceberg | 1.10.0-amzn-0 | Apache Iceberg는 방대한 분석 데이터 세트를 위한 오픈 테이블 형식입니다. |
| jupyterhub | 1.5.0 | Jupyter Notebook용 다중 사용자 서버 |
| livy-server | 0.8.0-incubating | Apache Spark와 상호작용하기 위한 REST 인터페이스 |
| nginx | 1.12.1 | HTTP인 nginx [engine x] 및 역방향 프록시 서버 |
| mariadb-server | 5.5.68 이상 | MariaDB 데이터베이스 서버. |
| nvidia-cuda | 12.5.0 | Nvidia 드라이버와 Cuda 도구 키트 |
| oozie-client | 5.2.1 | Oozie 명령줄 클라이언트 |
| oozie-server | 5.2.1 | Oozie 워크플로 요청을 수락하는 서비스 |
| opencv | 4.7.0 | 오픈 소스 컴퓨터 비전 라이브러리. |
| phoenix-library | 5.2.1 | 서버 및 클라이언트의 phoenix 라이브러리 |
| phoenix-connectors | 6.0.0 | Spark-3용 Apache Phoenix 커넥터 |
| phoenix-query-server | 6.0.0 | Avatica API에 대한 JSON 형식 액세스 및 프로토콜 버퍼 액세스를 비롯하여 JDBC 액세스를 제공하는 경량 서버 |
| presto-coordinator | 0.287-amzn-6 | presto-worker의 쿼리를 수락하고 쿼리 실행을 관리하는 서비스. |
| presto-worker | 0.287-amzn-6 | 여러 쿼리를 실행하는 서비스. |
| presto-client | 0.287-amzn-6 | Presto 서버가 시작되지 않은 HA 클러스터의 대기 마스터에 설치된 Presto 명령줄 클라이언트. |
| trino-coordinator | 476-amzn-1 | trino-workers의 쿼리를 수락하고 쿼리 실행을 관리하는 서비스. |
| trino-worker | 476-amzn-1 | 여러 쿼리를 실행하는 서비스. |
| trino-client | 476-amzn-1 | Trino 서버가 시작되지 않은 HA 클러스터의 대기 마스터에 설치된 Trino 명령줄 클라이언트. |
| pig-client | 0.17.0 | Pig 명령줄 클라이언트. |
| r | 4.3.2 | 통계 컴퓨팅용 R 프로젝트 |
| ranger-kms-server | 2.0.0 | Apache Ranger 키 관리 시스템 |
| spark-client | 3.5.6-amzn-1 | Spark 명령줄 클라이언트. |
| spark-history-server | 3.5.6-amzn-1 | 완료된 Spark 애플리케이션의 수명에 대해 기록된 이벤트를 조회하는 웹 UI. |
| spark-on-yarn | 3.5.6-amzn-1 | YARN용 인 메모리 실행 엔진. |
| spark-yarn-slave | 3.5.6-amzn-1 | YARN 슬레이브에서 필요한 Apache Spark 라이브러리. |
| spark-rapids | 25.08.0-amzn-0 | GPU로 Apache Spark를 가속화하는 Nvidia Spark RAPIDS 플러그인. |
| tensorflow | 2.19.0 | TensorFlow는 고성능 수치 계산용 오픈 소스 소프트웨어 라이브러리입니다. |
| tez-on-yarn | 0.10.2-amzn-19 | tez YARN 애플리케이션 및 라이브러리. |
| tez-on-worker | 0.10.2-amzn-19 | 워커 노드에 대한 tez YARN 애플리케이션 및 라이브러리. |
| zeppelin-server | 0.11.1 | 대화형 데이터 분석이 가능한 웹 기반 노트북 |
| zookeeper-server | 3.9.3-amzn-4 | 구성 정보 유지 관리, 이름 지정, 분산 동기화 제공 및 그룹 서비스 제공을 위한 중앙 집중식 서비스. |
| zookeeper-client | 3.9.3-amzn-4 | ZooKeeper 명령줄 클라이언트. |
## 7.12.0 구성 분류
구성 분류를 사용하면 애플리케이션을 사용자 지정할 수 있습니다. 이는 종종 `hive-site.xml`과 같이 애플리케이션의 구성 XML 파일에 해당합니다. 자세한 내용은 [애플리케이션 구성](emr-configure-apps.md) 단원을 참조하십시오.
재구성 작업은 실행 중인 클러스터의 인스턴스 그룹에 대한 구성을 지정할 때 수행됩니다. Amazon EMR은 사용자가 수정한 분류에 대한 재구성 작업만 시작합니다. 자세한 내용은 [실행 중인 클러스터에서 인스턴스 그룹 재구성](emr-configure-apps-running-cluster.md) 단원을 참조하십시오.
**emr-7.12.0 분류**
| 분류 | 설명 | 재구성 작업 |
| --- | --- | --- |
| capacity-scheduler | Hadoop capacity-scheduler.xml 파일에서 값을 변경합니다. | Restarts the ResourceManager service. |
| container-executor | Hadoop YARN container-executor.cfg 파일에서 값을 변경합니다. | Not available. |
| container-log4j | Hadoop YARN container-log4j.properties 파일에서 값을 변경합니다. | Not available. |
| core-site | Hadoop core-site.xml 파일에서 값을 변경합니다. | Restarts the Hadoop HDFS services Namenode, SecondaryNamenode, Datanode, ZKFC, and Journalnode. Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts Hadoop KMS, Ranger KMS, HiveServer2, Hive MetaStore, Hadoop Httpfs, and MapReduce-HistoryServer. |
| docker-conf | Docker 관련 설정을 변경합니다. | Not available. |
| emrfs-site | EMRFS 설정을 변경합니다. | Restarts the Hadoop HDFS services Namenode, SecondaryNamenode, Datanode, ZKFC, and Journalnode. Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts HBaseRegionserver, HBaseMaster, HBaseThrift, HBaseRest, HiveServer2, Hive MetaStore, Hadoop Httpfs, and MapReduce-HistoryServer. |
| flink-conf | flink-conf.yaml 설정을 변경합니다. | Restarts Flink history server. |
| flink-log4j | Flink log4j.properties 설정을 변경합니다. | Restarts Flink history server. |
| flink-log4j-session | Kubernetes 및 Yarn 세션에 대한 Flink log4j-session.properties 설정을 변경합니다. | Restarts Flink history server. |
| flink-log4j-cli | Flink log4j-cli.properties 설정을 변경합니다. | Restarts Flink history server. |
| hadoop-env | 모든 Hadoop 구성 요소에 대한 Hadoop 환경에서 값을 변경합니다. | Restarts the Hadoop HDFS services Namenode, SecondaryNamenode, Datanode, ZKFC, and Journalnode. Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts PhoenixQueryserver, HiveServer2, Hive MetaStore, and MapReduce-HistoryServer. |
| hadoop-log4j | Hadoop log4j.properties 파일에서 값을 변경합니다. | Restarts the Hadoop HDFS services SecondaryNamenode, Datanode, and Journalnode. Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts Hadoop KMS, Hadoop Httpfs, and MapReduce-HistoryServer. |
| hadoop-ssl-server | hadoop ssl 서버 구성을 변경합니다. | Not available. |
| hadoop-ssl-client | hadoop ssl 클라이언트 구성을 변경합니다. | Not available. |
| hbase | Apache HBase에 대한 Amazon EMR 큐레이트 설정입니다. | Custom EMR specific property. Sets emrfs-site and hbase-site configs. See those for their associated restarts. |
| hbase-env | HBase 환경에서 값을 변경합니다. | Restarts the HBase services RegionServer, HBaseMaster, ThriftServer, RestServer. |
| hbase-log4j2 | HBase hbase-log4j.properties 파일에서 값을 변경합니다. | Restarts the HBase services RegionServer, HBaseMaster, ThriftServer, RestServer. |
| hbase-metrics | HBase hadoop-metrics2-hbase.properties 파일에서 값을 변경합니다. | Restarts the HBase services RegionServer, HBaseMaster, ThriftServer, RestServer. |
| hbase-policy | HBase hbase-policy.xml 파일에서 값을 변경합니다. | Not available. |
| hbase-site | HBase hbase-site.xml 파일에서 값을 변경합니다. | Restarts the HBase services RegionServer, HBaseMaster, ThriftServer, RestServer. Additionally restarts Phoenix QueryServer. |
| hdfs-encryption-zones | HDFS 암호화 영역을 구성합니다. | This classification should not be reconfigured. |
| hdfs-env | HDFS 환경에서 값을 변경합니다. | Restarts Hadoop HDFS services Namenode, Datanode, and ZKFC. |
| hdfs-site | HDFS hdfs-site.xml에서 값을 변경합니다. | Restarts the Hadoop HDFS services Namenode, SecondaryNamenode, Datanode, ZKFC, and Journalnode. Additionally restarts Hadoop Httpfs. |
| hcatalog-env | HCatalog 환경에서 값을 변경합니다. | Restarts Hive HCatalog Server. |
| hcatalog-server-jndi | HCatalog jndi.properties 환경에서 값을 변경합니다. | Restarts Hive HCatalog Server. |
| hcatalog-server-proto-hive-site | HCatalog proto-hive-site.xml에서 값을 변경합니다. | Restarts Hive HCatalog Server. |
| hcatalog-webhcat-env | HCatalog WebHCat 환경에서 값을 변경합니다. | Restarts Hive WebHCat server. |
| hcatalog-webhcat-log4j2 | HCatalog WebHCat log4j2.properties에서 값을 변경합니다. | Restarts Hive WebHCat server. |
| hcatalog-webhcat-site | HCatalog WebHCat webhcat-site.xml 파일에서 값을 변경합니다. | Restarts Hive WebHCat server. |
| hive | Apache Hive에 대한 Amazon EMR 큐레이트 설정입니다. | Sets configurations to launch Hive LLAP service. |
| hive-beeline-log4j2 | Hive beeline-log4j2.properties 파일에서 값을 변경합니다. | Not available. |
| hive-parquet-logging | Hive parquet-logging.properties 파일에서 값을 변경합니다. | Not available. |
| hive-env | Hive 환경에서 값을 변경합니다. | Restarts HiveServer2, HiveMetastore, and Hive HCatalog-Server. Runs Hive schemaTool CLI commands to verify hive-metastore. |
| hive-exec-log4j2 | Hive hive-exec-log4j2.properties 파일에서 값을 변경합니다. | Not available. |
| hive-llap-daemon-log4j2 | Hive llap-daemon-log4j2.properties 파일에서 값을 변경합니다. | Not available. |
| hive-log4j2 | Hive hive-log4j2.properties 파일에서 값을 변경합니다. | Not available. |
| hive-site | Hive hive-site.xml 파일에서 값을 변경합니다. | Restarts HiveServer2, HiveMetastore, and Hive HCatalog-Server. Runs Hive schemaTool CLI commands to verify hive-metastore. Also restarts Oozie and Zeppelin. |
| hiveserver2-site | Hive Server2 hiveserver2-site.xml 파일에서 값을 변경합니다. | Not available. |
| hue-ini | Hue ini 파일에서 값을 변경합니다. | Restarts Hue. Also activates Hue config override CLI commands to pick up new configurations. |
| httpfs-env | HTTPFS 환경에서 값을 변경합니다. | Restarts Hadoop Httpfs service. |
| httpfs-site | Hadoop httpfs-site.xml 파일에서 값을 변경합니다. | Restarts Hadoop Httpfs service. |
| hadoop-kms-acls | Hadoop kms-acls.xml 파일에서 값을 변경합니다. | Not available. |
| hadoop-kms-env | Hadoop KMS 환경에서 값을 변경합니다. | Restarts Hadoop-KMS service. |
| hadoop-kms-java-home | Hadoop의 KMS java 홈 변경 | Not available. |
| hadoop-kms-log4j | Hadoop kms-log4j.properties 파일에서 값을 변경합니다. | Not available. |
| hadoop-kms-site | Hadoop kms-site.xml 파일에서 값을 변경합니다. | Restarts Hadoop-KMS and Ranger-KMS service. |
| hudi-env | Hudi 환경에서 값을 변경합니다. | Not available. |
| hudi-defaults | Hudi hudi-defaults.conf 파일에서 값을 변경합니다. | Not available. |
| iceberg-defaults | Iceberg iceberg-defaults.conf 파일에서 값을 변경합니다. | Not available. |
| delta-defaults | Delta delta-defaults.conf 파일에서 값을 변경합니다. | Not available. |
| jupyter-notebook-conf | Jupyter Notebook jupyter\$1notebook\$1config.py 파일에서 값을 변경합니다. | Not available. |
| jupyter-hub-conf | JupyterHubs jupyterhub\$1config.py 파일에서 값을 변경합니다. | Not available. |
| jupyter-s3-conf | Jupyter Notebook S3 지속성 구성 | Not available. |
| jupyter-sparkmagic-conf | Sparkmagic config.json 파일에서 값을 변경합니다. | Not available. |
| livy-conf | Livy livy.conf 파일에서 값을 변경합니다. | Restarts Livy Server. |
| livy-env | Livy 환경에서 값을 변경합니다. | Restarts Livy Server. |
| livy-log4j2 | Livy log4j2.properties 설정을 변경합니다. | Restarts Livy Server. |
| mapred-env | MapReduce 애플리케이션 환경에서 값을 변경합니다. | Restarts Hadoop MapReduce-HistoryServer. |
| mapred-site | MapReduce 애플리케이션 mapred-site.xml 파일에서 값을 변경합니다. | Restarts Hadoop MapReduce-HistoryServer. |
| oozie-env | Oozie 환경에서 값을 변경합니다. | Restarts Oozie. |
| oozie-log4j | Oozie oozie-log4j.properties 파일에서 값을 변경합니다. | Restarts Oozie. |
| oozie-site | Oozie oozie-site.xml 파일에서 값을 변경합니다. | Restarts Oozie. |
| phoenix-hbase-metrics | Phoenix hadoop-metrics2-hbase.properties 파일에서 값을 변경합니다. | Not available. |
| phoenix-hbase-site | Phoenix hbase-site.xml 파일에서 값을 변경합니다. | Not available. |
| phoenix-log4j2 | Phoenix log4j2.properties 파일에서 값을 변경합니다. | Restarts Phoenix-QueryServer. |
| phoenix-metrics | Phoenix hadoop-metrics2-phoenix.properties 파일에서 값을 변경합니다. | Not available. |
| pig-env | Pig 환경에서 값을 변경합니다. | Not available. |
| pig-properties | Pig pig.properties 파일에서 값을 변경합니다. | Restarts Oozie. |
| pig-log4j | Pig log4j.properties 파일에서 값을 변경합니다. | Not available. |
| presto-log | Presto log.properties 파일에서 값을 변경합니다. | Restarts Presto-Server (for PrestoDB) |
| presto-config | Presto config.properties 파일에서 값을 변경합니다. | Restarts Presto-Server (for PrestoDB) |
| presto-password-authenticator | Presto password-authenticator.properties 파일에서 값을 변경합니다. | Not available. |
| presto-env | Presto presto-env.sh 파일에서 값을 변경합니다. | Restarts Presto-Server (for PrestoDB) |
| presto-node | Presto node.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-blackhole | Presto blackhole.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-cassandra | Presto cassandra.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-hive | Presto hive.properties 파일에서 값을 변경합니다. | Restarts Presto-Server (for PrestoDB) |
| presto-connector-jmx | Presto jmx.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-kafka | Presto kafka.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-lakeformation | Presto lakeformation.properties 파일에서 값을 변경합니다. | Restarts Presto-Server (for PrestoDB) |
| presto-connector-localfile | Presto localfile.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-memory | Presto memory.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-mongodb | Presto mongodb.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-mysql | Presto mysql.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-postgresql | Presto postgresql.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-raptor | Presto raptor.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-redis | Presto redis.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-redshift | Presto redshift.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-tpch | Presto tpch.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-tpcds | Presto tpcds.properties 파일에서 값을 변경합니다. | Not available. |
| trino-log | Trino log.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-config | Trino config.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-password-authenticator | Trino password-authenticator.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-env | Trino trino-env.sh 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-node | Trino node.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-blackhole | Trino blackhole.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-cassandra | Trino cassandra.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-delta | Trino delta.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-connector-hive | Trino hive.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-exchange-manager | Trino exchange-manager.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-connector-iceberg | Trino iceberg.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-connector-hudi | Trino hudi.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-connector-jmx | Trino jmx.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-kafka | Trino kafka.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-localfile | Trino localfile.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-memory | Trino memory.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-mongodb | Trino mongodb.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-mysql | Trino mysql.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-postgresql | Trino postgresql.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-raptor | Trino raptor.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-redis | Trino redis.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-redshift | Trino redshift.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-tpch | Trino tpch.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-tpcds | Trino tpcds.properties 파일에서 값을 변경합니다. | Not available. |
| ranger-kms-dbks-site | Ranger KMS dbks-site.xml 파일에서 값을 변경합니다. | Restarts Ranger KMS Server. |
| ranger-kms-site | Ranger KMS ranger-kms-site.xml 파일에서 값을 변경합니다. | Restarts Ranger KMS Server. |
| ranger-kms-env | Ranger KMS 환경에서 값을 변경합니다. | Restarts Ranger KMS Server. |
| ranger-kms-logback | Ranger KMS kms-logback.xml 파일에서 값을 변경합니다. | Not available. |
| ranger-kms-db-ca | Ranger KMS와의 MySQL SSL 연결에서 CA 파일의 값을 변경합니다. | Not available. |
| spark | Apache Spark에 대한 Amazon EMR 큐레이트 설정입니다. | This property modifies spark-defaults. See actions there. |
| spark-defaults | Spark spark-defaults.conf 파일에서 값을 변경합니다. | Restarts Spark history server and Spark thrift server. |
| spark-env | Spark 환경에서 값을 변경합니다. | Restarts Spark history server and Spark thrift server. |
| spark-hive-site | Spark hive-site.xml 파일에서 값을 변경합니다. | Not available. |
| spark-log4j2 | Spark log4j2.properties 파일에서 값을 변경합니다. | Restarts Spark history server and Spark thrift server. |
| spark-metrics | Spark metrics.properties 파일에서 값을 변경합니다. | Restarts Spark history server and Spark thrift server. |
| tez-site | Tez tez-site.xml 파일에서 값을 변경합니다. | Restart Oozie and HiveServer2. |
| yarn-env | YARN 환경에서 값을 변경합니다. | Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts MapReduce-HistoryServer. |
| yarn-site | YARN yarn-site.xml 파일에서 값을 변경합니다. | Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts Livy Server and MapReduce-HistoryServer. |
| zeppelin-env | Zeppelin 환경에서 값을 변경합니다. | Restarts Zeppelin. |
| zeppelin-site | zeppelin-site.xml에서 구성 설정을 변경합니다. | Restarts Zeppelin. |
| zookeeper-config | ZooKeeper zoo.cfg 파일에서 값을 변경합니다. | Restarts Zookeeper server. |
| zookeeper-logback | ZooKeeper logback.xml 파일에서 값을 변경합니다. | Restarts Zookeeper server. |
| cloudwatch-logs | EMR 클러스터 노드에 대한 CloudWatch Logs 통합을 구성합니다. | Not available. |
| emr-metrics | 이 노드에 대한 emr 지표 설정을 변경합니다. | Restarts the CloudWatchAgent service. |
## 7.12.0 변경 로그
**7.12.0 릴리스 및 릴리스 정보에 대한 변경 로그**
| Date | 이벤트 | 설명 |
| --- | --- | --- |
| 2025-11-21 | 문서 게시 | Amazon EMR 7.12.0 릴리스 정보 최초 게시 |
# Amazon EMR 릴리스 7.11.0
## 7.11.0 지원 수명 주기
다음 표에서는 Amazon EMR 릴리스 7.11.0에 지원되는 수명 주기 날짜를 설명합니다.
| 지원 단계 | Date |
| --- | --- |
| 초기 릴리스 날짜 | 2025년 11월 3일 |
| 표준 지원 종료 시점 | 2027년 11월 3일 |
| 지원 종료 | 2027년 11월 4일 |
| 수명 종료 | 2028년 11월 3일 |
## 7.11.0 애플리케이션 버전
이 릴리스에 포함된 애플리케이션은 [https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Install-CloudWatch-Agent.html](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Install-CloudWatch-Agent.html), [https://delta.io/](https://delta.io/), [https://flink.apache.org/](https://flink.apache.org/), [http://hbase.apache.org/](http://hbase.apache.org/), [https://cwiki.apache.org/confluence/display/Hive/HCatalog](https://cwiki.apache.org/confluence/display/Hive/HCatalog), [http://hadoop.apache.org/docs/current/](http://hadoop.apache.org/docs/current/), [http://hive.apache.org/](http://hive.apache.org/), [https://hudi.apache.org](https://hudi.apache.org), [http://gethue.com/](http://gethue.com/), [https://iceberg.apache.org/](https://iceberg.apache.org/), [https://jupyter-enterprise-gateway.readthedocs.io/en/latest/](https://jupyter-enterprise-gateway.readthedocs.io/en/latest/), [https://jupyterhub.readthedocs.io/en/latest/#](https://jupyterhub.readthedocs.io/en/latest/#), [https://livy.incubator.apache.org/](https://livy.incubator.apache.org/), [http://oozie.apache.org/](http://oozie.apache.org/), [https://phoenix.apache.org/](https://phoenix.apache.org/), [http://pig.apache.org/](http://pig.apache.org/), [https://prestodb.io/](https://prestodb.io/), [https://spark.apache.org/docs/latest/](https://spark.apache.org/docs/latest/), [https://www.tensorflow.org/](https://www.tensorflow.org/), [https://tez.apache.org/](https://tez.apache.org/), [https://trino.io/](https://trino.io/), [https://zeppelin.incubator.apache.org/](https://zeppelin.incubator.apache.org/), [https://zookeeper.apache.org](https://zookeeper.apache.org)입니다.
아래 테이블에는 이번 Amazon EMR 릴리스에서 사용할 수 있는 애플리케이션 버전과 이전 세 가지 Amazon EMR 릴리스(해당하는 경우)의 애플리케이션 버전이 나와 있습니다.
각 Amazon EMR 릴리스에서 애플리케이션 버전의 전체 기록은 다음 주제를 참조하세요.
+ [Amazon EMR 7.x 릴리스의 애플리케이션 버전](emr-release-app-versions-7.x.md)
+ [Amazon EMR 6.x 릴리스의 애플리케이션 버전](emr-release-app-versions-6.x.md)
+ [Amazon EMR 5.x 릴리스의 애플리케이션 버전](emr-release-app-versions-5.x.md)
+ [Amazon EMR 4.x 릴리스의 애플리케이션 버전](emr-release-app-versions-4.x.md)
**애플리케이션 버전 정보**
| | emr-7.11.0 | emr-7.10.0 | emr-7.9.0 | emr-7.8.0 |
| --- | --- | --- | --- | --- |
| AWS Java용 SDK | 2.35.5, 1.12.792 | 2.31.48, 1.12.782 | 2.31.16, 1.12.782 | 2.29.52, 1.12.780 |
| Python | 3.9, 3.11 | 3.9, 3.11 | 3.9, 3.11 | 3.9, 3.11 |
| Scala | 2.12.18 | 2.12.18 | 2.12.18 | 2.12.18 |
| AmazonCloudWatchAgent | 1.300032.2-amzn-0 | 1.300032.2-amzn-0 | 1.300032.2-amzn-0 | 1.300032.2-amzn-0 |
| Delta | 3.3.2-amzn-0 | 3.3.0-amzn-2 | 3.3.0-amzn-1 | 3.3.0-amzn-0 |
| Flink | 1.20.0-amzn-5 | 1.20.0-amzn-4 | 1.20.0-amzn-3 | 1.20.0-amzn-2 |
| Ganglia | - | - | - | - |
| HBase | 2.6.2-amzn-2 | 2.6.2-amzn-1 | 2.6.2-amzn-0 | 2.6.1-amzn-2 |
| HCatalog | 3.1.3-amzn-20 | 3.1.3-amzn-19 | 3.1.3-amzn-18 | 3.1.3-amzn-17 |
| Hadoop | 3.4.1-amzn-3 | 3.4.1-amzn-2 | 3.4.1-amzn-1 | 3.4.1-amzn-0 |
| Hive | 3.1.3-amzn-20 | 3.1.3-amzn-19 | 3.1.3-amzn-18 | 3.1.3-amzn-17 |
| Hudi | 1.0.2-amzn-0 | 0.15.0-amzn-7 | 0.15.0-amzn-6 | 0.15.0-amzn-5 |
| Hue | 4.11.0 | 4.11.0 | 4.11.0 | 4.11.0 |
| Iceberg | 1.9.1-amzn-0 | 1.8.1-amzn-0 | 1.7.1-amzn-2 | 1.7.1-amzn-1 |
| JupyterEnterpriseGateway | 2.6.0 | 2.6.0 | 2.6.0 | 2.6.0 |
| JupyterHub | 1.5.0 | 1.5.0 | 1.5.0 | 1.5.0 |
| Livy | 0.8.0-incubating | 0.8.0-incubating | 0.8.0-incubating | 0.8.0-incubating |
| MXNet | - | - | - | - |
| Mahout | - | - | - | - |
| Oozie | 5.2.1 | 5.2.1 | 5.2.1 | 5.2.1 |
| Phoenix | 5.2.1 | 5.2.1 | 5.2.1 | 5.2.1 |
| Pig | 0.17.0 | 0.17.0 | 0.17.0 | 0.17.0 |
| Presto | 0.287-amzn-5 | 0.287-amzn-4 | 0.287-amzn-3 | 0.287-amzn-2 |
| Spark | 3.5.6-amzn-0 | 3.5.5-amzn-1 | 3.5.5-amzn-0 | 3.5.4-amzn-0 |
| Sqoop | - | - | - | - |
| TensorFlow | 2.19.0 | 2.18.0 | 2.16.1 | 2.16.1 |
| Tez | 0.10.2-amzn-18 | 0.10.2-amzn-17 | 0.10.2-amzn-16 | 0.10.2-amzn-15 |
| Trino (PrestoSQL) | 475-amzn-0 | 470-amzn-0 | 467-amzn-2 | 467-amzn-1 |
| Zeppelin | 0.11.1 | 0.11.1 | 0.11.1 | 0.11.1 |
| ZooKeeper | 3.9.3-amzn-3 | 3.9.3-amzn-2 | 3.9.3-amzn-1 | 3.9.3-amzn-0 |
# 7.11.0 일반적인 취약성 및 노출
다음 표에는 Amazon EMR 7.11.0의 권장 구성에서 실행되는 EMR 클러스터에 영향을 주지 않는 모든 CVEs가 나열되어 있습니다. Amazon EMR은 업스트림 오픈 소스의 수정 사항 가용성에 종속되어 있으며, Amazon EMR이 수정 사항을 확인한 후 90일 이내에 코어 엔진 구성 요소의 일부로 안정적인 최신 버전을 제공합니다.
이 표는 2025년 11월 18일에 업데이트되었습니다.
| CVE ID | 심각도 | CVE 세부 정보 URL |
| --- | --- | --- |
| CVE-2015-1832 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2015-1832](https://nvd.nist.gov/vuln/detail/CVE-2015-1832) |
| CVE-2016-5018 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2016-5018](https://nvd.nist.gov/vuln/detail/CVE-2016-5018) |
| CVE-2017-15095 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2017-15095](https://nvd.nist.gov/vuln/detail/CVE-2017-15095) |
| CVE-2017-17485 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2017-17485](https://nvd.nist.gov/vuln/detail/CVE-2017-17485) |
| CVE-2017-7525 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2017-7525](https://nvd.nist.gov/vuln/detail/CVE-2017-7525) |
| CVE-2018-11307 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-11307](https://nvd.nist.gov/vuln/detail/CVE-2018-11307) |
| CVE-2018-11307 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-11307](https://nvd.nist.gov/vuln/detail/CVE-2018-11307) |
| CVE-2018-14718 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-14718](https://nvd.nist.gov/vuln/detail/CVE-2018-14718) |
| CVE-2018-14718 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-14718](https://nvd.nist.gov/vuln/detail/CVE-2018-14718) |
| CVE-2018-14719 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-14719](https://nvd.nist.gov/vuln/detail/CVE-2018-14719) |
| CVE-2018-14719 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-14719](https://nvd.nist.gov/vuln/detail/CVE-2018-14719) |
| CVE-2018-14720 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-14720](https://nvd.nist.gov/vuln/detail/CVE-2018-14720) |
| CVE-2018-14720 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-14720](https://nvd.nist.gov/vuln/detail/CVE-2018-14720) |
| CVE-2018-14721 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-14721](https://nvd.nist.gov/vuln/detail/CVE-2018-14721) |
| CVE-2018-14721 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-14721](https://nvd.nist.gov/vuln/detail/CVE-2018-14721) |
| CVE-2018-19360 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-19360](https://nvd.nist.gov/vuln/detail/CVE-2018-19360) |
| CVE-2018-19360 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-19360](https://nvd.nist.gov/vuln/detail/CVE-2018-19360) |
| CVE-2018-19361 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-19361](https://nvd.nist.gov/vuln/detail/CVE-2018-19361) |
| CVE-2018-19361 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-19361](https://nvd.nist.gov/vuln/detail/CVE-2018-19361) |
| CVE-2018-19362 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-19362](https://nvd.nist.gov/vuln/detail/CVE-2018-19362) |
| CVE-2018-19362 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-19362](https://nvd.nist.gov/vuln/detail/CVE-2018-19362) |
| CVE-2018-7489 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-7489](https://nvd.nist.gov/vuln/detail/CVE-2018-7489) |
| CVE-2018-7489 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-7489](https://nvd.nist.gov/vuln/detail/CVE-2018-7489) |
| CVE-2019-10202 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-10202](https://nvd.nist.gov/vuln/detail/CVE-2019-10202) |
| CVE-2019-14379 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14379](https://nvd.nist.gov/vuln/detail/CVE-2019-14379) |
| CVE-2019-14379 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14379](https://nvd.nist.gov/vuln/detail/CVE-2019-14379) |
| CVE-2019-14540 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14540](https://nvd.nist.gov/vuln/detail/CVE-2019-14540) |
| CVE-2019-14540 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14540](https://nvd.nist.gov/vuln/detail/CVE-2019-14540) |
| CVE-2019-14892 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14892](https://nvd.nist.gov/vuln/detail/CVE-2019-14892) |
| CVE-2019-14892 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14892](https://nvd.nist.gov/vuln/detail/CVE-2019-14892) |
| CVE-2019-14893 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14893](https://nvd.nist.gov/vuln/detail/CVE-2019-14893) |
| CVE-2019-14893 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14893](https://nvd.nist.gov/vuln/detail/CVE-2019-14893) |
| CVE-2019-16335 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-16335](https://nvd.nist.gov/vuln/detail/CVE-2019-16335) |
| CVE-2019-16335 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-16335](https://nvd.nist.gov/vuln/detail/CVE-2019-16335) |
| CVE-2019-16942 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-16942](https://nvd.nist.gov/vuln/detail/CVE-2019-16942) |
| CVE-2019-16942 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-16942](https://nvd.nist.gov/vuln/detail/CVE-2019-16942) |
| CVE-2019-16943 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-16943](https://nvd.nist.gov/vuln/detail/CVE-2019-16943) |
| CVE-2019-16943 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-16943](https://nvd.nist.gov/vuln/detail/CVE-2019-16943) |
| CVE-2019-17267 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-17267](https://nvd.nist.gov/vuln/detail/CVE-2019-17267) |
| CVE-2019-17267 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-17267](https://nvd.nist.gov/vuln/detail/CVE-2019-17267) |
| CVE-2019-17531 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-17531](https://nvd.nist.gov/vuln/detail/CVE-2019-17531) |
| CVE-2019-17531 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-17531](https://nvd.nist.gov/vuln/detail/CVE-2019-17531) |
| CVE-2019-20330 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-20330](https://nvd.nist.gov/vuln/detail/CVE-2019-20330) |
| CVE-2019-20330 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-20330](https://nvd.nist.gov/vuln/detail/CVE-2019-20330) |
| CVE-2020-8840 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8840](https://nvd.nist.gov/vuln/detail/CVE-2020-8840) |
| CVE-2020-8840 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8840](https://nvd.nist.gov/vuln/detail/CVE-2020-8840) |
| CVE-2020-9546 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-9546](https://nvd.nist.gov/vuln/detail/CVE-2020-9546) |
| CVE-2020-9546 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-9546](https://nvd.nist.gov/vuln/detail/CVE-2020-9546) |
| CVE-2020-9547 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-9547](https://nvd.nist.gov/vuln/detail/CVE-2020-9547) |
| CVE-2020-9547 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-9547](https://nvd.nist.gov/vuln/detail/CVE-2020-9547) |
| CVE-2020-9548 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-9548](https://nvd.nist.gov/vuln/detail/CVE-2020-9548) |
| CVE-2020-9548 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-9548](https://nvd.nist.gov/vuln/detail/CVE-2020-9548) |
| CVE-2022-1471 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-1471](https://nvd.nist.gov/vuln/detail/CVE-2022-1471) |
| CVE-2022-1471 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-1471](https://nvd.nist.gov/vuln/detail/CVE-2022-1471) |
| CVE-2022-37865 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-37865](https://nvd.nist.gov/vuln/detail/CVE-2022-37865) |
| CVE-2022-39135 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-39135](https://nvd.nist.gov/vuln/detail/CVE-2022-39135) |
| CVE-2022-46337 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-46337](https://nvd.nist.gov/vuln/detail/CVE-2022-46337) |
| CVE-2022-46337 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-46337](https://nvd.nist.gov/vuln/detail/CVE-2022-46337) |
| CVE-2024-51504 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2024-51504](https://nvd.nist.gov/vuln/detail/CVE-2024-51504) |
| CVE-2024-51504 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2024-51504](https://nvd.nist.gov/vuln/detail/CVE-2024-51504) |
| CVE-2024-52046 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2024-52046](https://nvd.nist.gov/vuln/detail/CVE-2024-52046) |
| CVE-2024-52046 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2024-52046](https://nvd.nist.gov/vuln/detail/CVE-2024-52046) |
| CVE-2024-53990 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2024-53990](https://nvd.nist.gov/vuln/detail/CVE-2024-53990) |
| CVE-2025-30065 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2025-30065](https://nvd.nist.gov/vuln/detail/CVE-2025-30065) |
| CVE-2014-3643 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2014-3643](https://nvd.nist.gov/vuln/detail/CVE-2014-3643) |
| CVE-2015-5237 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2015-5237](https://nvd.nist.gov/vuln/detail/CVE-2015-5237) |
| CVE-2015-5237 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2015-5237](https://nvd.nist.gov/vuln/detail/CVE-2015-5237) |
| CVE-2016-6796 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2016-6796](https://nvd.nist.gov/vuln/detail/CVE-2016-6796) |
| CVE-2018-1000180 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-1000180](https://nvd.nist.gov/vuln/detail/CVE-2018-1000180) |
| CVE-2018-1000180 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-1000180](https://nvd.nist.gov/vuln/detail/CVE-2018-1000180) |
| CVE-2018-12022 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-12022](https://nvd.nist.gov/vuln/detail/CVE-2018-12022) |
| CVE-2018-12022 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-12022](https://nvd.nist.gov/vuln/detail/CVE-2018-12022) |
| CVE-2018-12023 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-12023](https://nvd.nist.gov/vuln/detail/CVE-2018-12023) |
| CVE-2018-12023 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-12023](https://nvd.nist.gov/vuln/detail/CVE-2018-12023) |
| CVE-2018-5968 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-5968](https://nvd.nist.gov/vuln/detail/CVE-2018-5968) |
| CVE-2019-0205 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-0205](https://nvd.nist.gov/vuln/detail/CVE-2019-0205) |
| CVE-2019-0205 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-0205](https://nvd.nist.gov/vuln/detail/CVE-2019-0205) |
| CVE-2019-10172 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-10172](https://nvd.nist.gov/vuln/detail/CVE-2019-10172) |
| CVE-2019-12086 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-12086](https://nvd.nist.gov/vuln/detail/CVE-2019-12086) |
| CVE-2019-12086 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-12086](https://nvd.nist.gov/vuln/detail/CVE-2019-12086) |
| CVE-2019-14439 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14439](https://nvd.nist.gov/vuln/detail/CVE-2019-14439) |
| CVE-2019-14439 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14439](https://nvd.nist.gov/vuln/detail/CVE-2019-14439) |
| CVE-2020-10650 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10650](https://nvd.nist.gov/vuln/detail/CVE-2020-10650) |
| CVE-2020-10650 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10650](https://nvd.nist.gov/vuln/detail/CVE-2020-10650) |
| CVE-2020-10672 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10672](https://nvd.nist.gov/vuln/detail/CVE-2020-10672) |
| CVE-2020-10672 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10672](https://nvd.nist.gov/vuln/detail/CVE-2020-10672) |
| CVE-2020-10673 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10673](https://nvd.nist.gov/vuln/detail/CVE-2020-10673) |
| CVE-2020-10673 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10673](https://nvd.nist.gov/vuln/detail/CVE-2020-10673) |
| CVE-2020-10968 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10968](https://nvd.nist.gov/vuln/detail/CVE-2020-10968) |
| CVE-2020-10968 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10968](https://nvd.nist.gov/vuln/detail/CVE-2020-10968) |
| CVE-2020-10969 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10969](https://nvd.nist.gov/vuln/detail/CVE-2020-10969) |
| CVE-2020-10969 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10969](https://nvd.nist.gov/vuln/detail/CVE-2020-10969) |
| CVE-2020-11111 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11111](https://nvd.nist.gov/vuln/detail/CVE-2020-11111) |
| CVE-2020-11111 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11111](https://nvd.nist.gov/vuln/detail/CVE-2020-11111) |
| CVE-2020-11112 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11112](https://nvd.nist.gov/vuln/detail/CVE-2020-11112) |
| CVE-2020-11112 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11112](https://nvd.nist.gov/vuln/detail/CVE-2020-11112) |
| CVE-2020-11113 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11113](https://nvd.nist.gov/vuln/detail/CVE-2020-11113) |
| CVE-2020-11113 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11113](https://nvd.nist.gov/vuln/detail/CVE-2020-11113) |
| CVE-2020-11619 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11619](https://nvd.nist.gov/vuln/detail/CVE-2020-11619) |
| CVE-2020-11619 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11619](https://nvd.nist.gov/vuln/detail/CVE-2020-11619) |
| CVE-2020-11620 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11620](https://nvd.nist.gov/vuln/detail/CVE-2020-11620) |
| CVE-2020-11620 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11620](https://nvd.nist.gov/vuln/detail/CVE-2020-11620) |
| CVE-2020-13949 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-13949](https://nvd.nist.gov/vuln/detail/CVE-2020-13949) |
| CVE-2020-13949 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-13949](https://nvd.nist.gov/vuln/detail/CVE-2020-13949) |
| CVE-2020-13949 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-13949](https://nvd.nist.gov/vuln/detail/CVE-2020-13949) |
| CVE-2020-14060 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14060](https://nvd.nist.gov/vuln/detail/CVE-2020-14060) |
| CVE-2020-14060 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14060](https://nvd.nist.gov/vuln/detail/CVE-2020-14060) |
| CVE-2020-14061 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14061](https://nvd.nist.gov/vuln/detail/CVE-2020-14061) |
| CVE-2020-14061 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14061](https://nvd.nist.gov/vuln/detail/CVE-2020-14061) |
| CVE-2020-14062 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14062](https://nvd.nist.gov/vuln/detail/CVE-2020-14062) |
| CVE-2020-14062 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14062](https://nvd.nist.gov/vuln/detail/CVE-2020-14062) |
| CVE-2020-14195 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14195](https://nvd.nist.gov/vuln/detail/CVE-2020-14195) |
| CVE-2020-14195 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14195](https://nvd.nist.gov/vuln/detail/CVE-2020-14195) |
| CVE-2020-24616 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-24616](https://nvd.nist.gov/vuln/detail/CVE-2020-24616) |
| CVE-2020-24616 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-24616](https://nvd.nist.gov/vuln/detail/CVE-2020-24616) |
| CVE-2020-24750 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-24750](https://nvd.nist.gov/vuln/detail/CVE-2020-24750) |
| CVE-2020-24750 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-24750](https://nvd.nist.gov/vuln/detail/CVE-2020-24750) |
| CVE-2020-25649 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-25649](https://nvd.nist.gov/vuln/detail/CVE-2020-25649) |
| CVE-2020-28052 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-28052](https://nvd.nist.gov/vuln/detail/CVE-2020-28052) |
| CVE-2020-35490 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-35490](https://nvd.nist.gov/vuln/detail/CVE-2020-35490) |
| CVE-2020-35490 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-35490](https://nvd.nist.gov/vuln/detail/CVE-2020-35490) |
| CVE-2020-35491 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-35491](https://nvd.nist.gov/vuln/detail/CVE-2020-35491) |
| CVE-2020-35491 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-35491](https://nvd.nist.gov/vuln/detail/CVE-2020-35491) |
| CVE-2020-35728 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-35728](https://nvd.nist.gov/vuln/detail/CVE-2020-35728) |
| CVE-2020-35728 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-35728](https://nvd.nist.gov/vuln/detail/CVE-2020-35728) |
| CVE-2020-36179 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36179](https://nvd.nist.gov/vuln/detail/CVE-2020-36179) |
| CVE-2020-36179 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36179](https://nvd.nist.gov/vuln/detail/CVE-2020-36179) |
| CVE-2020-36180 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36180](https://nvd.nist.gov/vuln/detail/CVE-2020-36180) |
| CVE-2020-36180 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36180](https://nvd.nist.gov/vuln/detail/CVE-2020-36180) |
| CVE-2020-36181 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36181](https://nvd.nist.gov/vuln/detail/CVE-2020-36181) |
| CVE-2020-36181 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36181](https://nvd.nist.gov/vuln/detail/CVE-2020-36181) |
| CVE-2020-36182 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36182](https://nvd.nist.gov/vuln/detail/CVE-2020-36182) |
| CVE-2020-36182 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36182](https://nvd.nist.gov/vuln/detail/CVE-2020-36182) |
| CVE-2020-36183 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36183](https://nvd.nist.gov/vuln/detail/CVE-2020-36183) |
| CVE-2020-36183 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36183](https://nvd.nist.gov/vuln/detail/CVE-2020-36183) |
| CVE-2020-36184 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36184](https://nvd.nist.gov/vuln/detail/CVE-2020-36184) |
| CVE-2020-36184 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36184](https://nvd.nist.gov/vuln/detail/CVE-2020-36184) |
| CVE-2020-36185 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36185](https://nvd.nist.gov/vuln/detail/CVE-2020-36185) |
| CVE-2020-36185 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36185](https://nvd.nist.gov/vuln/detail/CVE-2020-36185) |
| CVE-2020-36186 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36186](https://nvd.nist.gov/vuln/detail/CVE-2020-36186) |
| CVE-2020-36186 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36186](https://nvd.nist.gov/vuln/detail/CVE-2020-36186) |
| CVE-2020-36187 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36187](https://nvd.nist.gov/vuln/detail/CVE-2020-36187) |
| CVE-2020-36187 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36187](https://nvd.nist.gov/vuln/detail/CVE-2020-36187) |
| CVE-2020-36188 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36188](https://nvd.nist.gov/vuln/detail/CVE-2020-36188) |
| CVE-2020-36188 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36188](https://nvd.nist.gov/vuln/detail/CVE-2020-36188) |
| CVE-2020-36189 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36189](https://nvd.nist.gov/vuln/detail/CVE-2020-36189) |
| CVE-2020-36189 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36189](https://nvd.nist.gov/vuln/detail/CVE-2020-36189) |
| CVE-2020-36518 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36518](https://nvd.nist.gov/vuln/detail/CVE-2020-36518) |
| CVE-2020-36518 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36518](https://nvd.nist.gov/vuln/detail/CVE-2020-36518) |
| CVE-2021-0341 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-0341](https://nvd.nist.gov/vuln/detail/CVE-2021-0341) |
| CVE-2021-20190 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-20190](https://nvd.nist.gov/vuln/detail/CVE-2021-20190) |
| CVE-2021-20190 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-20190](https://nvd.nist.gov/vuln/detail/CVE-2021-20190) |
| CVE-2021-31684 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-31684](https://nvd.nist.gov/vuln/detail/CVE-2021-31684) |
| CVE-2021-34538 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-34538](https://nvd.nist.gov/vuln/detail/CVE-2021-34538) |
| CVE-2021-34538 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-34538](https://nvd.nist.gov/vuln/detail/CVE-2021-34538) |
| CVE-2021-34538 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-34538](https://nvd.nist.gov/vuln/detail/CVE-2021-34538) |
| CVE-2022-25647 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-25647](https://nvd.nist.gov/vuln/detail/CVE-2022-25647) |
| CVE-2022-25647 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-25647](https://nvd.nist.gov/vuln/detail/CVE-2022-25647) |
| CVE-2022-25857 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-25857](https://nvd.nist.gov/vuln/detail/CVE-2022-25857) |
| CVE-2022-3171 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3171](https://nvd.nist.gov/vuln/detail/CVE-2022-3171) |
| CVE-2022-3171 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3171](https://nvd.nist.gov/vuln/detail/CVE-2022-3171) |
| CVE-2022-3509 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3509](https://nvd.nist.gov/vuln/detail/CVE-2022-3509) |
| CVE-2022-3509 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3509](https://nvd.nist.gov/vuln/detail/CVE-2022-3509) |
| CVE-2022-3510 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3510](https://nvd.nist.gov/vuln/detail/CVE-2022-3510) |
| CVE-2022-36364 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-36364](https://nvd.nist.gov/vuln/detail/CVE-2022-36364) |
| CVE-2022-37866 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-37866](https://nvd.nist.gov/vuln/detail/CVE-2022-37866) |
| CVE-2022-40149 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-40149](https://nvd.nist.gov/vuln/detail/CVE-2022-40149) |
| CVE-2022-40149 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-40149](https://nvd.nist.gov/vuln/detail/CVE-2022-40149) |
| CVE-2022-40150 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-40150](https://nvd.nist.gov/vuln/detail/CVE-2022-40150) |
| CVE-2022-40150 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-40150](https://nvd.nist.gov/vuln/detail/CVE-2022-40150) |
| CVE-2022-41404 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-41404](https://nvd.nist.gov/vuln/detail/CVE-2022-41404) |
| CVE-2022-42003 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42003](https://nvd.nist.gov/vuln/detail/CVE-2022-42003) |
| CVE-2022-42003 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42003](https://nvd.nist.gov/vuln/detail/CVE-2022-42003) |
| CVE-2022-42003 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42003](https://nvd.nist.gov/vuln/detail/CVE-2022-42003) |
| CVE-2022-42003 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42003](https://nvd.nist.gov/vuln/detail/CVE-2022-42003) |
| CVE-2022-42003 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42003](https://nvd.nist.gov/vuln/detail/CVE-2022-42003) |
| CVE-2022-42004 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42004](https://nvd.nist.gov/vuln/detail/CVE-2022-42004) |
| CVE-2022-42004 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42004](https://nvd.nist.gov/vuln/detail/CVE-2022-42004) |
| CVE-2022-42004 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42004](https://nvd.nist.gov/vuln/detail/CVE-2022-42004) |
| CVE-2022-42004 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42004](https://nvd.nist.gov/vuln/detail/CVE-2022-42004) |
| CVE-2022-45685 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-45685](https://nvd.nist.gov/vuln/detail/CVE-2022-45685) |
| CVE-2022-45685 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-45685](https://nvd.nist.gov/vuln/detail/CVE-2022-45685) |
| CVE-2022-45693 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-45693](https://nvd.nist.gov/vuln/detail/CVE-2022-45693) |
| CVE-2022-45693 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-45693](https://nvd.nist.gov/vuln/detail/CVE-2022-45693) |
| CVE-2022-46751 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-46751](https://nvd.nist.gov/vuln/detail/CVE-2022-46751) |
| CVE-2022-46751 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-46751](https://nvd.nist.gov/vuln/detail/CVE-2022-46751) |
| CVE-2023-1370 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-1370](https://nvd.nist.gov/vuln/detail/CVE-2023-1370) |
| CVE-2023-1436 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-1436](https://nvd.nist.gov/vuln/detail/CVE-2023-1436) |
| CVE-2023-1436 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-1436](https://nvd.nist.gov/vuln/detail/CVE-2023-1436) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-6378 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-6378](https://nvd.nist.gov/vuln/detail/CVE-2023-6378) |
| CVE-2023-6378 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-6378](https://nvd.nist.gov/vuln/detail/CVE-2023-6378) |
| CVE-2023-6481 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-6481](https://nvd.nist.gov/vuln/detail/CVE-2023-6481) |
| CVE-2023-6481 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-6481](https://nvd.nist.gov/vuln/detail/CVE-2023-6481) |
| CVE-2024-13009 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-13009](https://nvd.nist.gov/vuln/detail/CVE-2024-13009) |
| CVE-2024-13009 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-13009](https://nvd.nist.gov/vuln/detail/CVE-2024-13009) |
| CVE-2024-29857 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-29857](https://nvd.nist.gov/vuln/detail/CVE-2024-29857) |
| CVE-2024-29857 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-29857](https://nvd.nist.gov/vuln/detail/CVE-2024-29857) |
| CVE-2024-29857 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-29857](https://nvd.nist.gov/vuln/detail/CVE-2024-29857) |
| CVE-2024-29857 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-29857](https://nvd.nist.gov/vuln/detail/CVE-2024-29857) |
| CVE-2024-30172 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-30172](https://nvd.nist.gov/vuln/detail/CVE-2024-30172) |
| CVE-2024-30172 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-30172](https://nvd.nist.gov/vuln/detail/CVE-2024-30172) |
| CVE-2024-34447 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-34447](https://nvd.nist.gov/vuln/detail/CVE-2024-34447) |
| CVE-2024-34447 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-34447](https://nvd.nist.gov/vuln/detail/CVE-2024-34447) |
| CVE-2024-36114 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-36114](https://nvd.nist.gov/vuln/detail/CVE-2024-36114) |
| CVE-2024-7254 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-7254](https://nvd.nist.gov/vuln/detail/CVE-2024-7254) |
| CVE-2024-7254 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-7254](https://nvd.nist.gov/vuln/detail/CVE-2024-7254) |
| CVE-2024-7254 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-7254](https://nvd.nist.gov/vuln/detail/CVE-2024-7254) |
| CVE-2024-7254 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-7254](https://nvd.nist.gov/vuln/detail/CVE-2024-7254) |
| CVE-2024-7254 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-7254](https://nvd.nist.gov/vuln/detail/CVE-2024-7254) |
| CVE-2024-7254 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-7254](https://nvd.nist.gov/vuln/detail/CVE-2024-7254) |
| CVE-2024-7254 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-7254](https://nvd.nist.gov/vuln/detail/CVE-2024-7254) |
| CVE-2024-9823 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-9823](https://nvd.nist.gov/vuln/detail/CVE-2024-9823) |
| CVE-2025-24970 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-24970](https://nvd.nist.gov/vuln/detail/CVE-2025-24970) |
| CVE-2025-24970 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-24970](https://nvd.nist.gov/vuln/detail/CVE-2025-24970) |
| CVE-2025-27553 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-27553](https://nvd.nist.gov/vuln/detail/CVE-2025-27553) |
| CVE-2025-27817 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-27817](https://nvd.nist.gov/vuln/detail/CVE-2025-27817) |
| CVE-2025-46762 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-46762](https://nvd.nist.gov/vuln/detail/CVE-2025-46762) |
| CVE-2025-46762 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-46762](https://nvd.nist.gov/vuln/detail/CVE-2025-46762) |
| CVE-2025-48734 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-48734](https://nvd.nist.gov/vuln/detail/CVE-2025-48734) |
| CVE-2025-52434 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-52434](https://nvd.nist.gov/vuln/detail/CVE-2025-52434) |
| CVE-2025-52999 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-52999](https://nvd.nist.gov/vuln/detail/CVE-2025-52999) |
| CVE-2025-52999 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-52999](https://nvd.nist.gov/vuln/detail/CVE-2025-52999) |
| CVE-2025-52999 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-52999](https://nvd.nist.gov/vuln/detail/CVE-2025-52999) |
| CVE-2025-52999 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-52999](https://nvd.nist.gov/vuln/detail/CVE-2025-52999) |
| CVE-2025-52999 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-52999](https://nvd.nist.gov/vuln/detail/CVE-2025-52999) |
| CVE-2025-52999 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-52999](https://nvd.nist.gov/vuln/detail/CVE-2025-52999) |
| CVE-2025-55163 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-55163](https://nvd.nist.gov/vuln/detail/CVE-2025-55163) |
| CVE-2025-55163 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-55163](https://nvd.nist.gov/vuln/detail/CVE-2025-55163) |
| CVE-2025-55163 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-55163](https://nvd.nist.gov/vuln/detail/CVE-2025-55163) |
| CVE-2025-58056 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-58056](https://nvd.nist.gov/vuln/detail/CVE-2025-58056) |
| CVE-2025-58056 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-58056](https://nvd.nist.gov/vuln/detail/CVE-2025-58056) |
| CVE-2025-58056 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-58056](https://nvd.nist.gov/vuln/detail/CVE-2025-58056) |
| CVE-2025-58056 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-58056](https://nvd.nist.gov/vuln/detail/CVE-2025-58056) |
| CVE-2025-58057 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-58057](https://nvd.nist.gov/vuln/detail/CVE-2025-58057) |
| CVE-2025-58057 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-58057](https://nvd.nist.gov/vuln/detail/CVE-2025-58057) |
| CVE-2025-58057 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-58057](https://nvd.nist.gov/vuln/detail/CVE-2025-58057) |
| CVE-2025-58057 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-58057](https://nvd.nist.gov/vuln/detail/CVE-2025-58057) |
| CVE-2025-58057 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-58057](https://nvd.nist.gov/vuln/detail/CVE-2025-58057) |
| CVE-2025-59250 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-59250](https://nvd.nist.gov/vuln/detail/CVE-2025-59250) |
| CVE-2012-5783 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2012-5783](https://nvd.nist.gov/vuln/detail/CVE-2012-5783) |
| CVE-2012-5783 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2012-5783](https://nvd.nist.gov/vuln/detail/CVE-2012-5783) |
| CVE-2012-6153 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2012-6153](https://nvd.nist.gov/vuln/detail/CVE-2012-6153) |
| CVE-2012-6153 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2012-6153](https://nvd.nist.gov/vuln/detail/CVE-2012-6153) |
| CVE-2018-10237 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2018-10237](https://nvd.nist.gov/vuln/detail/CVE-2018-10237) |
| CVE-2018-10237 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2018-10237](https://nvd.nist.gov/vuln/detail/CVE-2018-10237) |
| CVE-2018-10237 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2018-10237](https://nvd.nist.gov/vuln/detail/CVE-2018-10237) |
| CVE-2018-10237 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2018-10237](https://nvd.nist.gov/vuln/detail/CVE-2018-10237) |
| CVE-2018-10237 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2018-10237](https://nvd.nist.gov/vuln/detail/CVE-2018-10237) |
| CVE-2018-11798 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2018-11798](https://nvd.nist.gov/vuln/detail/CVE-2018-11798) |
| CVE-2018-1313 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2018-1313](https://nvd.nist.gov/vuln/detail/CVE-2018-1313) |
| CVE-2019-12384 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2019-12384](https://nvd.nist.gov/vuln/detail/CVE-2019-12384) |
| CVE-2019-12384 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2019-12384](https://nvd.nist.gov/vuln/detail/CVE-2019-12384) |
| CVE-2019-12814 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2019-12814](https://nvd.nist.gov/vuln/detail/CVE-2019-12814) |
| CVE-2019-12814 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2019-12814](https://nvd.nist.gov/vuln/detail/CVE-2019-12814) |
| CVE-2020-13955 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-13955](https://nvd.nist.gov/vuln/detail/CVE-2020-13955) |
| CVE-2020-13956 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-13956](https://nvd.nist.gov/vuln/detail/CVE-2020-13956) |
| CVE-2020-15250 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-15250](https://nvd.nist.gov/vuln/detail/CVE-2020-15250) |
| CVE-2020-15250 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-15250](https://nvd.nist.gov/vuln/detail/CVE-2020-15250) |
| CVE-2020-15522 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-15522](https://nvd.nist.gov/vuln/detail/CVE-2020-15522) |
| CVE-2020-15522 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-15522](https://nvd.nist.gov/vuln/detail/CVE-2020-15522) |
| CVE-2020-15522 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-15522](https://nvd.nist.gov/vuln/detail/CVE-2020-15522) |
| CVE-2020-17521 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-17521](https://nvd.nist.gov/vuln/detail/CVE-2020-17521) |
| CVE-2020-17521 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-17521](https://nvd.nist.gov/vuln/detail/CVE-2020-17521) |
| CVE-2020-1945 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-1945](https://nvd.nist.gov/vuln/detail/CVE-2020-1945) |
| CVE-2020-26939 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-26939](https://nvd.nist.gov/vuln/detail/CVE-2020-26939) |
| CVE-2020-26939 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-26939](https://nvd.nist.gov/vuln/detail/CVE-2020-26939) |
| CVE-2020-26939 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-26939](https://nvd.nist.gov/vuln/detail/CVE-2020-26939) |
| CVE-2021-22569 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2021-22569](https://nvd.nist.gov/vuln/detail/CVE-2021-22569) |
| CVE-2021-22569 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2021-22569](https://nvd.nist.gov/vuln/detail/CVE-2021-22569) |
| CVE-2021-27568 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2021-27568](https://nvd.nist.gov/vuln/detail/CVE-2021-27568) |
| CVE-2021-28170 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2021-28170](https://nvd.nist.gov/vuln/detail/CVE-2021-28170) |
| CVE-2021-29425 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2021-29425](https://nvd.nist.gov/vuln/detail/CVE-2021-29425) |
| CVE-2021-36373 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2021-36373](https://nvd.nist.gov/vuln/detail/CVE-2021-36373) |
| CVE-2021-36374 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2021-36374](https://nvd.nist.gov/vuln/detail/CVE-2021-36374) |
| CVE-2022-38749 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2022-38749](https://nvd.nist.gov/vuln/detail/CVE-2022-38749) |
| CVE-2022-38750 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2022-38750](https://nvd.nist.gov/vuln/detail/CVE-2022-38750) |
| CVE-2022-38751 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2022-38751](https://nvd.nist.gov/vuln/detail/CVE-2022-38751) |
| CVE-2022-38752 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2022-38752](https://nvd.nist.gov/vuln/detail/CVE-2022-38752) |
| CVE-2022-41854 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2022-41854](https://nvd.nist.gov/vuln/detail/CVE-2022-41854) |
| CVE-2023-0833 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-0833](https://nvd.nist.gov/vuln/detail/CVE-2023-0833) |
| CVE-2023-33201 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-33201](https://nvd.nist.gov/vuln/detail/CVE-2023-33201) |
| CVE-2023-33201 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-33201](https://nvd.nist.gov/vuln/detail/CVE-2023-33201) |
| CVE-2023-33201 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-33201](https://nvd.nist.gov/vuln/detail/CVE-2023-33201) |
| CVE-2023-33201 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-33201](https://nvd.nist.gov/vuln/detail/CVE-2023-33201) |
| CVE-2023-33202 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-33202](https://nvd.nist.gov/vuln/detail/CVE-2023-33202) |
| CVE-2023-33202 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-33202](https://nvd.nist.gov/vuln/detail/CVE-2023-33202) |
| CVE-2023-33202 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-33202](https://nvd.nist.gov/vuln/detail/CVE-2023-33202) |
| CVE-2023-33202 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-33202](https://nvd.nist.gov/vuln/detail/CVE-2023-33202) |
| CVE-2023-42503 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-42503](https://nvd.nist.gov/vuln/detail/CVE-2023-42503) |
| CVE-2023-51074 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-51074](https://nvd.nist.gov/vuln/detail/CVE-2023-51074) |
| CVE-2024-12798 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-12798](https://nvd.nist.gov/vuln/detail/CVE-2024-12798) |
| CVE-2024-12798 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-12798](https://nvd.nist.gov/vuln/detail/CVE-2024-12798) |
| CVE-2024-12798 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-12798](https://nvd.nist.gov/vuln/detail/CVE-2024-12798) |
| CVE-2024-12798 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-12798](https://nvd.nist.gov/vuln/detail/CVE-2024-12798) |
| CVE-2024-12798 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-12798](https://nvd.nist.gov/vuln/detail/CVE-2024-12798) |
| CVE-2024-12798 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-12798](https://nvd.nist.gov/vuln/detail/CVE-2024-12798) |
| CVE-2024-23944 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-23944](https://nvd.nist.gov/vuln/detail/CVE-2024-23944) |
| CVE-2024-23945 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-23945](https://nvd.nist.gov/vuln/detail/CVE-2024-23945) |
| CVE-2024-23945 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-23945](https://nvd.nist.gov/vuln/detail/CVE-2024-23945) |
| CVE-2024-23953 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-23953](https://nvd.nist.gov/vuln/detail/CVE-2024-23953) |
| CVE-2024-23953 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-23953](https://nvd.nist.gov/vuln/detail/CVE-2024-23953) |
| CVE-2024-25710 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-25710](https://nvd.nist.gov/vuln/detail/CVE-2024-25710) |
| CVE-2024-25710 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-25710](https://nvd.nist.gov/vuln/detail/CVE-2024-25710) |
| CVE-2024-26308 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-26308](https://nvd.nist.gov/vuln/detail/CVE-2024-26308) |
| CVE-2024-26308 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-26308](https://nvd.nist.gov/vuln/detail/CVE-2024-26308) |
| CVE-2024-29025 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-29025](https://nvd.nist.gov/vuln/detail/CVE-2024-29025) |
| CVE-2024-29869 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-29869](https://nvd.nist.gov/vuln/detail/CVE-2024-29869) |
| CVE-2024-29869 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-29869](https://nvd.nist.gov/vuln/detail/CVE-2024-29869) |
| CVE-2024-30171 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-30171](https://nvd.nist.gov/vuln/detail/CVE-2024-30171) |
| CVE-2024-30171 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-30171](https://nvd.nist.gov/vuln/detail/CVE-2024-30171) |
| CVE-2024-30171 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-30171](https://nvd.nist.gov/vuln/detail/CVE-2024-30171) |
| CVE-2024-30171 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-30171](https://nvd.nist.gov/vuln/detail/CVE-2024-30171) |
| CVE-2024-31141 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-31141](https://nvd.nist.gov/vuln/detail/CVE-2024-31141) |
| CVE-2024-47535 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-47535](https://nvd.nist.gov/vuln/detail/CVE-2024-47535) |
| CVE-2024-47535 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-47535](https://nvd.nist.gov/vuln/detail/CVE-2024-47535) |
| CVE-2024-47554 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-47554](https://nvd.nist.gov/vuln/detail/CVE-2024-47554) |
| CVE-2024-47554 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-47554](https://nvd.nist.gov/vuln/detail/CVE-2024-47554) |
| CVE-2024-47554 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-47554](https://nvd.nist.gov/vuln/detail/CVE-2024-47554) |
| CVE-2024-56128 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-56128](https://nvd.nist.gov/vuln/detail/CVE-2024-56128) |
| CVE-2024-6763 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-6763](https://nvd.nist.gov/vuln/detail/CVE-2024-6763) |
| CVE-2024-6763 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-6763](https://nvd.nist.gov/vuln/detail/CVE-2024-6763) |
| CVE-2024-6763 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-6763](https://nvd.nist.gov/vuln/detail/CVE-2024-6763) |
| CVE-2024-6763 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-6763](https://nvd.nist.gov/vuln/detail/CVE-2024-6763) |
| CVE-2024-6763 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-6763](https://nvd.nist.gov/vuln/detail/CVE-2024-6763) |
| CVE-2024-8184 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-8184](https://nvd.nist.gov/vuln/detail/CVE-2024-8184) |
| CVE-2025-11226 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-11226](https://nvd.nist.gov/vuln/detail/CVE-2025-11226) |
| CVE-2025-11226 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-11226](https://nvd.nist.gov/vuln/detail/CVE-2025-11226) |
| CVE-2025-11226 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-11226](https://nvd.nist.gov/vuln/detail/CVE-2025-11226) |
| CVE-2025-25193 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-25193](https://nvd.nist.gov/vuln/detail/CVE-2025-25193) |
| CVE-2025-25193 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-25193](https://nvd.nist.gov/vuln/detail/CVE-2025-25193) |
| CVE-2025-30474 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-30474](https://nvd.nist.gov/vuln/detail/CVE-2025-30474) |
| CVE-2025-3588 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-3588](https://nvd.nist.gov/vuln/detail/CVE-2025-3588) |
| CVE-2025-46392 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-46392](https://nvd.nist.gov/vuln/detail/CVE-2025-46392) |
| CVE-2025-48924 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-48924](https://nvd.nist.gov/vuln/detail/CVE-2025-48924) |
| CVE-2025-48924 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-48924](https://nvd.nist.gov/vuln/detail/CVE-2025-48924) |
| CVE-2025-48924 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-48924](https://nvd.nist.gov/vuln/detail/CVE-2025-48924) |
| CVE-2025-48924 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-48924](https://nvd.nist.gov/vuln/detail/CVE-2025-48924) |
| CVE-2025-48924 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-48924](https://nvd.nist.gov/vuln/detail/CVE-2025-48924) |
| CVE-2025-48924 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-48924](https://nvd.nist.gov/vuln/detail/CVE-2025-48924) |
| CVE-2025-48924 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-48924](https://nvd.nist.gov/vuln/detail/CVE-2025-48924) |
| CVE-2025-48924 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-48924](https://nvd.nist.gov/vuln/detail/CVE-2025-48924) |
| CVE-2025-48924 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-48924](https://nvd.nist.gov/vuln/detail/CVE-2025-48924) |
| CVE-2025-49128 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-49128](https://nvd.nist.gov/vuln/detail/CVE-2025-49128) |
| CVE-2025-49128 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-49128](https://nvd.nist.gov/vuln/detail/CVE-2025-49128) |
| CVE-2025-49128 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-49128](https://nvd.nist.gov/vuln/detail/CVE-2025-49128) |
| CVE-2025-53864 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-53864](https://nvd.nist.gov/vuln/detail/CVE-2025-53864) |
| CVE-2025-58457 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-58457](https://nvd.nist.gov/vuln/detail/CVE-2025-58457) |
| CVE-2025-58457 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-58457](https://nvd.nist.gov/vuln/detail/CVE-2025-58457) |
| CVE-2025-59419 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-59419](https://nvd.nist.gov/vuln/detail/CVE-2025-59419) |
| CVE-2025-8885 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-8885](https://nvd.nist.gov/vuln/detail/CVE-2025-8885) |
| CVE-2025-8885 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-8885](https://nvd.nist.gov/vuln/detail/CVE-2025-8885) |
| CVE-2025-8916 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-8916](https://nvd.nist.gov/vuln/detail/CVE-2025-8916) |
| CVE-2025-8916 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-8916](https://nvd.nist.gov/vuln/detail/CVE-2025-8916) |
| CVE-2025-8916 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-8916](https://nvd.nist.gov/vuln/detail/CVE-2025-8916) |
| CVE-2025-8916 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-8916](https://nvd.nist.gov/vuln/detail/CVE-2025-8916) |
| CVE-2020-8908 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8908](https://nvd.nist.gov/vuln/detail/CVE-2020-8908) |
| CVE-2020-8908 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8908](https://nvd.nist.gov/vuln/detail/CVE-2020-8908) |
| CVE-2020-8908 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8908](https://nvd.nist.gov/vuln/detail/CVE-2020-8908) |
| CVE-2020-8908 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8908](https://nvd.nist.gov/vuln/detail/CVE-2020-8908) |
| CVE-2020-8908 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8908](https://nvd.nist.gov/vuln/detail/CVE-2020-8908) |
| CVE-2020-8908 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8908](https://nvd.nist.gov/vuln/detail/CVE-2020-8908) |
| CVE-2020-8908 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8908](https://nvd.nist.gov/vuln/detail/CVE-2020-8908) |
| CVE-2020-8908 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8908](https://nvd.nist.gov/vuln/detail/CVE-2020-8908) |
| CVE-2020-8908 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8908](https://nvd.nist.gov/vuln/detail/CVE-2020-8908) |
| CVE-2024-12801 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-12801](https://nvd.nist.gov/vuln/detail/CVE-2024-12801) |
| CVE-2024-12801 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-12801](https://nvd.nist.gov/vuln/detail/CVE-2024-12801) |
| CVE-2024-12801 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-12801](https://nvd.nist.gov/vuln/detail/CVE-2024-12801) |
| CVE-2025-46551 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-46551](https://nvd.nist.gov/vuln/detail/CVE-2025-46551) |
## 7.11.0 릴리스 정보
다음 릴리스 정보에는 Amazon EMR 릴리스 7.11.0에 대한 정보가 포함되어 있습니다.
+ **새로운 기능**
+ **애플리케이션 업그레이드** - Amazon EMR 7.11.0 애플리케이션 업그레이드에는 Delta 3.3.2-amzn-0, Flink 1.20.0-amzn-5, HBase 2.6.2-amzn-2, HCatalog 3.1.3-amzn-20, Hadoop 3.4.1-amzn-3, Hive 3.1.3-amzn-20, Hudi 1.0.2-amzn-0, Iceberg 1.9.1-amzn-0, Presto 0.287-amzn-5, Spark 3.5.6-amzn-0, TensorFlow 2.19.0, Tez 0.18-amzn-10이 포함됩니다 ZooKeeper .
+ Amazon EMR on EC2에서 이제 IAM Identity Center 사용자 백그라운드 세션 지원
+ **사용자 백그라운드 세션**: 사용자가 SageMaker Unified Studio에서 로그오프한 후에도 장기 실행 Spark 워크로드가 계속 실행되도록 하여 최대 90일의 세션 지원
+ **유연한 백그라운드 세션 구성**: 사용자 지정 가능한 백그라운드 세션 기간이 15분\$190일(기본값: 7일)인 2단계 구성(IAM Identity Center 인스턴스 및 Amazon EMR-EC2 클러스터)
+ **신뢰할 수 있는 자격 증명 전파**: Amazon EMR의 신뢰할 수 있는 자격 증명 전파 기능을 사용하여 백그라운드 세션 수명 주기 동안 보안 자격 증명 컨텍스트를 유지합니다.
+ **SageMaker Unified Studio 통합**: SageMaker Unified Studio의 Livy 대화형 세션을 통해 시작된 백그라운드 세션
+ **기업 자격 증명이 있는 장기 실행 세션** - Amazon SageMaker Unified Studio는 이제 IAM Identity Center의 신뢰할 수 있는 자격 증명 전파(TIP)를 통해 기업 자격 증명이 있는 장기 실행 세션을 지원합니다. 사용자는 로그오프되거나 세션이 만료되더라도 회사 자격 증명을 사용하여 지속되는 Amazon EMR 및 AWS Glue에서 대화형 노트북 및 데이터 처리 세션을 시작할 수 있습니다. 세션은 자격 증명 권한과 일관된 보안 제어를 유지하면서 최대 90일(기본값 7일) 동안 실행됩니다.
## 7.11.0 기본 Java 버전
Amazon EMR 릴리스 7.11.0은 Apache Livy를 제외하고 Corretto 17(OpenJDK)을 지원하는 애플리케이션에 기본적으로 Amazon Corretto 17(OpenJDK 기반)과 함께 제공됩니다.
다음 표에는 Amazon EMR 7.11.0의 애플리케이션에 대한 기본 Java 버전이 나와 있습니다.
| 애플리케이션 | Java 및 Amazon Corretto 버전(기본값은 굵은체로 표시) |
| --- | --- |
| 델타 | 17, 11, 8 |
| Flink | 17, 11, 8 |
| HBase | 17, 11, 8 |
| HCatalog | 17, 11, 8 |
| Hadoop | 17, 11, 8 |
| Hive | 17, 11, 8 |
| Hudi | 17, 11, 8 |
| Iceberg | 17, 11 |
| Livy | 17, 11, 8 |
| Oozie | 17, 11, 8 |
| 피닉스 | 17, 11, 8 |
| PrestoDB | 8 |
| Spark | 17, 11, 8 |
| Spark RAPIDS | 17, 11, 8 |
| Tez의 Hive 실행 시간 비교 | 17, 11, 8 |
| Trino | 21, 17 |
| Zeppelin | 17, 11, 8 |
| Pig | 17, 11, 8 |
| Zookeeper | 17, 11, 8 |
## 7.11.0 구성 요소 버전
이 릴리스를 통해 Amazon EMR이 설치하는 구성 요소는 다음과 같습니다. 일부는 빅 데이터 애플리케이션 패키지의 일부로 설치됩니다. 나머지는 Amazon EMR에 고유하며 시스템 프로세스 및 기능을 위해 설치됩니다. 이는 일반적으로 `emr` 또는 `aws`로 시작됩니다. 최근 Amazon EMR 릴리스의 빅 데이터 애플리케이션 패키지는 일반적으로 커뮤니티에서 발견된 최신 버전입니다. 가능한 한 빨리 Amazon EMR에서 커뮤니티 릴리스를 제공합니다.
Amazon EMR의 일부 구성 요소는 커뮤니티 버전과 다릅니다. 이러한 구성 요소에는 `CommunityVersion-amzn-EmrVersion` 양식의 버전 레이블이 있습니다. `EmrVersion`은 0에서 시작합니다. 예를 들어, 버전 2.2의 `myapp-component`라는 오픈 소스 커뮤니티 구성 요소가 다른 Amazon EMR 릴리스에 포함되도록 세 번 수정된 경우 해당 릴리스 버전은 `2.2-amzn-2`로 나열됩니다.
| 구성 요소 | 버전 | 설명 |
| --- | --- | --- |
| adot-java-agent | 1.31.0 | 애플리케이션 대몬(daemon)에서 지표를 수집하는 Java 에이전트입니다. |
| delta | 3.3.2-amzn-0 | Delta Lake는 방대한 분석 데이터 세트를 위한 오픈 테이블 형식입니다. |
| emr-amazon-cloudwatch-agent | 1.300032.2-amzn-0 | Amazon EC2 인스턴스에서 내부 시스템 수준 지표와 사용자 지정 애플리케이션 지표를 수집하는 애플리케이션입니다. |
| emr-ddb | 5.7.0 | 하둡 에코시스템 애플리케이션용 Amazon DynamoDB 커넥터 |
| emr-goodies | 3.20.0 | 편리한 하둡 에코시스템용 추가 라이브러리 |
| emr-kinesis | 3.24.0 | 하둡 에코시스템 애플리케이션용 Amazon Kinesis 커넥터. |
| emr-notebook-env | 1.18.0 | Jupyter Enterprise Gateway가 포함된 EMR 노트북용 Conda 환경 |
| emr-s3-dist-cp | 2.41.0 | Amazon S3용으로 최적화된 분사 복사 애플리케이션. |
| emr-s3-select | 2.20.0 | EMR S3Select 커넥터 |
| emr-wal-cli | 1.3.5 | emrwal 목록/삭제에 사용되는 CLI입니다. |
| emrfs | 2.72.0 | 하둡 에코시스템 애플리케이션용 Amazon S3 커넥터. |
| flink-client | 1.20.0-amzn-5 | Apache Flink 명령줄 클라이언트 스크립트 및 애플리케이션 |
| flink-jobmanager-config | 1.20.0-amzn-5 | Apache Flink JobManager에 대한 EMR 노드에서 리소스를 관리합니다. |
| hadoop-client | 3.4.1-amzn-3 | 'hdfs', 'hadoop', 'yarn' 등과 같은 하둡 명령줄 클라이언트 |
| hadoop-hdfs-datanode | 3.4.1-amzn-3 | 블록을 저장하는 HDFS 노드 수준 서비스 |
| hadoop-hdfs-library | 3.4.1-amzn-3 | HDFS 명령줄 클라이언트 및 라이브러리 |
| hadoop-hdfs-namenode | 3.4.1-amzn-3 | 파일 이름 및 블록 위치를 추적하는 HDFS 서비스 |
| hadoop-hdfs-zkfc | 3.4.1-amzn-3 | HA 모드의 네임노드를 추적하기 위한 ZKFC 서비스입니다. |
| hadoop-hdfs-journalnode | 3.4.1-amzn-3 | HA 클러스터에서 하둡 파일 시스템 저널을 관리하기 위한 HDFS 서비스 |
| hadoop-httpfs-server | 3.4.1-amzn-3 | HDFS 작업에 대한 HTTP 엔드포인트 |
| hadoop-kms-server | 3.4.1-amzn-3 | 하둡의 KeyProvider API를 기반으로 하는 암호화 키 관리 서버 |
| hadoop-mapred | 3.4.1-amzn-3 | MapReduce 애플리케이션을 실행하는 MapReduce 실행 엔진 라이브러리 |
| hadoop-yarn-nodemanager | 3.4.1-amzn-3 | 개별 노드의 컨테이너를 관리하는 YARN 서비스 |
| hadoop-yarn-resourcemanager | 3.4.1-amzn-3 | 클러스터 리소스 및 분산 애플리케이션을 할당 및 관리하는 YARN 서비스 |
| hadoop-yarn-timeline-server | 3.4.1-amzn-3 | YARN 애플리케이션의 현재 및 기록 정보를 가져오는 서비스 |
| hbase-hmaster | 2.6.2-amzn-2 | 리전 조정 및 관리 명령의 실행을 담당하는 HBase 클러스터용 서비스 |
| hbase-region-server | 2.6.2-amzn-2 | 한 개 이상의 HBase 리전에 서비스를 제공하는 서비스 |
| hbase-client | 2.6.2-amzn-2 | HBase 명령줄 클라이언트 |
| hbase-rest-server | 2.6.2-amzn-2 | HBase용 RESTful HTTP 엔드포인트를 제공하는 서비스 |
| hbase-thrift-server | 2.6.2-amzn-2 | HBase에 Thrift 엔드포인트를 제공하는 서비스 |
| hbase-operator-tools | 2.6.2-amzn-2 | Apache HBase 클러스터용 복구 도구. |
| hcatalog-client | 3.1.3-amzn-20 | hcatalog-server를 조정하기 위한 'hcat' 명령줄 클라이언트 |
| hcatalog-server | 3.1.3-amzn-20 | 분산 애플리케이션용 스토리지 관리 계층, 테이블 및 HCatalog를 제공하는 서비스 |
| hcatalog-webhcat-server | 3.1.3-amzn-20 | HCatalog에 REST 인터페이스를 제공하는 HTTP 엔드포인트 |
| hive-client | 3.1.3-amzn-20 | Hive 명령줄 클라이언트 |
| hive-hbase | 3.1.3-amzn-20 | Hive-hbase 클라이언트 |
| hive-metastore-server | 3.1.3-amzn-20 | 하둡 작업에 대한 SQL용 메타데이터가 저장되는 시맨틱 리포지토리인 Hive 메타스토어에 액세스하기 위한 서비스 |
| hive-server2 | 3.1.3-amzn-20 | Hive 쿼리를 웹 요청으로 수락하기 위한 서비스 |
| hudi | 1.0.2-amzn-0 | 짧은 지연 시간 및 높은 효율성으로 데이터 파이프라인을 구동하는 증분 처리 프레임워크. |
| hudi-presto | 1.0.2-amzn-0 | Hudi로 Presto를 실행하기 위한 번들 라이브러리. |
| hudi-trino | 1.0.2-amzn-0 | Hudi와 함께 Trnio를 실행하기 위한 번들 라이브러리. |
| hudi-spark | 1.0.2-amzn-0 | Hudi와 함께 Spark를 실행하기 위한 번들 라이브러리. |
| hue-server | 4.11.0 | 하둡 에코시스템 애플리케이션을 사용하여 데이터를 분석하는 웹 애플리케이션. |
| iceberg | 1.9.1-amzn-0 | Apache Iceberg는 방대한 분석 데이터 세트를 위한 오픈 테이블 형식입니다. |
| jupyterhub | 1.5.0 | Jupyter Notebook용 다중 사용자 서버 |
| livy-server | 0.8.0-incubating | Apache Spark와 상호작용하기 위한 REST 인터페이스 |
| nginx | 1.12.1 | HTTP인 nginx [engine x] 및 역방향 프록시 서버 |
| mariadb-server | 5.5.68 이상 | MariaDB 데이터베이스 서버. |
| nvidia-cuda | 12.5.0 | Nvidia 드라이버와 Cuda 도구 키트 |
| oozie-client | 5.2.1 | Oozie 명령줄 클라이언트 |
| oozie-server | 5.2.1 | Oozie 워크플로 요청을 수락하는 서비스 |
| opencv | 4.7.0 | 오픈 소스 컴퓨터 비전 라이브러리. |
| phoenix-library | 5.2.1 | 서버 및 클라이언트의 phoenix 라이브러리 |
| phoenix-connectors | 6.0.0 | Spark-3용 Apache Phoenix 커넥터 |
| phoenix-query-server | 6.0.0 | Avatica API에 대한 JSON 형식 액세스 및 프로토콜 버퍼 액세스를 비롯하여 JDBC 액세스를 제공하는 경량 서버 |
| presto-coordinator | 0.287-amzn-5 | presto-worker의 쿼리를 수락하고 쿼리 실행을 관리하는 서비스. |
| presto-worker | 0.287-amzn-5 | 여러 쿼리를 실행하는 서비스. |
| presto-client | 0.287-amzn-5 | Presto 서버가 시작되지 않은 HA 클러스터의 대기 마스터에 설치된 Presto 명령줄 클라이언트. |
| trino-coordinator | 475-amzn-0 | trino-workers의 쿼리를 수락하고 쿼리 실행을 관리하는 서비스. |
| trino-worker | 475-amzn-0 | 여러 쿼리를 실행하는 서비스. |
| trino-client | 475-amzn-0 | Trino 서버가 시작되지 않은 HA 클러스터의 대기 마스터에 설치된 Trino 명령줄 클라이언트. |
| pig-client | 0.17.0 | Pig 명령줄 클라이언트. |
| r | 4.3.2 | 통계 컴퓨팅용 R 프로젝트 |
| ranger-kms-server | 2.0.0 | Apache Ranger 키 관리 시스템 |
| spark-client | 3.5.6-amzn-0 | Spark 명령줄 클라이언트. |
| spark-history-server | 3.5.6-amzn-0 | 완료된 Spark 애플리케이션의 수명에 대해 기록된 이벤트를 조회하는 웹 UI. |
| spark-on-yarn | 3.5.6-amzn-0 | YARN용 인 메모리 실행 엔진. |
| spark-yarn-slave | 3.5.6-amzn-0 | YARN 슬레이브에서 필요한 Apache Spark 라이브러리. |
| spark-rapids | 25.06.0-amzn-0 | GPU로 Apache Spark를 가속화하는 Nvidia Spark RAPIDS 플러그인. |
| tensorflow | 2.19.0 | TensorFlow는 고성능 수치 계산용 오픈 소스 소프트웨어 라이브러리입니다. |
| tez-on-yarn | 0.10.2-amzn-18 | tez YARN 애플리케이션 및 라이브러리. |
| tez-on-worker | 0.10.2-amzn-18 | 워커 노드에 대한 tez YARN 애플리케이션 및 라이브러리. |
| zeppelin-server | 0.11.1 | 대화형 데이터 분석이 가능한 웹 기반 노트북 |
| zookeeper-server | 3.9.3-amzn-3 | 구성 정보 유지 관리, 이름 지정, 분산 동기화 제공 및 그룹 서비스 제공을 위한 중앙 집중식 서비스. |
| zookeeper-client | 3.9.3-amzn-3 | ZooKeeper 명령줄 클라이언트. |
## 7.11.0 구성 분류
구성 분류를 사용하면 애플리케이션을 사용자 지정할 수 있습니다. 이는 종종 `hive-site.xml`과 같이 애플리케이션의 구성 XML 파일에 해당합니다. 자세한 내용은 [애플리케이션 구성](emr-configure-apps.md) 단원을 참조하십시오.
재구성 작업은 실행 중인 클러스터의 인스턴스 그룹에 대한 구성을 지정할 때 수행됩니다. Amazon EMR은 사용자가 수정한 분류에 대한 재구성 작업만 시작합니다. 자세한 내용은 [실행 중인 클러스터에서 인스턴스 그룹 재구성](emr-configure-apps-running-cluster.md) 단원을 참조하십시오.
**emr-7.11.0 분류**
| 분류 | 설명 | 재구성 작업 |
| --- | --- | --- |
| capacity-scheduler | Hadoop capacity-scheduler.xml 파일에서 값을 변경합니다. | Restarts the ResourceManager service. |
| container-executor | Hadoop YARN container-executor.cfg 파일에서 값을 변경합니다. | Not available. |
| container-log4j | Hadoop YARN container-log4j.properties 파일에서 값을 변경합니다. | Not available. |
| core-site | Hadoop core-site.xml 파일에서 값을 변경합니다. | Restarts the Hadoop HDFS services Namenode, SecondaryNamenode, Datanode, ZKFC, and Journalnode. Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts Hadoop KMS, Ranger KMS, HiveServer2, Hive MetaStore, Hadoop Httpfs, and MapReduce-HistoryServer. |
| docker-conf | Docker 관련 설정을 변경합니다. | Not available. |
| emrfs-site | EMRFS 설정을 변경합니다. | Restarts the Hadoop HDFS services Namenode, SecondaryNamenode, Datanode, ZKFC, and Journalnode. Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts HBaseRegionserver, HBaseMaster, HBaseThrift, HBaseRest, HiveServer2, Hive MetaStore, Hadoop Httpfs, and MapReduce-HistoryServer. |
| flink-conf | flink-conf.yaml 설정을 변경합니다. | Restarts Flink history server. |
| flink-log4j | Flink log4j.properties 설정을 변경합니다. | Restarts Flink history server. |
| flink-log4j-session | Kubernetes 및 Yarn 세션에 대한 Flink log4j-session.properties 설정을 변경합니다. | Restarts Flink history server. |
| flink-log4j-cli | Flink log4j-cli.properties 설정을 변경합니다. | Restarts Flink history server. |
| hadoop-env | 모든 Hadoop 구성 요소에 대한 Hadoop 환경에서 값을 변경합니다. | Restarts the Hadoop HDFS services Namenode, SecondaryNamenode, Datanode, ZKFC, and Journalnode. Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts PhoenixQueryserver, HiveServer2, Hive MetaStore, and MapReduce-HistoryServer. |
| hadoop-log4j | Hadoop log4j.properties 파일에서 값을 변경합니다. | Restarts the Hadoop HDFS services SecondaryNamenode, Datanode, and Journalnode. Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts Hadoop KMS, Hadoop Httpfs, and MapReduce-HistoryServer. |
| hadoop-ssl-server | hadoop ssl 서버 구성을 변경합니다. | Not available. |
| hadoop-ssl-client | hadoop ssl 클라이언트 구성을 변경합니다. | Not available. |
| hbase | Apache HBase에 대한 Amazon EMR 큐레이트 설정입니다. | Custom EMR specific property. Sets emrfs-site and hbase-site configs. See those for their associated restarts. |
| hbase-env | HBase 환경에서 값을 변경합니다. | Restarts the HBase services RegionServer, HBaseMaster, ThriftServer, RestServer. |
| hbase-log4j2 | HBase hbase-log4j.properties 파일에서 값을 변경합니다. | Restarts the HBase services RegionServer, HBaseMaster, ThriftServer, RestServer. |
| hbase-metrics | HBase hadoop-metrics2-hbase.properties 파일에서 값을 변경합니다. | Restarts the HBase services RegionServer, HBaseMaster, ThriftServer, RestServer. |
| hbase-policy | HBase hbase-policy.xml 파일에서 값을 변경합니다. | Not available. |
| hbase-site | HBase hbase-site.xml 파일에서 값을 변경합니다. | Restarts the HBase services RegionServer, HBaseMaster, ThriftServer, RestServer. Additionally restarts Phoenix QueryServer. |
| hdfs-encryption-zones | HDFS 암호화 영역을 구성합니다. | This classification should not be reconfigured. |
| hdfs-env | HDFS 환경에서 값을 변경합니다. | Restarts Hadoop HDFS services Namenode, Datanode, and ZKFC. |
| hdfs-site | HDFS hdfs-site.xml에서 값을 변경합니다. | Restarts the Hadoop HDFS services Namenode, SecondaryNamenode, Datanode, ZKFC, and Journalnode. Additionally restarts Hadoop Httpfs. |
| hcatalog-env | HCatalog 환경에서 값을 변경합니다. | Restarts Hive HCatalog Server. |
| hcatalog-server-jndi | HCatalog jndi.properties 환경에서 값을 변경합니다. | Restarts Hive HCatalog Server. |
| hcatalog-server-proto-hive-site | HCatalog proto-hive-site.xml에서 값을 변경합니다. | Restarts Hive HCatalog Server. |
| hcatalog-webhcat-env | HCatalog WebHCat 환경에서 값을 변경합니다. | Restarts Hive WebHCat server. |
| hcatalog-webhcat-log4j2 | HCatalog WebHCat log4j2.properties에서 값을 변경합니다. | Restarts Hive WebHCat server. |
| hcatalog-webhcat-site | HCatalog WebHCat webhcat-site.xml 파일에서 값을 변경합니다. | Restarts Hive WebHCat server. |
| hive | Apache Hive에 대한 Amazon EMR 큐레이트 설정입니다. | Sets configurations to launch Hive LLAP service. |
| hive-beeline-log4j2 | Hive beeline-log4j2.properties 파일에서 값을 변경합니다. | Not available. |
| hive-parquet-logging | Hive parquet-logging.properties 파일에서 값을 변경합니다. | Not available. |
| hive-env | Hive 환경에서 값을 변경합니다. | Restarts HiveServer2, HiveMetastore, and Hive HCatalog-Server. Runs Hive schemaTool CLI commands to verify hive-metastore. |
| hive-exec-log4j2 | Hive hive-exec-log4j2.properties 파일에서 값을 변경합니다. | Not available. |
| hive-llap-daemon-log4j2 | Hive llap-daemon-log4j2.properties 파일에서 값을 변경합니다. | Not available. |
| hive-log4j2 | Hive hive-log4j2.properties 파일에서 값을 변경합니다. | Not available. |
| hive-site | Hive hive-site.xml 파일에서 값을 변경합니다. | Restarts HiveServer2, HiveMetastore, and Hive HCatalog-Server. Runs Hive schemaTool CLI commands to verify hive-metastore. Also restarts Oozie and Zeppelin. |
| hiveserver2-site | Hive Server2 hiveserver2-site.xml 파일에서 값을 변경합니다. | Not available. |
| hue-ini | Hue ini 파일에서 값을 변경합니다. | Restarts Hue. Also activates Hue config override CLI commands to pick up new configurations. |
| httpfs-env | HTTPFS 환경에서 값을 변경합니다. | Restarts Hadoop Httpfs service. |
| httpfs-site | Hadoop httpfs-site.xml 파일에서 값을 변경합니다. | Restarts Hadoop Httpfs service. |
| hadoop-kms-acls | Hadoop kms-acls.xml 파일에서 값을 변경합니다. | Not available. |
| hadoop-kms-env | Hadoop KMS 환경에서 값을 변경합니다. | Restarts Hadoop-KMS service. |
| hadoop-kms-java-home | Hadoop의 KMS java 홈 변경 | Not available. |
| hadoop-kms-log4j | Hadoop kms-log4j.properties 파일에서 값을 변경합니다. | Not available. |
| hadoop-kms-site | Hadoop kms-site.xml 파일에서 값을 변경합니다. | Restarts Hadoop-KMS and Ranger-KMS service. |
| hudi-env | Hudi 환경에서 값을 변경합니다. | Not available. |
| hudi-defaults | Hudi hudi-defaults.conf 파일에서 값을 변경합니다. | Not available. |
| iceberg-defaults | Iceberg iceberg-defaults.conf 파일에서 값을 변경합니다. | Not available. |
| delta-defaults | Delta delta-defaults.conf 파일에서 값을 변경합니다. | Not available. |
| jupyter-notebook-conf | Jupyter Notebook jupyter\$1notebook\$1config.py 파일에서 값을 변경합니다. | Not available. |
| jupyter-hub-conf | JupyterHubs jupyterhub\$1config.py 파일에서 값을 변경합니다. | Not available. |
| jupyter-s3-conf | Jupyter Notebook S3 지속성 구성 | Not available. |
| jupyter-sparkmagic-conf | Sparkmagic config.json 파일에서 값을 변경합니다. | Not available. |
| livy-conf | Livy livy.conf 파일에서 값을 변경합니다. | Restarts Livy Server. |
| livy-env | Livy 환경에서 값을 변경합니다. | Restarts Livy Server. |
| livy-log4j2 | Livy log4j2.properties 설정을 변경합니다. | Restarts Livy Server. |
| mapred-env | MapReduce 애플리케이션 환경에서 값을 변경합니다. | Restarts Hadoop MapReduce-HistoryServer. |
| mapred-site | MapReduce 애플리케이션 mapred-site.xml 파일에서 값을 변경합니다. | Restarts Hadoop MapReduce-HistoryServer. |
| oozie-env | Oozie 환경에서 값을 변경합니다. | Restarts Oozie. |
| oozie-log4j | Oozie oozie-log4j.properties 파일에서 값을 변경합니다. | Restarts Oozie. |
| oozie-site | Oozie oozie-site.xml 파일에서 값을 변경합니다. | Restarts Oozie. |
| phoenix-hbase-metrics | Phoenix hadoop-metrics2-hbase.properties 파일에서 값을 변경합니다. | Not available. |
| phoenix-hbase-site | Phoenix hbase-site.xml 파일에서 값을 변경합니다. | Not available. |
| phoenix-log4j2 | Phoenix log4j2.properties 파일에서 값을 변경합니다. | Restarts Phoenix-QueryServer. |
| phoenix-metrics | Phoenix hadoop-metrics2-phoenix.properties 파일에서 값을 변경합니다. | Not available. |
| pig-env | Pig 환경에서 값을 변경합니다. | Not available. |
| pig-properties | Pig pig.properties 파일에서 값을 변경합니다. | Restarts Oozie. |
| pig-log4j | Pig log4j.properties 파일에서 값을 변경합니다. | Not available. |
| presto-log | Presto log.properties 파일에서 값을 변경합니다. | Restarts Presto-Server (for PrestoDB) |
| presto-config | Presto config.properties 파일에서 값을 변경합니다. | Restarts Presto-Server (for PrestoDB) |
| presto-password-authenticator | Presto password-authenticator.properties 파일에서 값을 변경합니다. | Not available. |
| presto-env | Presto presto-env.sh 파일에서 값을 변경합니다. | Restarts Presto-Server (for PrestoDB) |
| presto-node | Presto node.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-blackhole | Presto blackhole.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-cassandra | Presto cassandra.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-hive | Presto hive.properties 파일에서 값을 변경합니다. | Restarts Presto-Server (for PrestoDB) |
| presto-connector-jmx | Presto jmx.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-kafka | Presto kafka.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-lakeformation | Presto lakeformation.properties 파일에서 값을 변경합니다. | Restarts Presto-Server (for PrestoDB) |
| presto-connector-localfile | Presto localfile.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-memory | Presto memory.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-mongodb | Presto mongodb.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-mysql | Presto mysql.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-postgresql | Presto postgresql.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-raptor | Presto raptor.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-redis | Presto redis.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-redshift | Presto redshift.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-tpch | Presto tpch.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-tpcds | Presto tpcds.properties 파일에서 값을 변경합니다. | Not available. |
| trino-log | Trino log.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-config | Trino config.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-password-authenticator | Trino password-authenticator.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-env | Trino trino-env.sh 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-node | Trino node.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-blackhole | Trino blackhole.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-cassandra | Trino cassandra.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-delta | Trino delta.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-connector-hive | Trino hive.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-exchange-manager | Trino exchange-manager.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-connector-iceberg | Trino iceberg.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-connector-hudi | Trino hudi.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-connector-jmx | Trino jmx.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-kafka | Trino kafka.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-localfile | Trino localfile.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-memory | Trino memory.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-mongodb | Trino mongodb.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-mysql | Trino mysql.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-postgresql | Trino postgresql.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-raptor | Trino raptor.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-redis | Trino redis.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-redshift | Trino redshift.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-tpch | Trino tpch.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-tpcds | Trino tpcds.properties 파일에서 값을 변경합니다. | Not available. |
| ranger-kms-dbks-site | Ranger KMS dbks-site.xml 파일에서 값을 변경합니다. | Restarts Ranger KMS Server. |
| ranger-kms-site | Ranger KMS ranger-kms-site.xml 파일에서 값을 변경합니다. | Restarts Ranger KMS Server. |
| ranger-kms-env | Ranger KMS 환경에서 값을 변경합니다. | Restarts Ranger KMS Server. |
| ranger-kms-logback | Ranger KMS kms-logback.xml 파일에서 값을 변경합니다. | Not available. |
| ranger-kms-db-ca | Ranger KMS와의 MySQL SSL 연결에서 CA 파일의 값을 변경합니다. | Not available. |
| spark | Apache Spark에 대한 Amazon EMR 큐레이트 설정입니다. | This property modifies spark-defaults. See actions there. |
| spark-defaults | Spark spark-defaults.conf 파일에서 값을 변경합니다. | Restarts Spark history server and Spark thrift server. |
| spark-env | Spark 환경에서 값을 변경합니다. | Restarts Spark history server and Spark thrift server. |
| spark-hive-site | Spark hive-site.xml 파일에서 값을 변경합니다. | Not available. |
| spark-log4j2 | Spark log4j2.properties 파일에서 값을 변경합니다. | Restarts Spark history server and Spark thrift server. |
| spark-metrics | Spark metrics.properties 파일에서 값을 변경합니다. | Restarts Spark history server and Spark thrift server. |
| tez-site | Tez tez-site.xml 파일에서 값을 변경합니다. | Restart Oozie and HiveServer2. |
| yarn-env | YARN 환경에서 값을 변경합니다. | Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts MapReduce-HistoryServer. |
| yarn-site | YARN yarn-site.xml 파일에서 값을 변경합니다. | Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts Livy Server and MapReduce-HistoryServer. |
| zeppelin-env | Zeppelin 환경에서 값을 변경합니다. | Restarts Zeppelin. |
| zeppelin-site | zeppelin-site.xml에서 구성 설정을 변경합니다. | Restarts Zeppelin. |
| zookeeper-config | ZooKeeper zoo.cfg 파일에서 값을 변경합니다. | Restarts Zookeeper server. |
| zookeeper-logback | ZooKeeper logback.xml 파일에서 값을 변경합니다. | Restarts Zookeeper server. |
| cloudwatch-logs | EMR 클러스터 노드에 대한 CloudWatch Logs 통합을 구성합니다. | Not available. |
| emr-metrics | 이 노드에 대한 emr 지표 설정을 변경합니다. | Restarts the CloudWatchAgent service. |
## 7.11.0 변경 로그
**7.11.0 릴리스 및 릴리스 정보에 대한 변경 로그**
| Date | 이벤트 | 설명 |
| --- | --- | --- |
| 2025-11-12 | 문서 게시 | Amazon EMR 7.11.0 릴리스 정보 최초 게시 |
# Amazon EMR 릴리스 7.10.0
## 7.10.0 지원 수명 주기
다음 표에서는 Amazon EMR 릴리스 7.10.0에서 지원되는 수명 주기 날짜를 설명합니다.
| 지원 단계 | Date |
| --- | --- |
| 초기 릴리스 날짜 | 2025년 8월 15일 |
| 표준 지원 종료 시점 | 2027년 8월 15일 |
| 지원 종료 | 2027년 8월 16일 |
| 수명 종료 | 2028년 8월 15일 |
## 7.10.0 애플리케이션 버전
이 릴리스에 포함된 애플리케이션은 [https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Install-CloudWatch-Agent.html](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Install-CloudWatch-Agent.html), [https://delta.io/](https://delta.io/), [https://flink.apache.org/](https://flink.apache.org/), [http://hbase.apache.org/](http://hbase.apache.org/), [https://cwiki.apache.org/confluence/display/Hive/HCatalog](https://cwiki.apache.org/confluence/display/Hive/HCatalog), [http://hadoop.apache.org/docs/current/](http://hadoop.apache.org/docs/current/), [http://hive.apache.org/](http://hive.apache.org/), [https://hudi.apache.org](https://hudi.apache.org), [http://gethue.com/](http://gethue.com/), [https://iceberg.apache.org/](https://iceberg.apache.org/), [https://jupyter-enterprise-gateway.readthedocs.io/en/latest/](https://jupyter-enterprise-gateway.readthedocs.io/en/latest/), [https://jupyterhub.readthedocs.io/en/latest/#](https://jupyterhub.readthedocs.io/en/latest/#), [https://livy.incubator.apache.org/](https://livy.incubator.apache.org/), [http://oozie.apache.org/](http://oozie.apache.org/), [https://phoenix.apache.org/](https://phoenix.apache.org/), [http://pig.apache.org/](http://pig.apache.org/), [https://prestodb.io/](https://prestodb.io/), [https://spark.apache.org/docs/latest/](https://spark.apache.org/docs/latest/), [https://www.tensorflow.org/](https://www.tensorflow.org/), [https://tez.apache.org/](https://tez.apache.org/), [https://trino.io/](https://trino.io/), [https://zeppelin.incubator.apache.org/](https://zeppelin.incubator.apache.org/), [https://zookeeper.apache.org](https://zookeeper.apache.org)입니다.
아래 테이블에는 이번 Amazon EMR 릴리스에서 사용할 수 있는 애플리케이션 버전과 이전 세 가지 Amazon EMR 릴리스(해당하는 경우)의 애플리케이션 버전이 나와 있습니다.
각 Amazon EMR 릴리스에서 애플리케이션 버전의 전체 기록은 다음 주제를 참조하세요.
+ [Amazon EMR 7.x 릴리스의 애플리케이션 버전](emr-release-app-versions-7.x.md)
+ [Amazon EMR 6.x 릴리스의 애플리케이션 버전](emr-release-app-versions-6.x.md)
+ [Amazon EMR 5.x 릴리스의 애플리케이션 버전](emr-release-app-versions-5.x.md)
+ [Amazon EMR 4.x 릴리스의 애플리케이션 버전](emr-release-app-versions-4.x.md)
**애플리케이션 버전 정보**
| | emr-7.10.0 | emr-7.9.0 | emr-7.8.0 | emr-7.7.0 |
| --- | --- | --- | --- | --- |
| AWS Java용 SDK | 2.31.48, 1.12.782 | 2.31.16, 1.12.782 | 2.29.52, 1.12.780 | 2.29.44, 1.12.780 |
| Python | 3.9, 3.11 | 3.9, 3.11 | 3.9, 3.11 | 3.9, 3.11 |
| Scala | 2.12.18 | 2.12.18 | 2.12.18 | 2.12.18 |
| AmazonCloudWatchAgent | 1.300032.2-amzn-0 | 1.300032.2-amzn-0 | 1.300032.2-amzn-0 | 1.300032.2-amzn-0 |
| Delta | 3.3.0-amzn-2 | 3.3.0-amzn-1 | 3.3.0-amzn-0 | 3.2.1-amzn-2 |
| Flink | 1.20.0-amzn-4 | 1.20.0-amzn-3 | 1.20.0-amzn-2 | 1.20.0-amzn-1 |
| Ganglia | - | - | - | - |
| HBase | 2.6.2-amzn-1 | 2.6.2-amzn-0 | 2.6.1-amzn-2 | 2.6.1-amzn-1 |
| HCatalog | 3.1.3-amzn-19 | 3.1.3-amzn-18 | 3.1.3-amzn-17 | 3.1.3-amzn-16 |
| Hadoop | 3.4.1-amzn-2 | 3.4.1-amzn-1 | 3.4.1-amzn-0 | 3.4.0-amzn-3 |
| Hive | 3.1.3-amzn-19 | 3.1.3-amzn-18 | 3.1.3-amzn-17 | 3.1.3-amzn-16 |
| Hudi | 0.15.0-amzn-7 | 0.15.0-amzn-6 | 0.15.0-amzn-5 | 0.15.0-amzn-4 |
| Hue | 4.11.0 | 4.11.0 | 4.11.0 | 4.11.0 |
| Iceberg | 1.8.1-amzn-0 | 1.7.1-amzn-2 | 1.7.1-amzn-1 | 1.7.1-amzn-0 |
| JupyterEnterpriseGateway | 2.6.0 | 2.6.0 | 2.6.0 | 2.6.0 |
| JupyterHub | 1.5.0 | 1.5.0 | 1.5.0 | 1.5.0 |
| Livy | 0.8.0-incubating | 0.8.0-incubating | 0.8.0-incubating | 0.8.0-incubating |
| MXNet | - | - | - | - |
| Mahout | - | - | - | - |
| Oozie | 5.2.1 | 5.2.1 | 5.2.1 | 5.2.1 |
| Phoenix | 5.2.1 | 5.2.1 | 5.2.1 | 5.2.1 |
| Pig | 0.17.0 | 0.17.0 | 0.17.0 | 0.17.0 |
| Presto | 0.287-amzn-4 | 0.287-amzn-3 | 0.287-amzn-2 | 0.287-amzn-1 |
| Spark | 3.5.5-amzn-1 | 3.5.5-amzn-0 | 3.5.4-amzn-0 | 3.5.3-amzn-1 |
| Sqoop | - | - | - | - |
| TensorFlow | 2.18.0 | 2.16.1 | 2.16.1 | 2.16.1 |
| Tez | 0.10.2-amzn-17 | 0.10.2-amzn-16 | 0.10.2-amzn-15 | 0.10.2-amzn-14 |
| Trino (PrestoSQL) | 470-amzn-0 | 467-amzn-2 | 467-amzn-1 | 467-amzn-0 |
| Zeppelin | 0.11.1 | 0.11.1 | 0.11.1 | 0.11.1 |
| ZooKeeper | 3.9.3-amzn-2 | 3.9.3-amzn-1 | 3.9.3-amzn-0 | 3.9.2-amzn-1 |
# 7.10.0 일반적인 취약성 및 노출
다음 표에는 Amazon EMR 7.10.0의 권장 구성에서 실행되는 EMR 클러스터에 영향을 주지 않는 모든 CVEs가 나열되어 있습니다. Amazon EMR은 업스트림 오픈 소스의 수정 사항 가용성에 종속되어 있으며, Amazon EMR이 수정 사항을 확인한 후 90일 이내에 코어 엔진 구성 요소의 일부로 안정적인 최신 버전을 제공합니다.
이 표는 2025년 9월 25일에 업데이트되었습니다.
| CVE ID | 심각도 | CVE 세부 정보 URL |
| --- | --- | --- |
| CVE-2015-1832 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2015-1832](https://nvd.nist.gov/vuln/detail/CVE-2015-1832) |
| CVE-2016-5018 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2016-5018](https://nvd.nist.gov/vuln/detail/CVE-2016-5018) |
| CVE-2017-15095 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2017-15095](https://nvd.nist.gov/vuln/detail/CVE-2017-15095) |
| CVE-2017-17485 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2017-17485](https://nvd.nist.gov/vuln/detail/CVE-2017-17485) |
| CVE-2017-7525 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2017-7525](https://nvd.nist.gov/vuln/detail/CVE-2017-7525) |
| CVE-2018-11307 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-11307](https://nvd.nist.gov/vuln/detail/CVE-2018-11307) |
| CVE-2018-11307 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-11307](https://nvd.nist.gov/vuln/detail/CVE-2018-11307) |
| CVE-2018-14718 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-14718](https://nvd.nist.gov/vuln/detail/CVE-2018-14718) |
| CVE-2018-14718 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-14718](https://nvd.nist.gov/vuln/detail/CVE-2018-14718) |
| CVE-2018-14719 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-14719](https://nvd.nist.gov/vuln/detail/CVE-2018-14719) |
| CVE-2018-14719 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-14719](https://nvd.nist.gov/vuln/detail/CVE-2018-14719) |
| CVE-2018-14720 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-14720](https://nvd.nist.gov/vuln/detail/CVE-2018-14720) |
| CVE-2018-14720 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-14720](https://nvd.nist.gov/vuln/detail/CVE-2018-14720) |
| CVE-2018-14721 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-14721](https://nvd.nist.gov/vuln/detail/CVE-2018-14721) |
| CVE-2018-14721 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-14721](https://nvd.nist.gov/vuln/detail/CVE-2018-14721) |
| CVE-2018-19360 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-19360](https://nvd.nist.gov/vuln/detail/CVE-2018-19360) |
| CVE-2018-19360 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-19360](https://nvd.nist.gov/vuln/detail/CVE-2018-19360) |
| CVE-2018-19361 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-19361](https://nvd.nist.gov/vuln/detail/CVE-2018-19361) |
| CVE-2018-19361 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-19361](https://nvd.nist.gov/vuln/detail/CVE-2018-19361) |
| CVE-2018-19362 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-19362](https://nvd.nist.gov/vuln/detail/CVE-2018-19362) |
| CVE-2018-19362 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-19362](https://nvd.nist.gov/vuln/detail/CVE-2018-19362) |
| CVE-2018-7489 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-7489](https://nvd.nist.gov/vuln/detail/CVE-2018-7489) |
| CVE-2018-7489 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-7489](https://nvd.nist.gov/vuln/detail/CVE-2018-7489) |
| CVE-2019-10202 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-10202](https://nvd.nist.gov/vuln/detail/CVE-2019-10202) |
| CVE-2019-14379 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14379](https://nvd.nist.gov/vuln/detail/CVE-2019-14379) |
| CVE-2019-14379 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14379](https://nvd.nist.gov/vuln/detail/CVE-2019-14379) |
| CVE-2019-14540 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14540](https://nvd.nist.gov/vuln/detail/CVE-2019-14540) |
| CVE-2019-14540 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14540](https://nvd.nist.gov/vuln/detail/CVE-2019-14540) |
| CVE-2019-14892 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14892](https://nvd.nist.gov/vuln/detail/CVE-2019-14892) |
| CVE-2019-14892 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14892](https://nvd.nist.gov/vuln/detail/CVE-2019-14892) |
| CVE-2019-14893 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14893](https://nvd.nist.gov/vuln/detail/CVE-2019-14893) |
| CVE-2019-14893 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14893](https://nvd.nist.gov/vuln/detail/CVE-2019-14893) |
| CVE-2019-16335 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-16335](https://nvd.nist.gov/vuln/detail/CVE-2019-16335) |
| CVE-2019-16335 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-16335](https://nvd.nist.gov/vuln/detail/CVE-2019-16335) |
| CVE-2019-16942 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-16942](https://nvd.nist.gov/vuln/detail/CVE-2019-16942) |
| CVE-2019-16942 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-16942](https://nvd.nist.gov/vuln/detail/CVE-2019-16942) |
| CVE-2019-16943 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-16943](https://nvd.nist.gov/vuln/detail/CVE-2019-16943) |
| CVE-2019-16943 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-16943](https://nvd.nist.gov/vuln/detail/CVE-2019-16943) |
| CVE-2019-17267 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-17267](https://nvd.nist.gov/vuln/detail/CVE-2019-17267) |
| CVE-2019-17267 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-17267](https://nvd.nist.gov/vuln/detail/CVE-2019-17267) |
| CVE-2019-17531 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-17531](https://nvd.nist.gov/vuln/detail/CVE-2019-17531) |
| CVE-2019-17531 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-17531](https://nvd.nist.gov/vuln/detail/CVE-2019-17531) |
| CVE-2019-20330 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-20330](https://nvd.nist.gov/vuln/detail/CVE-2019-20330) |
| CVE-2019-20330 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-20330](https://nvd.nist.gov/vuln/detail/CVE-2019-20330) |
| CVE-2020-8840 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8840](https://nvd.nist.gov/vuln/detail/CVE-2020-8840) |
| CVE-2020-8840 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8840](https://nvd.nist.gov/vuln/detail/CVE-2020-8840) |
| CVE-2020-9546 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-9546](https://nvd.nist.gov/vuln/detail/CVE-2020-9546) |
| CVE-2020-9546 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-9546](https://nvd.nist.gov/vuln/detail/CVE-2020-9546) |
| CVE-2020-9547 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-9547](https://nvd.nist.gov/vuln/detail/CVE-2020-9547) |
| CVE-2020-9547 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-9547](https://nvd.nist.gov/vuln/detail/CVE-2020-9547) |
| CVE-2020-9548 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-9548](https://nvd.nist.gov/vuln/detail/CVE-2020-9548) |
| CVE-2020-9548 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-9548](https://nvd.nist.gov/vuln/detail/CVE-2020-9548) |
| CVE-2022-1471 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-1471](https://nvd.nist.gov/vuln/detail/CVE-2022-1471) |
| CVE-2022-1471 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-1471](https://nvd.nist.gov/vuln/detail/CVE-2022-1471) |
| CVE-2022-37865 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-37865](https://nvd.nist.gov/vuln/detail/CVE-2022-37865) |
| CVE-2022-39135 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-39135](https://nvd.nist.gov/vuln/detail/CVE-2022-39135) |
| CVE-2022-42889 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42889](https://nvd.nist.gov/vuln/detail/CVE-2022-42889) |
| CVE-2022-46337 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-46337](https://nvd.nist.gov/vuln/detail/CVE-2022-46337) |
| CVE-2022-46337 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-46337](https://nvd.nist.gov/vuln/detail/CVE-2022-46337) |
| CVE-2024-51504 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2024-51504](https://nvd.nist.gov/vuln/detail/CVE-2024-51504) |
| CVE-2024-51504 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2024-51504](https://nvd.nist.gov/vuln/detail/CVE-2024-51504) |
| CVE-2024-52046 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2024-52046](https://nvd.nist.gov/vuln/detail/CVE-2024-52046) |
| CVE-2024-52046 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2024-52046](https://nvd.nist.gov/vuln/detail/CVE-2024-52046) |
| CVE-2024-52577 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2024-52577](https://nvd.nist.gov/vuln/detail/CVE-2024-52577) |
| CVE-2024-53990 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2024-53990](https://nvd.nist.gov/vuln/detail/CVE-2024-53990) |
| CVE-2024-56325 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2024-56325](https://nvd.nist.gov/vuln/detail/CVE-2024-56325) |
| CVE-2025-30065 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2025-30065](https://nvd.nist.gov/vuln/detail/CVE-2025-30065) |
| CVE-2014-3643 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2014-3643](https://nvd.nist.gov/vuln/detail/CVE-2014-3643) |
| CVE-2015-5237 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2015-5237](https://nvd.nist.gov/vuln/detail/CVE-2015-5237) |
| CVE-2015-5237 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2015-5237](https://nvd.nist.gov/vuln/detail/CVE-2015-5237) |
| CVE-2016-6796 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2016-6796](https://nvd.nist.gov/vuln/detail/CVE-2016-6796) |
| CVE-2018-1000180 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-1000180](https://nvd.nist.gov/vuln/detail/CVE-2018-1000180) |
| CVE-2018-1000180 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-1000180](https://nvd.nist.gov/vuln/detail/CVE-2018-1000180) |
| CVE-2018-12022 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-12022](https://nvd.nist.gov/vuln/detail/CVE-2018-12022) |
| CVE-2018-12022 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-12022](https://nvd.nist.gov/vuln/detail/CVE-2018-12022) |
| CVE-2018-12023 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-12023](https://nvd.nist.gov/vuln/detail/CVE-2018-12023) |
| CVE-2018-12023 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-12023](https://nvd.nist.gov/vuln/detail/CVE-2018-12023) |
| CVE-2018-5968 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-5968](https://nvd.nist.gov/vuln/detail/CVE-2018-5968) |
| CVE-2019-0205 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-0205](https://nvd.nist.gov/vuln/detail/CVE-2019-0205) |
| CVE-2019-0205 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-0205](https://nvd.nist.gov/vuln/detail/CVE-2019-0205) |
| CVE-2019-10172 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-10172](https://nvd.nist.gov/vuln/detail/CVE-2019-10172) |
| CVE-2019-12086 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-12086](https://nvd.nist.gov/vuln/detail/CVE-2019-12086) |
| CVE-2019-12086 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-12086](https://nvd.nist.gov/vuln/detail/CVE-2019-12086) |
| CVE-2019-14439 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14439](https://nvd.nist.gov/vuln/detail/CVE-2019-14439) |
| CVE-2019-14439 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14439](https://nvd.nist.gov/vuln/detail/CVE-2019-14439) |
| CVE-2020-10650 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10650](https://nvd.nist.gov/vuln/detail/CVE-2020-10650) |
| CVE-2020-10650 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10650](https://nvd.nist.gov/vuln/detail/CVE-2020-10650) |
| CVE-2020-10672 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10672](https://nvd.nist.gov/vuln/detail/CVE-2020-10672) |
| CVE-2020-10672 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10672](https://nvd.nist.gov/vuln/detail/CVE-2020-10672) |
| CVE-2020-10673 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10673](https://nvd.nist.gov/vuln/detail/CVE-2020-10673) |
| CVE-2020-10673 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10673](https://nvd.nist.gov/vuln/detail/CVE-2020-10673) |
| CVE-2020-10968 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10968](https://nvd.nist.gov/vuln/detail/CVE-2020-10968) |
| CVE-2020-10968 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10968](https://nvd.nist.gov/vuln/detail/CVE-2020-10968) |
| CVE-2020-10969 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10969](https://nvd.nist.gov/vuln/detail/CVE-2020-10969) |
| CVE-2020-10969 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10969](https://nvd.nist.gov/vuln/detail/CVE-2020-10969) |
| CVE-2020-11111 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11111](https://nvd.nist.gov/vuln/detail/CVE-2020-11111) |
| CVE-2020-11111 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11111](https://nvd.nist.gov/vuln/detail/CVE-2020-11111) |
| CVE-2020-11112 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11112](https://nvd.nist.gov/vuln/detail/CVE-2020-11112) |
| CVE-2020-11112 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11112](https://nvd.nist.gov/vuln/detail/CVE-2020-11112) |
| CVE-2020-11113 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11113](https://nvd.nist.gov/vuln/detail/CVE-2020-11113) |
| CVE-2020-11113 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11113](https://nvd.nist.gov/vuln/detail/CVE-2020-11113) |
| CVE-2020-11619 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11619](https://nvd.nist.gov/vuln/detail/CVE-2020-11619) |
| CVE-2020-11619 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11619](https://nvd.nist.gov/vuln/detail/CVE-2020-11619) |
| CVE-2020-11620 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11620](https://nvd.nist.gov/vuln/detail/CVE-2020-11620) |
| CVE-2020-11620 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11620](https://nvd.nist.gov/vuln/detail/CVE-2020-11620) |
| CVE-2020-13949 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-13949](https://nvd.nist.gov/vuln/detail/CVE-2020-13949) |
| CVE-2020-13949 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-13949](https://nvd.nist.gov/vuln/detail/CVE-2020-13949) |
| CVE-2020-13949 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-13949](https://nvd.nist.gov/vuln/detail/CVE-2020-13949) |
| CVE-2020-14060 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14060](https://nvd.nist.gov/vuln/detail/CVE-2020-14060) |
| CVE-2020-14060 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14060](https://nvd.nist.gov/vuln/detail/CVE-2020-14060) |
| CVE-2020-14061 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14061](https://nvd.nist.gov/vuln/detail/CVE-2020-14061) |
| CVE-2020-14061 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14061](https://nvd.nist.gov/vuln/detail/CVE-2020-14061) |
| CVE-2020-14062 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14062](https://nvd.nist.gov/vuln/detail/CVE-2020-14062) |
| CVE-2020-14062 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14062](https://nvd.nist.gov/vuln/detail/CVE-2020-14062) |
| CVE-2020-14195 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14195](https://nvd.nist.gov/vuln/detail/CVE-2020-14195) |
| CVE-2020-14195 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14195](https://nvd.nist.gov/vuln/detail/CVE-2020-14195) |
| CVE-2020-24616 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-24616](https://nvd.nist.gov/vuln/detail/CVE-2020-24616) |
| CVE-2020-24616 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-24616](https://nvd.nist.gov/vuln/detail/CVE-2020-24616) |
| CVE-2020-24750 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-24750](https://nvd.nist.gov/vuln/detail/CVE-2020-24750) |
| CVE-2020-24750 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-24750](https://nvd.nist.gov/vuln/detail/CVE-2020-24750) |
| CVE-2020-25649 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-25649](https://nvd.nist.gov/vuln/detail/CVE-2020-25649) |
| CVE-2020-28052 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-28052](https://nvd.nist.gov/vuln/detail/CVE-2020-28052) |
| CVE-2020-35490 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-35490](https://nvd.nist.gov/vuln/detail/CVE-2020-35490) |
| CVE-2020-35490 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-35490](https://nvd.nist.gov/vuln/detail/CVE-2020-35490) |
| CVE-2020-35491 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-35491](https://nvd.nist.gov/vuln/detail/CVE-2020-35491) |
| CVE-2020-35491 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-35491](https://nvd.nist.gov/vuln/detail/CVE-2020-35491) |
| CVE-2020-35728 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-35728](https://nvd.nist.gov/vuln/detail/CVE-2020-35728) |
| CVE-2020-35728 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-35728](https://nvd.nist.gov/vuln/detail/CVE-2020-35728) |
| CVE-2020-36179 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36179](https://nvd.nist.gov/vuln/detail/CVE-2020-36179) |
| CVE-2020-36179 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36179](https://nvd.nist.gov/vuln/detail/CVE-2020-36179) |
| CVE-2020-36180 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36180](https://nvd.nist.gov/vuln/detail/CVE-2020-36180) |
| CVE-2020-36180 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36180](https://nvd.nist.gov/vuln/detail/CVE-2020-36180) |
| CVE-2020-36181 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36181](https://nvd.nist.gov/vuln/detail/CVE-2020-36181) |
| CVE-2020-36181 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36181](https://nvd.nist.gov/vuln/detail/CVE-2020-36181) |
| CVE-2020-36182 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36182](https://nvd.nist.gov/vuln/detail/CVE-2020-36182) |
| CVE-2020-36182 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36182](https://nvd.nist.gov/vuln/detail/CVE-2020-36182) |
| CVE-2020-36183 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36183](https://nvd.nist.gov/vuln/detail/CVE-2020-36183) |
| CVE-2020-36183 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36183](https://nvd.nist.gov/vuln/detail/CVE-2020-36183) |
| CVE-2020-36184 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36184](https://nvd.nist.gov/vuln/detail/CVE-2020-36184) |
| CVE-2020-36184 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36184](https://nvd.nist.gov/vuln/detail/CVE-2020-36184) |
| CVE-2020-36185 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36185](https://nvd.nist.gov/vuln/detail/CVE-2020-36185) |
| CVE-2020-36185 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36185](https://nvd.nist.gov/vuln/detail/CVE-2020-36185) |
| CVE-2020-36186 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36186](https://nvd.nist.gov/vuln/detail/CVE-2020-36186) |
| CVE-2020-36186 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36186](https://nvd.nist.gov/vuln/detail/CVE-2020-36186) |
| CVE-2020-36187 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36187](https://nvd.nist.gov/vuln/detail/CVE-2020-36187) |
| CVE-2020-36187 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36187](https://nvd.nist.gov/vuln/detail/CVE-2020-36187) |
| CVE-2020-36188 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36188](https://nvd.nist.gov/vuln/detail/CVE-2020-36188) |
| CVE-2020-36188 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36188](https://nvd.nist.gov/vuln/detail/CVE-2020-36188) |
| CVE-2020-36189 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36189](https://nvd.nist.gov/vuln/detail/CVE-2020-36189) |
| CVE-2020-36189 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36189](https://nvd.nist.gov/vuln/detail/CVE-2020-36189) |
| CVE-2020-36518 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36518](https://nvd.nist.gov/vuln/detail/CVE-2020-36518) |
| CVE-2020-36518 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36518](https://nvd.nist.gov/vuln/detail/CVE-2020-36518) |
| CVE-2021-20190 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-20190](https://nvd.nist.gov/vuln/detail/CVE-2021-20190) |
| CVE-2021-20190 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-20190](https://nvd.nist.gov/vuln/detail/CVE-2021-20190) |
| CVE-2021-31684 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-31684](https://nvd.nist.gov/vuln/detail/CVE-2021-31684) |
| CVE-2021-34538 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-34538](https://nvd.nist.gov/vuln/detail/CVE-2021-34538) |
| CVE-2021-34538 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-34538](https://nvd.nist.gov/vuln/detail/CVE-2021-34538) |
| CVE-2021-34538 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-34538](https://nvd.nist.gov/vuln/detail/CVE-2021-34538) |
| CVE-2022-25647 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-25647](https://nvd.nist.gov/vuln/detail/CVE-2022-25647) |
| CVE-2022-25647 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-25647](https://nvd.nist.gov/vuln/detail/CVE-2022-25647) |
| CVE-2022-25647 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-25647](https://nvd.nist.gov/vuln/detail/CVE-2022-25647) |
| CVE-2022-25857 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-25857](https://nvd.nist.gov/vuln/detail/CVE-2022-25857) |
| CVE-2022-3171 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3171](https://nvd.nist.gov/vuln/detail/CVE-2022-3171) |
| CVE-2022-3171 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3171](https://nvd.nist.gov/vuln/detail/CVE-2022-3171) |
| CVE-2022-3509 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3509](https://nvd.nist.gov/vuln/detail/CVE-2022-3509) |
| CVE-2022-3509 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3509](https://nvd.nist.gov/vuln/detail/CVE-2022-3509) |
| CVE-2022-3510 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3510](https://nvd.nist.gov/vuln/detail/CVE-2022-3510) |
| CVE-2022-36364 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-36364](https://nvd.nist.gov/vuln/detail/CVE-2022-36364) |
| CVE-2022-37866 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-37866](https://nvd.nist.gov/vuln/detail/CVE-2022-37866) |
| CVE-2022-40149 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-40149](https://nvd.nist.gov/vuln/detail/CVE-2022-40149) |
| CVE-2022-40149 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-40149](https://nvd.nist.gov/vuln/detail/CVE-2022-40149) |
| CVE-2022-40150 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-40150](https://nvd.nist.gov/vuln/detail/CVE-2022-40150) |
| CVE-2022-40150 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-40150](https://nvd.nist.gov/vuln/detail/CVE-2022-40150) |
| CVE-2022-41404 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-41404](https://nvd.nist.gov/vuln/detail/CVE-2022-41404) |
| CVE-2022-42003 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42003](https://nvd.nist.gov/vuln/detail/CVE-2022-42003) |
| CVE-2022-42003 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42003](https://nvd.nist.gov/vuln/detail/CVE-2022-42003) |
| CVE-2022-42003 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42003](https://nvd.nist.gov/vuln/detail/CVE-2022-42003) |
| CVE-2022-42003 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42003](https://nvd.nist.gov/vuln/detail/CVE-2022-42003) |
| CVE-2022-42003 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42003](https://nvd.nist.gov/vuln/detail/CVE-2022-42003) |
| CVE-2022-42004 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42004](https://nvd.nist.gov/vuln/detail/CVE-2022-42004) |
| CVE-2022-42004 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42004](https://nvd.nist.gov/vuln/detail/CVE-2022-42004) |
| CVE-2022-42004 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42004](https://nvd.nist.gov/vuln/detail/CVE-2022-42004) |
| CVE-2022-42004 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42004](https://nvd.nist.gov/vuln/detail/CVE-2022-42004) |
| CVE-2022-45685 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-45685](https://nvd.nist.gov/vuln/detail/CVE-2022-45685) |
| CVE-2022-45685 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-45685](https://nvd.nist.gov/vuln/detail/CVE-2022-45685) |
| CVE-2022-45693 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-45693](https://nvd.nist.gov/vuln/detail/CVE-2022-45693) |
| CVE-2022-45693 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-45693](https://nvd.nist.gov/vuln/detail/CVE-2022-45693) |
| CVE-2022-46751 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-46751](https://nvd.nist.gov/vuln/detail/CVE-2022-46751) |
| CVE-2022-46751 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-46751](https://nvd.nist.gov/vuln/detail/CVE-2022-46751) |
| CVE-2023-1370 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-1370](https://nvd.nist.gov/vuln/detail/CVE-2023-1370) |
| CVE-2023-1436 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-1436](https://nvd.nist.gov/vuln/detail/CVE-2023-1436) |
| CVE-2023-1436 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-1436](https://nvd.nist.gov/vuln/detail/CVE-2023-1436) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-39410 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-39410](https://nvd.nist.gov/vuln/detail/CVE-2023-39410) |
| CVE-2023-6378 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-6378](https://nvd.nist.gov/vuln/detail/CVE-2023-6378) |
| CVE-2023-6378 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-6378](https://nvd.nist.gov/vuln/detail/CVE-2023-6378) |
| CVE-2023-6481 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-6481](https://nvd.nist.gov/vuln/detail/CVE-2023-6481) |
| CVE-2023-6481 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-6481](https://nvd.nist.gov/vuln/detail/CVE-2023-6481) |
| CVE-2024-13009 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-13009](https://nvd.nist.gov/vuln/detail/CVE-2024-13009) |
| CVE-2024-13009 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-13009](https://nvd.nist.gov/vuln/detail/CVE-2024-13009) |
| CVE-2024-29131 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-29131](https://nvd.nist.gov/vuln/detail/CVE-2024-29131) |
| CVE-2024-29857 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-29857](https://nvd.nist.gov/vuln/detail/CVE-2024-29857) |
| CVE-2024-29857 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-29857](https://nvd.nist.gov/vuln/detail/CVE-2024-29857) |
| CVE-2024-29857 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-29857](https://nvd.nist.gov/vuln/detail/CVE-2024-29857) |
| CVE-2024-29857 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-29857](https://nvd.nist.gov/vuln/detail/CVE-2024-29857) |
| CVE-2024-30172 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-30172](https://nvd.nist.gov/vuln/detail/CVE-2024-30172) |
| CVE-2024-30172 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-30172](https://nvd.nist.gov/vuln/detail/CVE-2024-30172) |
| CVE-2024-34447 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-34447](https://nvd.nist.gov/vuln/detail/CVE-2024-34447) |
| CVE-2024-34447 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-34447](https://nvd.nist.gov/vuln/detail/CVE-2024-34447) |
| CVE-2024-36114 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-36114](https://nvd.nist.gov/vuln/detail/CVE-2024-36114) |
| CVE-2024-36114 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-36114](https://nvd.nist.gov/vuln/detail/CVE-2024-36114) |
| CVE-2024-47561 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-47561](https://nvd.nist.gov/vuln/detail/CVE-2024-47561) |
| CVE-2024-57699 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-57699](https://nvd.nist.gov/vuln/detail/CVE-2024-57699) |
| CVE-2024-7254 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-7254](https://nvd.nist.gov/vuln/detail/CVE-2024-7254) |
| CVE-2024-7254 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-7254](https://nvd.nist.gov/vuln/detail/CVE-2024-7254) |
| CVE-2024-7254 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-7254](https://nvd.nist.gov/vuln/detail/CVE-2024-7254) |
| CVE-2024-7254 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-7254](https://nvd.nist.gov/vuln/detail/CVE-2024-7254) |
| CVE-2024-7254 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-7254](https://nvd.nist.gov/vuln/detail/CVE-2024-7254) |
| CVE-2024-7254 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-7254](https://nvd.nist.gov/vuln/detail/CVE-2024-7254) |
| CVE-2024-7254 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-7254](https://nvd.nist.gov/vuln/detail/CVE-2024-7254) |
| CVE-2024-9823 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-9823](https://nvd.nist.gov/vuln/detail/CVE-2024-9823) |
| CVE-2025-1948 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-1948](https://nvd.nist.gov/vuln/detail/CVE-2025-1948) |
| CVE-2025-24970 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-24970](https://nvd.nist.gov/vuln/detail/CVE-2025-24970) |
| CVE-2025-24970 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-24970](https://nvd.nist.gov/vuln/detail/CVE-2025-24970) |
| CVE-2025-27553 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-27553](https://nvd.nist.gov/vuln/detail/CVE-2025-27553) |
| CVE-2025-27817 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-27817](https://nvd.nist.gov/vuln/detail/CVE-2025-27817) |
| CVE-2025-27817 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-27817](https://nvd.nist.gov/vuln/detail/CVE-2025-27817) |
| CVE-2025-27817 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-27817](https://nvd.nist.gov/vuln/detail/CVE-2025-27817) |
| CVE-2025-27820 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-27820](https://nvd.nist.gov/vuln/detail/CVE-2025-27820) |
| CVE-2025-27820 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-27820](https://nvd.nist.gov/vuln/detail/CVE-2025-27820) |
| CVE-2025-30706 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-30706](https://nvd.nist.gov/vuln/detail/CVE-2025-30706) |
| CVE-2025-30706 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-30706](https://nvd.nist.gov/vuln/detail/CVE-2025-30706) |
| CVE-2025-46762 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-46762](https://nvd.nist.gov/vuln/detail/CVE-2025-46762) |
| CVE-2025-48734 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-48734](https://nvd.nist.gov/vuln/detail/CVE-2025-48734) |
| CVE-2025-48734 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-48734](https://nvd.nist.gov/vuln/detail/CVE-2025-48734) |
| CVE-2025-49146 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-49146](https://nvd.nist.gov/vuln/detail/CVE-2025-49146) |
| CVE-2025-5115 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-5115](https://nvd.nist.gov/vuln/detail/CVE-2025-5115) |
| CVE-2025-52434 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-52434](https://nvd.nist.gov/vuln/detail/CVE-2025-52434) |
| CVE-2025-52999 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-52999](https://nvd.nist.gov/vuln/detail/CVE-2025-52999) |
| CVE-2025-52999 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-52999](https://nvd.nist.gov/vuln/detail/CVE-2025-52999) |
| CVE-2025-52999 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-52999](https://nvd.nist.gov/vuln/detail/CVE-2025-52999) |
| CVE-2025-52999 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-52999](https://nvd.nist.gov/vuln/detail/CVE-2025-52999) |
| CVE-2025-52999 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-52999](https://nvd.nist.gov/vuln/detail/CVE-2025-52999) |
| CVE-2025-52999 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-52999](https://nvd.nist.gov/vuln/detail/CVE-2025-52999) |
| CVE-2025-55163 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-55163](https://nvd.nist.gov/vuln/detail/CVE-2025-55163) |
| CVE-2025-55163 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-55163](https://nvd.nist.gov/vuln/detail/CVE-2025-55163) |
| CVE-2025-58056 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-58056](https://nvd.nist.gov/vuln/detail/CVE-2025-58056) |
| CVE-2025-58056 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-58056](https://nvd.nist.gov/vuln/detail/CVE-2025-58056) |
| CVE-2025-58057 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-58057](https://nvd.nist.gov/vuln/detail/CVE-2025-58057) |
| CVE-2025-58057 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-58057](https://nvd.nist.gov/vuln/detail/CVE-2025-58057) |
| CVE-2025-58057 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-58057](https://nvd.nist.gov/vuln/detail/CVE-2025-58057) |
| CVE-2025-58057 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-58057](https://nvd.nist.gov/vuln/detail/CVE-2025-58057) |
| CVE-2012-5783 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2012-5783](https://nvd.nist.gov/vuln/detail/CVE-2012-5783) |
| CVE-2012-5783 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2012-5783](https://nvd.nist.gov/vuln/detail/CVE-2012-5783) |
| CVE-2012-6153 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2012-6153](https://nvd.nist.gov/vuln/detail/CVE-2012-6153) |
| CVE-2012-6153 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2012-6153](https://nvd.nist.gov/vuln/detail/CVE-2012-6153) |
| CVE-2018-10237 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2018-10237](https://nvd.nist.gov/vuln/detail/CVE-2018-10237) |
| CVE-2018-10237 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2018-10237](https://nvd.nist.gov/vuln/detail/CVE-2018-10237) |
| CVE-2018-10237 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2018-10237](https://nvd.nist.gov/vuln/detail/CVE-2018-10237) |
| CVE-2018-10237 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2018-10237](https://nvd.nist.gov/vuln/detail/CVE-2018-10237) |
| CVE-2018-10237 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2018-10237](https://nvd.nist.gov/vuln/detail/CVE-2018-10237) |
| CVE-2018-11798 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2018-11798](https://nvd.nist.gov/vuln/detail/CVE-2018-11798) |
| CVE-2018-1313 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2018-1313](https://nvd.nist.gov/vuln/detail/CVE-2018-1313) |
| CVE-2019-12384 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2019-12384](https://nvd.nist.gov/vuln/detail/CVE-2019-12384) |
| CVE-2019-12384 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2019-12384](https://nvd.nist.gov/vuln/detail/CVE-2019-12384) |
| CVE-2019-12814 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2019-12814](https://nvd.nist.gov/vuln/detail/CVE-2019-12814) |
| CVE-2019-12814 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2019-12814](https://nvd.nist.gov/vuln/detail/CVE-2019-12814) |
| CVE-2020-13955 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-13955](https://nvd.nist.gov/vuln/detail/CVE-2020-13955) |
| CVE-2020-13956 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-13956](https://nvd.nist.gov/vuln/detail/CVE-2020-13956) |
| CVE-2020-15250 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-15250](https://nvd.nist.gov/vuln/detail/CVE-2020-15250) |
| CVE-2020-15250 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-15250](https://nvd.nist.gov/vuln/detail/CVE-2020-15250) |
| CVE-2020-15522 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-15522](https://nvd.nist.gov/vuln/detail/CVE-2020-15522) |
| CVE-2020-15522 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-15522](https://nvd.nist.gov/vuln/detail/CVE-2020-15522) |
| CVE-2020-15522 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-15522](https://nvd.nist.gov/vuln/detail/CVE-2020-15522) |
| CVE-2020-17521 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-17521](https://nvd.nist.gov/vuln/detail/CVE-2020-17521) |
| CVE-2020-17521 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-17521](https://nvd.nist.gov/vuln/detail/CVE-2020-17521) |
| CVE-2020-1945 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-1945](https://nvd.nist.gov/vuln/detail/CVE-2020-1945) |
| CVE-2020-26939 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-26939](https://nvd.nist.gov/vuln/detail/CVE-2020-26939) |
| CVE-2020-26939 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-26939](https://nvd.nist.gov/vuln/detail/CVE-2020-26939) |
| CVE-2020-26939 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-26939](https://nvd.nist.gov/vuln/detail/CVE-2020-26939) |
| CVE-2021-22569 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2021-22569](https://nvd.nist.gov/vuln/detail/CVE-2021-22569) |
| CVE-2021-22569 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2021-22569](https://nvd.nist.gov/vuln/detail/CVE-2021-22569) |
| CVE-2021-27568 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2021-27568](https://nvd.nist.gov/vuln/detail/CVE-2021-27568) |
| CVE-2021-28170 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2021-28170](https://nvd.nist.gov/vuln/detail/CVE-2021-28170) |
| CVE-2021-29425 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2021-29425](https://nvd.nist.gov/vuln/detail/CVE-2021-29425) |
| CVE-2021-36373 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2021-36373](https://nvd.nist.gov/vuln/detail/CVE-2021-36373) |
| CVE-2021-36374 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2021-36374](https://nvd.nist.gov/vuln/detail/CVE-2021-36374) |
| CVE-2022-38749 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2022-38749](https://nvd.nist.gov/vuln/detail/CVE-2022-38749) |
| CVE-2022-38750 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2022-38750](https://nvd.nist.gov/vuln/detail/CVE-2022-38750) |
| CVE-2022-38751 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2022-38751](https://nvd.nist.gov/vuln/detail/CVE-2022-38751) |
| CVE-2022-38752 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2022-38752](https://nvd.nist.gov/vuln/detail/CVE-2022-38752) |
| CVE-2022-41854 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2022-41854](https://nvd.nist.gov/vuln/detail/CVE-2022-41854) |
| CVE-2023-0833 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-0833](https://nvd.nist.gov/vuln/detail/CVE-2023-0833) |
| CVE-2023-33201 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-33201](https://nvd.nist.gov/vuln/detail/CVE-2023-33201) |
| CVE-2023-33201 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-33201](https://nvd.nist.gov/vuln/detail/CVE-2023-33201) |
| CVE-2023-33201 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-33201](https://nvd.nist.gov/vuln/detail/CVE-2023-33201) |
| CVE-2023-33201 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-33201](https://nvd.nist.gov/vuln/detail/CVE-2023-33201) |
| CVE-2023-33202 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-33202](https://nvd.nist.gov/vuln/detail/CVE-2023-33202) |
| CVE-2023-33202 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-33202](https://nvd.nist.gov/vuln/detail/CVE-2023-33202) |
| CVE-2023-33202 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-33202](https://nvd.nist.gov/vuln/detail/CVE-2023-33202) |
| CVE-2023-33202 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-33202](https://nvd.nist.gov/vuln/detail/CVE-2023-33202) |
| CVE-2023-42503 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-42503](https://nvd.nist.gov/vuln/detail/CVE-2023-42503) |
| CVE-2023-51074 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-51074](https://nvd.nist.gov/vuln/detail/CVE-2023-51074) |
| CVE-2024-12798 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-12798](https://nvd.nist.gov/vuln/detail/CVE-2024-12798) |
| CVE-2024-12798 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-12798](https://nvd.nist.gov/vuln/detail/CVE-2024-12798) |
| CVE-2024-12798 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-12798](https://nvd.nist.gov/vuln/detail/CVE-2024-12798) |
| CVE-2024-12798 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-12798](https://nvd.nist.gov/vuln/detail/CVE-2024-12798) |
| CVE-2024-12798 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-12798](https://nvd.nist.gov/vuln/detail/CVE-2024-12798) |
| CVE-2024-12798 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-12798](https://nvd.nist.gov/vuln/detail/CVE-2024-12798) |
| CVE-2024-23944 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-23944](https://nvd.nist.gov/vuln/detail/CVE-2024-23944) |
| CVE-2024-23945 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-23945](https://nvd.nist.gov/vuln/detail/CVE-2024-23945) |
| CVE-2024-23945 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-23945](https://nvd.nist.gov/vuln/detail/CVE-2024-23945) |
| CVE-2024-23953 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-23953](https://nvd.nist.gov/vuln/detail/CVE-2024-23953) |
| CVE-2024-23953 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-23953](https://nvd.nist.gov/vuln/detail/CVE-2024-23953) |
| CVE-2024-25710 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-25710](https://nvd.nist.gov/vuln/detail/CVE-2024-25710) |
| CVE-2024-25710 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-25710](https://nvd.nist.gov/vuln/detail/CVE-2024-25710) |
| CVE-2024-26308 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-26308](https://nvd.nist.gov/vuln/detail/CVE-2024-26308) |
| CVE-2024-26308 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-26308](https://nvd.nist.gov/vuln/detail/CVE-2024-26308) |
| CVE-2024-29025 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-29025](https://nvd.nist.gov/vuln/detail/CVE-2024-29025) |
| CVE-2024-29133 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-29133](https://nvd.nist.gov/vuln/detail/CVE-2024-29133) |
| CVE-2024-29869 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-29869](https://nvd.nist.gov/vuln/detail/CVE-2024-29869) |
| CVE-2024-29869 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-29869](https://nvd.nist.gov/vuln/detail/CVE-2024-29869) |
| CVE-2024-30171 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-30171](https://nvd.nist.gov/vuln/detail/CVE-2024-30171) |
| CVE-2024-30171 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-30171](https://nvd.nist.gov/vuln/detail/CVE-2024-30171) |
| CVE-2024-30171 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-30171](https://nvd.nist.gov/vuln/detail/CVE-2024-30171) |
| CVE-2024-30171 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-30171](https://nvd.nist.gov/vuln/detail/CVE-2024-30171) |
| CVE-2024-31141 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-31141](https://nvd.nist.gov/vuln/detail/CVE-2024-31141) |
| CVE-2024-47535 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-47535](https://nvd.nist.gov/vuln/detail/CVE-2024-47535) |
| CVE-2024-47535 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-47535](https://nvd.nist.gov/vuln/detail/CVE-2024-47535) |
| CVE-2024-47554 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-47554](https://nvd.nist.gov/vuln/detail/CVE-2024-47554) |
| CVE-2024-47554 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-47554](https://nvd.nist.gov/vuln/detail/CVE-2024-47554) |
| CVE-2024-47554 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-47554](https://nvd.nist.gov/vuln/detail/CVE-2024-47554) |
| CVE-2024-47554 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-47554](https://nvd.nist.gov/vuln/detail/CVE-2024-47554) |
| CVE-2024-52980 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-52980](https://nvd.nist.gov/vuln/detail/CVE-2024-52980) |
| CVE-2024-56128 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-56128](https://nvd.nist.gov/vuln/detail/CVE-2024-56128) |
| CVE-2024-6763 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-6763](https://nvd.nist.gov/vuln/detail/CVE-2024-6763) |
| CVE-2024-6763 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-6763](https://nvd.nist.gov/vuln/detail/CVE-2024-6763) |
| CVE-2024-6763 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-6763](https://nvd.nist.gov/vuln/detail/CVE-2024-6763) |
| CVE-2024-6763 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-6763](https://nvd.nist.gov/vuln/detail/CVE-2024-6763) |
| CVE-2024-6763 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-6763](https://nvd.nist.gov/vuln/detail/CVE-2024-6763) |
| CVE-2024-8184 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-8184](https://nvd.nist.gov/vuln/detail/CVE-2024-8184) |
| CVE-2025-22227 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-22227](https://nvd.nist.gov/vuln/detail/CVE-2025-22227) |
| CVE-2025-25193 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-25193](https://nvd.nist.gov/vuln/detail/CVE-2025-25193) |
| CVE-2025-25193 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-25193](https://nvd.nist.gov/vuln/detail/CVE-2025-25193) |
| CVE-2025-25193 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-25193](https://nvd.nist.gov/vuln/detail/CVE-2025-25193) |
| CVE-2025-30474 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-30474](https://nvd.nist.gov/vuln/detail/CVE-2025-30474) |
| CVE-2025-3588 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-3588](https://nvd.nist.gov/vuln/detail/CVE-2025-3588) |
| CVE-2025-46392 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-46392](https://nvd.nist.gov/vuln/detail/CVE-2025-46392) |
| CVE-2025-46551 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-46551](https://nvd.nist.gov/vuln/detail/CVE-2025-46551) |
| CVE-2025-48924 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-48924](https://nvd.nist.gov/vuln/detail/CVE-2025-48924) |
| CVE-2025-48924 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-48924](https://nvd.nist.gov/vuln/detail/CVE-2025-48924) |
| CVE-2025-48924 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-48924](https://nvd.nist.gov/vuln/detail/CVE-2025-48924) |
| CVE-2025-48924 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-48924](https://nvd.nist.gov/vuln/detail/CVE-2025-48924) |
| CVE-2025-48924 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-48924](https://nvd.nist.gov/vuln/detail/CVE-2025-48924) |
| CVE-2025-48924 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-48924](https://nvd.nist.gov/vuln/detail/CVE-2025-48924) |
| CVE-2025-48924 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-48924](https://nvd.nist.gov/vuln/detail/CVE-2025-48924) |
| CVE-2025-48924 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-48924](https://nvd.nist.gov/vuln/detail/CVE-2025-48924) |
| CVE-2025-48924 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-48924](https://nvd.nist.gov/vuln/detail/CVE-2025-48924) |
| CVE-2025-48924 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-48924](https://nvd.nist.gov/vuln/detail/CVE-2025-48924) |
| CVE-2025-49128 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-49128](https://nvd.nist.gov/vuln/detail/CVE-2025-49128) |
| CVE-2025-49128 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-49128](https://nvd.nist.gov/vuln/detail/CVE-2025-49128) |
| CVE-2025-49128 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-49128](https://nvd.nist.gov/vuln/detail/CVE-2025-49128) |
| CVE-2025-49128 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-49128](https://nvd.nist.gov/vuln/detail/CVE-2025-49128) |
| CVE-2025-53864 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-53864](https://nvd.nist.gov/vuln/detail/CVE-2025-53864) |
| CVE-2025-53864 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-53864](https://nvd.nist.gov/vuln/detail/CVE-2025-53864) |
| CVE-2025-58457 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-58457](https://nvd.nist.gov/vuln/detail/CVE-2025-58457) |
| CVE-2025-58457 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-58457](https://nvd.nist.gov/vuln/detail/CVE-2025-58457) |
| CVE-2025-58457 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-58457](https://nvd.nist.gov/vuln/detail/CVE-2025-58457) |
| CVE-2025-8885 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-8885](https://nvd.nist.gov/vuln/detail/CVE-2025-8885) |
| CVE-2025-8885 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-8885](https://nvd.nist.gov/vuln/detail/CVE-2025-8885) |
| CVE-2025-8916 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-8916](https://nvd.nist.gov/vuln/detail/CVE-2025-8916) |
| CVE-2025-8916 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-8916](https://nvd.nist.gov/vuln/detail/CVE-2025-8916) |
| CVE-2025-8916 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-8916](https://nvd.nist.gov/vuln/detail/CVE-2025-8916) |
| CVE-2025-8916 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-8916](https://nvd.nist.gov/vuln/detail/CVE-2025-8916) |
| CVE-2020-8908 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8908](https://nvd.nist.gov/vuln/detail/CVE-2020-8908) |
| CVE-2020-8908 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8908](https://nvd.nist.gov/vuln/detail/CVE-2020-8908) |
| CVE-2020-8908 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8908](https://nvd.nist.gov/vuln/detail/CVE-2020-8908) |
| CVE-2020-8908 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8908](https://nvd.nist.gov/vuln/detail/CVE-2020-8908) |
| CVE-2020-8908 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8908](https://nvd.nist.gov/vuln/detail/CVE-2020-8908) |
| CVE-2020-8908 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8908](https://nvd.nist.gov/vuln/detail/CVE-2020-8908) |
| CVE-2020-8908 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8908](https://nvd.nist.gov/vuln/detail/CVE-2020-8908) |
| CVE-2020-8908 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8908](https://nvd.nist.gov/vuln/detail/CVE-2020-8908) |
| CVE-2020-8908 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8908](https://nvd.nist.gov/vuln/detail/CVE-2020-8908) |
| CVE-2020-8908 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8908](https://nvd.nist.gov/vuln/detail/CVE-2020-8908) |
| CVE-2024-12801 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-12801](https://nvd.nist.gov/vuln/detail/CVE-2024-12801) |
| CVE-2024-12801 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-12801](https://nvd.nist.gov/vuln/detail/CVE-2024-12801) |
| CVE-2024-12801 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-12801](https://nvd.nist.gov/vuln/detail/CVE-2024-12801) |
| CVE-2025-27496 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-27496](https://nvd.nist.gov/vuln/detail/CVE-2025-27496) |
## 7.10.0 릴리스 정보
다음 릴리스 정보에는 Amazon EMR 릴리스 7.10.0에 대한 정보가 포함되어 있습니다.
**새로운 기능**
+ **애플리케이션 업그레이드** – Amazon EMR 7.10.0 application upgrades include AWS SDK for Java 2.31.48/1.12.782, Delta 3.3.0-amzn-2, Hadoop 3.4.1-amzn-2, Hudi 0.15.0-amzn-7, Iceberg 1.8.1-amzn-0, Spark 3.5.5-amzn-1, and Zookeeper 3.9.3-amzn-2.
+ **S3A 파일 시스템** - EMR 7.10.0 릴리스부터 S3A 파일 시스템은 EMRFS를 기본 EMR S3 커넥터로 대체했습니다. 자세한 내용은 [마이그레이션 가이드: EMRFS에서 S3A Filesystem으로 마이그레이션](https://docs.aws.amazon.com/emr/latest/ReleaseGuide/emr-s3a-migrate.html)을 참조하세요.
+ **Spark Kafka 스트리밍 지원** - EMR 7.10.0 릴리스부터 Kafka 데이터 소스를 사용하는 Spark 스트리밍 워크로드에는 aws-msk-iam-auth 2.3.2 및 commons-pool2 2.11.1 종속성이 포함됩니다. 이러한 JARs은 클러스터 시작 시 Spark 애플리케이션을 선택한 경우 사용할 수 있습니다.
+ **Flink 스트리밍 커넥터** - EMR 7.10.0 릴리스부터 Kafka 및 Kinesis 데이터 소스를 사용하는 Flink 스트리밍 워크로드에는 flink-sql-connector-kafka 3.4.0, flink-sql-connector-kinesis 5.0.0 및 aws-msk-iam-auth 2.3.2가 포함되어 있습니다. 이러한 커넥터 JARs은 클러스터 시작 시 Flink 애플리케이션을 선택한 경우 사용할 수 있습니다.
**알려진 문제**
+ **수락 상태** - 오픈 소스 버그 [YARN-11834](https://issues.apache.org/jira/browse/YARN-11834)로 인해 YARN 애플리케이션이 수락 상태에서 멈췄습니다. 이 문제가 발생하면 AWS 지원 팀에 문의하세요.
+ **ConcurrentModificationException 예외** - 오픈 소스 버그 [YARN-11838](https://issues.apache.org/jira/browse/YARN-11838)로 인해 ConcurrentModificationException 예외가 발생하여 YARN이 자주 다시 시작됩니다. 이 문제가 발생하면 AWS 지원 팀에 문의하세요.
+ **YARN 애플리케이션 로그** - Resource Manager UI를 통해 YARN 애플리케이션 로그가 표시되지 않습니다. 문제를 해결하려면 다음 단계를 따르세요.
1. yarn-site.xml의 `yarn.log.server.url` 구성을 다음 값으로 업데이트합니다.
```
yarn.log.server.url
https://:19890/jobhistory/logs
```
1. hadoop 리소스 관리자 서비스 `systemctl restart hadoop-resourcemanager.service`를 다시 시작합니다.
+ **단계 로그 업로드 **- 일부 클러스터는 경합 조건으로 인해 단계 로그를 S3 버킷에 업로드하지 못할 수 있습니다. 이 문제가 발생하면 AWS 지원 팀에 문의하세요.
+ **Glue 카탈로그를 사용하여 HBase 테이블을 Hive에 생성** - EMR-7.3.0에서 EMR-7.10.0으로의 Hive Iceberg 통합으로 인해 버그가 발생하여 Glue Data Catalog를 메타스토어로 사용할 때 Hive에서 HBase 테이블 생성이 실패합니다. 이 문제가 발생하면 AWS 지원 팀에 문의하십시오.
+ **Tez UI** - EMR-7.3에서 EMR-7.10까지, 전송 중 암호화가 활성화된 경우 YARN Resource Manager Web UI를 통해 Tez UI에 액세스하지 못하는 버그가 있습니다. 이 문제는 Tez UI에 HTTPS가 필요한 동안 YARN 프록시가 HTTP 프로토콜을 사용하려고 시도하기 때문에 발생합니다. 이 문제를 해결하려면 `tez-site`의 `tez.tez-ui.history-url.base` 구성을 `http`에서 `https`로 수정하세요.
+ 레이블 및 지원되는 리전을 릴리스합니다.
[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/ko_kr/emr/latest/ReleaseGuide/emr-7100-release.html)
## 7.10.0 기본 Java 버전
Amazon EMR 릴리스 7.10 이상은 Apache Livy를 제외하고 Corretto 17(OpenJDK)을 지원하는 애플리케이션에 기본적으로 Amazon Corretto 17(OpenJDK 기반)과 함께 제공됩니다.
다음 표에는 Amazon EMR 7.10.0의 애플리케이션에 대한 기본 Java 버전이 나와 있습니다. 클러스터의 기본 JVM을 변경하려면 클러스터에서 실행되는 각 애플리케이션에 대해 [특정 Java 가상 머신을 사용하도록 애플리케이션 구성](configuring-java8.md)의 지침을 따릅니다. 클러스터에서는 Java 런타임 버전 1개만 사용할 수 있습니다. Amazon EMR은 동일한 클러스터에서 다양한 런타임 버전을 사용해 서로 다른 노드 또는 애플리케이션을 실행하는 것을 지원하지 않습니다.
| 애플리케이션 | Java 및 Amazon Corretto 버전(기본값은 굵은체로 표시) |
| --- | --- |
| 델타 | 17, 11, 8 |
| Flink | 17, 11, 8 |
| HBase | 17, 11, 8 |
| HCatalog | 17, 11, 8 |
| Hadoop | 17, 11, 8 |
| Hive | 17, 11, 8 |
| Hudi | 17, 11, 8 |
| Iceberg | 17, 11 |
| Livy | 17, 11, 8 |
| Oozie | 17, 11, 8 |
| 피닉스 | 17, 11, 8 |
| PrestoDB | 8 |
| Spark | 17, 11, 8 |
| Spark RAPIDS | 17, 11, 8 |
| Tez의 Hive 실행 시간 비교 | 17, 11, 8 |
| Trino | 21, 17 |
| Zeppelin | 17, 11, 8 |
| Pig | 17, 11, 8 |
| Zookeeper | 17, 11, 8 |
## 7.10.0 구성 요소 버전
이 릴리스를 통해 Amazon EMR이 설치하는 구성 요소는 다음과 같습니다. 일부는 빅 데이터 애플리케이션 패키지의 일부로 설치됩니다. 나머지는 Amazon EMR에 고유하며 시스템 프로세스 및 기능을 위해 설치됩니다. 이는 일반적으로 `emr` 또는 `aws`로 시작됩니다. 최근 Amazon EMR 릴리스의 빅 데이터 애플리케이션 패키지는 일반적으로 커뮤니티에서 발견된 최신 버전입니다. 가능한 한 빨리 Amazon EMR에서 커뮤니티 릴리스를 제공합니다.
Amazon EMR의 일부 구성 요소는 커뮤니티 버전과 다릅니다. 이러한 구성 요소에는 `CommunityVersion-amzn-EmrVersion` 양식의 버전 레이블이 있습니다. `EmrVersion`은 0에서 시작합니다. 예를 들어, 버전 2.2의 `myapp-component`라는 오픈 소스 커뮤니티 구성 요소가 다른 Amazon EMR 릴리스에 포함되도록 세 번 수정된 경우 해당 릴리스 버전은 `2.2-amzn-2`로 나열됩니다.
| 구성 요소 | 버전 | 설명 |
| --- | --- | --- |
| adot-java-agent | 1.31.0 | 애플리케이션 대몬(daemon)에서 지표를 수집하는 Java 에이전트입니다. |
| delta | 3.3.0-amzn-2 | Delta Lake는 방대한 분석 데이터 세트를 위한 오픈 테이블 형식입니다. |
| emr-amazon-cloudwatch-agent | 1.300032.2-amzn-0 | Amazon EC2 인스턴스에서 내부 시스템 수준 지표와 사용자 지정 애플리케이션 지표를 수집하는 애플리케이션입니다. |
| emr-ddb | 5.7.0 | 하둡 에코시스템 애플리케이션용 Amazon DynamoDB 커넥터 |
| emr-goodies | 3.19.0 | 편리한 하둡 에코시스템용 추가 라이브러리 |
| emr-kinesis | 3.23.0 | 하둡 에코시스템 애플리케이션용 Amazon Kinesis 커넥터. |
| emr-notebook-env | 1.18.0 | Jupyter Enterprise Gateway가 포함된 EMR 노트북용 Conda 환경 |
| emr-s3-dist-cp | 2.40.0 | Amazon S3용으로 최적화된 분사 복사 애플리케이션. |
| emr-s3-select | 2.19.0 | EMR S3Select 커넥터 |
| emr-wal-cli | 1.3.4 | emrwal 목록/삭제에 사용되는 CLI입니다. |
| emrfs | 2.71.0 | 하둡 에코시스템 애플리케이션용 Amazon S3 커넥터. |
| flink-client | 1.20.0-amzn-4 | Apache Flink 명령줄 클라이언트 스크립트 및 애플리케이션 |
| flink-jobmanager-config | 1.20.0-amzn-4 | Apache Flink JobManager에 대한 EMR 노드에서 리소스를 관리합니다. |
| hadoop-client | 3.4.1-amzn-2 | 'hdfs', 'hadoop', 'yarn' 등과 같은 하둡 명령줄 클라이언트 |
| hadoop-hdfs-datanode | 3.4.1-amzn-2 | 블록을 저장하는 HDFS 노드 수준 서비스 |
| hadoop-hdfs-library | 3.4.1-amzn-2 | HDFS 명령줄 클라이언트 및 라이브러리 |
| hadoop-hdfs-namenode | 3.4.1-amzn-2 | 파일 이름 및 블록 위치를 추적하는 HDFS 서비스 |
| hadoop-hdfs-journalnode | 3.4.1-amzn-2 | HA 클러스터에서 하둡 파일 시스템 저널을 관리하기 위한 HDFS 서비스 |
| hadoop-httpfs-server | 3.4.1-amzn-2 | HDFS 작업에 대한 HTTP 엔드포인트 |
| hadoop-kms-server | 3.4.1-amzn-2 | 하둡의 KeyProvider API를 기반으로 하는 암호화 키 관리 서버 |
| hadoop-mapred | 3.4.1-amzn-2 | MapReduce 애플리케이션을 실행하는 MapReduce 실행 엔진 라이브러리 |
| hadoop-yarn-nodemanager | 3.4.1-amzn-2 | 개별 노드의 컨테이너를 관리하는 YARN 서비스 |
| hadoop-yarn-resourcemanager | 3.4.1-amzn-2 | 클러스터 리소스 및 분산 애플리케이션을 할당 및 관리하는 YARN 서비스 |
| hadoop-yarn-timeline-server | 3.4.1-amzn-2 | YARN 애플리케이션의 현재 및 기록 정보를 가져오는 서비스 |
| hbase-hmaster | 2.6.2-amzn-1 | 리전 조정 및 관리 명령의 실행을 담당하는 HBase 클러스터용 서비스 |
| hbase-region-server | 2.6.2-amzn-1 | 한 개 이상의 HBase 리전에 서비스를 제공하는 서비스 |
| hbase-client | 2.6.2-amzn-1 | HBase 명령줄 클라이언트 |
| hbase-rest-server | 2.6.2-amzn-1 | HBase용 RESTful HTTP 엔드포인트를 제공하는 서비스 |
| hbase-thrift-server | 2.6.2-amzn-1 | HBase에 Thrift 엔드포인트를 제공하는 서비스 |
| hbase-operator-tools | 2.6.2-amzn-1 | Apache HBase 클러스터용 복구 도구. |
| hcatalog-client | 3.1.3-amzn-19 | hcatalog-server를 조정하기 위한 'hcat' 명령줄 클라이언트 |
| hcatalog-server | 3.1.3-amzn-19 | 분산 애플리케이션용 스토리지 관리 계층, 테이블 및 HCatalog를 제공하는 서비스 |
| hcatalog-webhcat-server | 3.1.3-amzn-19 | HCatalog에 REST 인터페이스를 제공하는 HTTP 엔드포인트 |
| hive-client | 3.1.3-amzn-19 | Hive 명령줄 클라이언트 |
| hive-hbase | 3.1.3-amzn-19 | Hive-hbase 클라이언트 |
| hive-metastore-server | 3.1.3-amzn-19 | 하둡 작업에 대한 SQL용 메타데이터가 저장되는 시맨틱 리포지토리인 Hive 메타스토어에 액세스하기 위한 서비스 |
| hive-server2 | 3.1.3-amzn-19 | Hive 쿼리를 웹 요청으로 수락하기 위한 서비스 |
| hudi | 0.15.0-amzn-7 | 짧은 지연 시간 및 높은 효율성으로 데이터 파이프라인을 구동하는 증분 처리 프레임워크. |
| hudi-presto | 0.15.0-amzn-7 | Hudi로 Presto를 실행하기 위한 번들 라이브러리. |
| hudi-trino | 0.15.0-amzn-7 | Hudi와 함께 Trnio를 실행하기 위한 번들 라이브러리. |
| hudi-spark | 0.15.0-amzn-7 | Hudi와 함께 Spark를 실행하기 위한 번들 라이브러리. |
| hue-server | 4.11.0 | 하둡 에코시스템 애플리케이션을 사용하여 데이터를 분석하는 웹 애플리케이션. |
| iceberg | 1.8.1-amzn-0 | Apache Iceberg는 방대한 분석 데이터 세트를 위한 오픈 테이블 형식입니다. |
| jupyterhub | 1.5.0 | Jupyter Notebook용 다중 사용자 서버 |
| livy-server | 0.8.0-incubating | Apache Spark와 상호작용하기 위한 REST 인터페이스 |
| nginx | 1.12.1 | HTTP인 nginx [engine x] 및 역방향 프록시 서버 |
| mariadb-server | 5.5.68 이상 | MariaDB 데이터베이스 서버. |
| nvidia-cuda | 12.5.0 | Nvidia 드라이버와 Cuda 도구 키트 |
| oozie-client | 5.2.1 | Oozie 명령줄 클라이언트 |
| oozie-server | 5.2.1 | Oozie 워크플로 요청을 수락하는 서비스 |
| opencv | 4.7.0 | 오픈 소스 컴퓨터 비전 라이브러리. |
| phoenix-library | 5.2.1 | 서버 및 클라이언트의 phoenix 라이브러리 |
| phoenix-connectors | 6.0.0 | Spark-3용 Apache Phoenix 커넥터 |
| phoenix-query-server | 6.0.0 | Avatica API에 대한 JSON 형식 액세스 및 프로토콜 버퍼 액세스를 비롯하여 JDBC 액세스를 제공하는 경량 서버 |
| presto-coordinator | 0.287-amzn-4 | presto-worker의 쿼리를 수락하고 쿼리 실행을 관리하는 서비스. |
| presto-worker | 0.287-amzn-4 | 여러 쿼리를 실행하는 서비스. |
| presto-client | 0.287-amzn-4 | Presto 서버가 시작되지 않은 HA 클러스터의 대기 마스터에 설치된 Presto 명령줄 클라이언트. |
| trino-coordinator | 470-amzn-0 | trino-workers의 쿼리를 수락하고 쿼리 실행을 관리하는 서비스. |
| trino-worker | 470-amzn-0 | 여러 쿼리를 실행하는 서비스. |
| trino-client | 470-amzn-0 | Trino 서버가 시작되지 않은 HA 클러스터의 대기 마스터에 설치된 Trino 명령줄 클라이언트. |
| pig-client | 0.17.0 | Pig 명령줄 클라이언트. |
| r | 4.3.2 | 통계 컴퓨팅용 R 프로젝트 |
| ranger-kms-server | 2.0.0 | Apache Ranger 키 관리 시스템 |
| spark-client | 3.5.5-amzn-1 | Spark 명령줄 클라이언트. |
| spark-history-server | 3.5.5-amzn-1 | 완료된 Spark 애플리케이션의 수명에 대해 기록된 이벤트를 조회하는 웹 UI. |
| spark-on-yarn | 3.5.5-amzn-1 | YARN용 인 메모리 실행 엔진. |
| spark-yarn-slave | 3.5.5-amzn-1 | YARN 슬레이브에서 필요한 Apache Spark 라이브러리. |
| spark-rapids | 3.5.5-amzn-1 | GPU로 Apache Spark를 가속화하는 Nvidia Spark RAPIDS 플러그인. |
| tensorflow | 2.18.0 | TensorFlow는 고성능 수치 계산용 오픈 소스 소프트웨어 라이브러리입니다. |
| tez-on-yarn | 0.10.2-amzn-17 | tez YARN 애플리케이션 및 라이브러리. |
| tez-on-worker | 0.10.2-amzn-17 | 워커 노드에 대한 tez YARN 애플리케이션 및 라이브러리. |
| zeppelin-server | 0.11.1 | 대화형 데이터 분석이 가능한 웹 기반 노트북 |
| zookeeper-server | 3.9.3-amzn-2 | 구성 정보 유지 관리, 이름 지정, 분산 동기화 제공 및 그룹 서비스 제공을 위한 중앙 집중식 서비스. |
| zookeeper-client | 3.9.3-amzn-2 | ZooKeeper 명령줄 클라이언트. |
## 7.10.0 구성 분류
구성 분류를 사용하면 애플리케이션을 사용자 지정할 수 있습니다. 이는 종종 `hive-site.xml`과 같이 애플리케이션의 구성 XML 파일에 해당합니다. 자세한 내용은 [애플리케이션 구성](emr-configure-apps.md) 단원을 참조하십시오.
재구성 작업은 실행 중인 클러스터의 인스턴스 그룹에 대한 구성을 지정할 때 수행됩니다. Amazon EMR은 사용자가 수정한 분류에 대한 재구성 작업만 시작합니다. 자세한 내용은 [실행 중인 클러스터에서 인스턴스 그룹 재구성](emr-configure-apps-running-cluster.md) 단원을 참조하십시오.
**emr-7.10.0 분류**
| 분류 | 설명 | 재구성 작업 |
| --- | --- | --- |
| capacity-scheduler | Hadoop capacity-scheduler.xml 파일에서 값을 변경합니다. | Restarts the ResourceManager service. |
| container-executor | Hadoop YARN container-executor.cfg 파일에서 값을 변경합니다. | Not available. |
| container-log4j | Hadoop YARN container-log4j.properties 파일에서 값을 변경합니다. | Not available. |
| core-site | Hadoop core-site.xml 파일에서 값을 변경합니다. | Restarts the Hadoop HDFS services Namenode, SecondaryNamenode, Datanode, ZKFC, and Journalnode. Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts Hadoop KMS, Ranger KMS, HiveServer2, Hive MetaStore, Hadoop Httpfs, and MapReduce-HistoryServer. |
| docker-conf | Docker 관련 설정을 변경합니다. | Not available. |
| emrfs-site | EMRFS 설정을 변경합니다. | Restarts the Hadoop HDFS services Namenode, SecondaryNamenode, Datanode, ZKFC, and Journalnode. Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts HBaseRegionserver, HBaseMaster, HBaseThrift, HBaseRest, HiveServer2, Hive MetaStore, Hadoop Httpfs, and MapReduce-HistoryServer. |
| flink-conf | flink-conf.yaml 설정을 변경합니다. | Restarts Flink history server. |
| flink-log4j | Flink log4j.properties 설정을 변경합니다. | Restarts Flink history server. |
| flink-log4j-session | Kubernetes 및 Yarn 세션에 대한 Flink log4j-session.properties 설정을 변경합니다. | Restarts Flink history server. |
| flink-log4j-cli | Flink log4j-cli.properties 설정을 변경합니다. | Restarts Flink history server. |
| hadoop-env | 모든 Hadoop 구성 요소에 대한 Hadoop 환경에서 값을 변경합니다. | Restarts the Hadoop HDFS services Namenode, SecondaryNamenode, Datanode, ZKFC, and Journalnode. Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts PhoenixQueryserver, HiveServer2, Hive MetaStore, and MapReduce-HistoryServer. |
| hadoop-log4j | Hadoop log4j.properties 파일에서 값을 변경합니다. | Restarts the Hadoop HDFS services SecondaryNamenode, Datanode, and Journalnode. Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts Hadoop KMS, Hadoop Httpfs, and MapReduce-HistoryServer. |
| hadoop-ssl-server | hadoop ssl 서버 구성을 변경합니다. | Not available. |
| hadoop-ssl-client | hadoop ssl 클라이언트 구성을 변경합니다. | Not available. |
| hbase | Apache HBase에 대한 Amazon EMR 큐레이트 설정입니다. | Custom EMR specific property. Sets emrfs-site and hbase-site configs. See those for their associated restarts. |
| hbase-env | HBase 환경에서 값을 변경합니다. | Restarts the HBase services RegionServer, HBaseMaster, ThriftServer, RestServer. |
| hbase-log4j2 | HBase hbase-log4j.properties 파일에서 값을 변경합니다. | Restarts the HBase services RegionServer, HBaseMaster, ThriftServer, RestServer. |
| hbase-metrics | HBase hadoop-metrics2-hbase.properties 파일에서 값을 변경합니다. | Restarts the HBase services RegionServer, HBaseMaster, ThriftServer, RestServer. |
| hbase-policy | HBase hbase-policy.xml 파일에서 값을 변경합니다. | Not available. |
| hbase-site | HBase hbase-site.xml 파일에서 값을 변경합니다. | Restarts the HBase services RegionServer, HBaseMaster, ThriftServer, RestServer. Additionally restarts Phoenix QueryServer. |
| hdfs-encryption-zones | HDFS 암호화 영역을 구성합니다. | This classification should not be reconfigured. |
| hdfs-env | HDFS 환경에서 값을 변경합니다. | Restarts Hadoop HDFS services Namenode, Datanode, and ZKFC. |
| hdfs-site | HDFS hdfs-site.xml에서 값을 변경합니다. | Restarts the Hadoop HDFS services Namenode, SecondaryNamenode, Datanode, ZKFC, and Journalnode. Additionally restarts Hadoop Httpfs. |
| hcatalog-env | HCatalog 환경에서 값을 변경합니다. | Restarts Hive HCatalog Server. |
| hcatalog-server-jndi | HCatalog jndi.properties 환경에서 값을 변경합니다. | Restarts Hive HCatalog Server. |
| hcatalog-server-proto-hive-site | HCatalog proto-hive-site.xml에서 값을 변경합니다. | Restarts Hive HCatalog Server. |
| hcatalog-webhcat-env | HCatalog WebHCat 환경에서 값을 변경합니다. | Restarts Hive WebHCat server. |
| hcatalog-webhcat-log4j2 | HCatalog WebHCat log4j2.properties에서 값을 변경합니다. | Restarts Hive WebHCat server. |
| hcatalog-webhcat-site | HCatalog WebHCat webhcat-site.xml 파일에서 값을 변경합니다. | Restarts Hive WebHCat server. |
| hive | Apache Hive에 대한 Amazon EMR 큐레이트 설정입니다. | Sets configurations to launch Hive LLAP service. |
| hive-beeline-log4j2 | Hive beeline-log4j2.properties 파일에서 값을 변경합니다. | Not available. |
| hive-parquet-logging | Hive parquet-logging.properties 파일에서 값을 변경합니다. | Not available. |
| hive-env | Hive 환경에서 값을 변경합니다. | Restarts HiveServer2, HiveMetastore, and Hive HCatalog-Server. Runs Hive schemaTool CLI commands to verify hive-metastore. |
| hive-exec-log4j2 | Hive hive-exec-log4j2.properties 파일에서 값을 변경합니다. | Not available. |
| hive-llap-daemon-log4j2 | Hive llap-daemon-log4j2.properties 파일에서 값을 변경합니다. | Not available. |
| hive-log4j2 | Hive hive-log4j2.properties 파일에서 값을 변경합니다. | Not available. |
| hive-site | Hive hive-site.xml 파일에서 값을 변경합니다. | Restarts HiveServer2, HiveMetastore, and Hive HCatalog-Server. Runs Hive schemaTool CLI commands to verify hive-metastore. Also restarts Oozie and Zeppelin. |
| hiveserver2-site | Hive Server2 hiveserver2-site.xml 파일에서 값을 변경합니다. | Not available. |
| hue-ini | Hue ini 파일에서 값을 변경합니다. | Restarts Hue. Also activates Hue config override CLI commands to pick up new configurations. |
| httpfs-env | HTTPFS 환경에서 값을 변경합니다. | Restarts Hadoop Httpfs service. |
| httpfs-site | Hadoop httpfs-site.xml 파일에서 값을 변경합니다. | Restarts Hadoop Httpfs service. |
| hadoop-kms-acls | Hadoop kms-acls.xml 파일에서 값을 변경합니다. | Not available. |
| hadoop-kms-env | Hadoop KMS 환경에서 값을 변경합니다. | Restarts Hadoop-KMS service. |
| hadoop-kms-java-home | Hadoop의 KMS java 홈 변경 | Not available. |
| hadoop-kms-log4j | Hadoop kms-log4j.properties 파일에서 값을 변경합니다. | Not available. |
| hadoop-kms-site | Hadoop kms-site.xml 파일에서 값을 변경합니다. | Restarts Hadoop-KMS and Ranger-KMS service. |
| hudi-env | Hudi 환경에서 값을 변경합니다. | Not available. |
| hudi-defaults | Hudi hudi-defaults.conf 파일에서 값을 변경합니다. | Not available. |
| iceberg-defaults | Iceberg iceberg-defaults.conf 파일에서 값을 변경합니다. | Not available. |
| delta-defaults | Delta delta-defaults.conf 파일에서 값을 변경합니다. | Not available. |
| jupyter-notebook-conf | Jupyter Notebook jupyter\$1notebook\$1config.py 파일에서 값을 변경합니다. | Not available. |
| jupyter-hub-conf | JupyterHubs jupyterhub\$1config.py 파일에서 값을 변경합니다. | Not available. |
| jupyter-s3-conf | Jupyter Notebook S3 지속성 구성 | Not available. |
| jupyter-sparkmagic-conf | Sparkmagic config.json 파일에서 값을 변경합니다. | Not available. |
| livy-conf | Livy livy.conf 파일에서 값을 변경합니다. | Restarts Livy Server. |
| livy-env | Livy 환경에서 값을 변경합니다. | Restarts Livy Server. |
| livy-log4j2 | Livy log4j2.properties 설정을 변경합니다. | Restarts Livy Server. |
| mapred-env | MapReduce 애플리케이션 환경에서 값을 변경합니다. | Restarts Hadoop MapReduce-HistoryServer. |
| mapred-site | MapReduce 애플리케이션 mapred-site.xml 파일에서 값을 변경합니다. | Restarts Hadoop MapReduce-HistoryServer. |
| oozie-env | Oozie 환경에서 값을 변경합니다. | Restarts Oozie. |
| oozie-log4j | Oozie oozie-log4j.properties 파일에서 값을 변경합니다. | Restarts Oozie. |
| oozie-site | Oozie oozie-site.xml 파일에서 값을 변경합니다. | Restarts Oozie. |
| phoenix-hbase-metrics | Phoenix hadoop-metrics2-hbase.properties 파일에서 값을 변경합니다. | Not available. |
| phoenix-hbase-site | Phoenix hbase-site.xml 파일에서 값을 변경합니다. | Not available. |
| phoenix-log4j2 | Phoenix log4j2.properties 파일에서 값을 변경합니다. | Restarts Phoenix-QueryServer. |
| phoenix-metrics | Phoenix hadoop-metrics2-phoenix.properties 파일에서 값을 변경합니다. | Not available. |
| pig-env | Pig 환경에서 값을 변경합니다. | Not available. |
| pig-properties | Pig pig.properties 파일에서 값을 변경합니다. | Restarts Oozie. |
| pig-log4j | Pig log4j.properties 파일에서 값을 변경합니다. | Not available. |
| presto-log | Presto log.properties 파일에서 값을 변경합니다. | Restarts Presto-Server (for PrestoDB) |
| presto-config | Presto config.properties 파일에서 값을 변경합니다. | Restarts Presto-Server (for PrestoDB) |
| presto-password-authenticator | Presto password-authenticator.properties 파일에서 값을 변경합니다. | Not available. |
| presto-env | Presto presto-env.sh 파일에서 값을 변경합니다. | Restarts Presto-Server (for PrestoDB) |
| presto-node | Presto node.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-blackhole | Presto blackhole.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-cassandra | Presto cassandra.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-hive | Presto hive.properties 파일에서 값을 변경합니다. | Restarts Presto-Server (for PrestoDB) |
| presto-connector-jmx | Presto jmx.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-kafka | Presto kafka.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-lakeformation | Presto lakeformation.properties 파일에서 값을 변경합니다. | Restarts Presto-Server (for PrestoDB) |
| presto-connector-localfile | Presto localfile.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-memory | Presto memory.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-mongodb | Presto mongodb.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-mysql | Presto mysql.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-postgresql | Presto postgresql.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-raptor | Presto raptor.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-redis | Presto redis.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-redshift | Presto redshift.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-tpch | Presto tpch.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-tpcds | Presto tpcds.properties 파일에서 값을 변경합니다. | Not available. |
| trino-log | Trino log.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-config | Trino config.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-password-authenticator | Trino password-authenticator.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-env | Trino trino-env.sh 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-node | Trino node.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-blackhole | Trino blackhole.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-cassandra | Trino cassandra.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-delta | Trino delta.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-connector-hive | Trino hive.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-exchange-manager | Trino exchange-manager.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-connector-iceberg | Trino iceberg.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-connector-hudi | Trino hudi.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-connector-jmx | Trino jmx.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-kafka | Trino kafka.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-localfile | Trino localfile.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-memory | Trino memory.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-mongodb | Trino mongodb.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-mysql | Trino mysql.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-postgresql | Trino postgresql.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-raptor | Trino raptor.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-redis | Trino redis.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-redshift | Trino redshift.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-tpch | Trino tpch.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-tpcds | Trino tpcds.properties 파일에서 값을 변경합니다. | Not available. |
| ranger-kms-dbks-site | Ranger KMS dbks-site.xml 파일에서 값을 변경합니다. | Restarts Ranger KMS Server. |
| ranger-kms-site | Ranger KMS ranger-kms-site.xml 파일에서 값을 변경합니다. | Restarts Ranger KMS Server. |
| ranger-kms-env | Ranger KMS 환경에서 값을 변경합니다. | Restarts Ranger KMS Server. |
| ranger-kms-logback | Ranger KMS kms-logback.xml 파일에서 값을 변경합니다. | Not available. |
| ranger-kms-db-ca | Ranger KMS와의 MySQL SSL 연결에서 CA 파일의 값을 변경합니다. | Not available. |
| spark | Apache Spark에 대한 Amazon EMR 큐레이트 설정입니다. | This property modifies spark-defaults. See actions there. |
| spark-defaults | Spark spark-defaults.conf 파일에서 값을 변경합니다. | Restarts Spark history server and Spark thrift server. |
| spark-env | Spark 환경에서 값을 변경합니다. | Restarts Spark history server and Spark thrift server. |
| spark-hive-site | Spark hive-site.xml 파일에서 값을 변경합니다. | Not available. |
| spark-log4j2 | Spark log4j2.properties 파일에서 값을 변경합니다. | Restarts Spark history server and Spark thrift server. |
| spark-metrics | Spark metrics.properties 파일에서 값을 변경합니다. | Restarts Spark history server and Spark thrift server. |
| tez-site | Tez tez-site.xml 파일에서 값을 변경합니다. | Restart Oozie and HiveServer2. |
| yarn-env | YARN 환경에서 값을 변경합니다. | Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts MapReduce-HistoryServer. |
| yarn-site | YARN yarn-site.xml 파일에서 값을 변경합니다. | Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts Livy Server and MapReduce-HistoryServer. |
| zeppelin-env | Zeppelin 환경에서 값을 변경합니다. | Restarts Zeppelin. |
| zeppelin-site | zeppelin-site.xml에서 구성 설정을 변경합니다. | Restarts Zeppelin. |
| zookeeper-config | ZooKeeper zoo.cfg 파일에서 값을 변경합니다. | Restarts Zookeeper server. |
| zookeeper-logback | ZooKeeper logback.xml 파일에서 값을 변경합니다. | Restarts Zookeeper server. |
| emr-metrics | 이 노드에 대한 emr 지표 설정을 변경합니다. | Restarts the CloudWatchAgent service. |
## 7.10.0 변경 로그
**7.10.0 릴리스 및 릴리스 정보에 대한 변경 로그**
| Date | 이벤트 | 설명 |
| --- | --- | --- |
| 2025-08-15 | 문서 게시 | Amazon EMR 7.10.0 릴리스 정보가 처음 게시됨 |
| 2025-08-15 | 배포 완료 | [지원되는 모든 리전](https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/)에 Amazon EMR 7.10.0 완전 배포 |
| 2025-08-15 | 초기 제한 릴리스 | Amazon EMR 7.10.0이 초기 상용 리전에 처음 배포됨 |
# Amazon EMR 릴리스 7.9.0
## 7.9.0 지원 수명 주기
다음 표에서는 Amazon EMR 릴리스 7.9.0에 지원되는 수명 주기 날짜를 설명합니다.
| 지원 단계 | Date |
| --- | --- |
| 초기 릴리스 날짜 | 2025년 5월 19일 |
| 표준 지원 종료 시점 | 2027년 5월 19일 |
| 지원 종료 | 2027년 5월 20일 |
| 수명 종료 | 2028년 5월 19일 |
## 7.9.0 애플리케이션 버전
이 릴리스에 포함된 애플리케이션은 [https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Install-CloudWatch-Agent.html](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Install-CloudWatch-Agent.html), [https://delta.io/](https://delta.io/), [https://flink.apache.org/](https://flink.apache.org/), [http://hbase.apache.org/](http://hbase.apache.org/), [https://cwiki.apache.org/confluence/display/Hive/HCatalog](https://cwiki.apache.org/confluence/display/Hive/HCatalog), [http://hadoop.apache.org/docs/current/](http://hadoop.apache.org/docs/current/), [http://hive.apache.org/](http://hive.apache.org/), [https://hudi.apache.org](https://hudi.apache.org), [http://gethue.com/](http://gethue.com/), [https://iceberg.apache.org/](https://iceberg.apache.org/), [https://jupyter-enterprise-gateway.readthedocs.io/en/latest/](https://jupyter-enterprise-gateway.readthedocs.io/en/latest/), [https://jupyterhub.readthedocs.io/en/latest/#](https://jupyterhub.readthedocs.io/en/latest/#), [https://livy.incubator.apache.org/](https://livy.incubator.apache.org/), [http://oozie.apache.org/](http://oozie.apache.org/), [https://phoenix.apache.org/](https://phoenix.apache.org/), [http://pig.apache.org/](http://pig.apache.org/), [https://prestodb.io/](https://prestodb.io/), [https://spark.apache.org/docs/latest/](https://spark.apache.org/docs/latest/), [https://www.tensorflow.org/](https://www.tensorflow.org/), [https://tez.apache.org/](https://tez.apache.org/), [https://trino.io/](https://trino.io/), [https://zeppelin.incubator.apache.org/](https://zeppelin.incubator.apache.org/), [https://zookeeper.apache.org](https://zookeeper.apache.org)입니다.
아래 테이블에는 이번 Amazon EMR 릴리스에서 사용할 수 있는 애플리케이션 버전과 이전 세 가지 Amazon EMR 릴리스(해당하는 경우)의 애플리케이션 버전이 나와 있습니다.
각 Amazon EMR 릴리스에서 애플리케이션 버전의 전체 기록은 다음 주제를 참조하세요.
+ [Amazon EMR 7.x 릴리스의 애플리케이션 버전](emr-release-app-versions-7.x.md)
+ [Amazon EMR 6.x 릴리스의 애플리케이션 버전](emr-release-app-versions-6.x.md)
+ [Amazon EMR 5.x 릴리스의 애플리케이션 버전](emr-release-app-versions-5.x.md)
+ [Amazon EMR 4.x 릴리스의 애플리케이션 버전](emr-release-app-versions-4.x.md)
**애플리케이션 버전 정보**
| | emr-7.9.0 | emr-7.8.0 | emr-7.7.0 | emr-7.6.0 |
| --- | --- | --- | --- | --- |
| AWS Java용 SDK | 2.31.16, 1.12.782 | 2.29.52, 1.12.780 | 2.29.44, 1.12.780 | 2.29.25, 1.12.779 |
| Python | 3.9, 3.11 | 3.9, 3.11 | 3.9, 3.11 | 3.9, 3.11 |
| Scala | 2.12.18 | 2.12.18 | 2.12.18 | 2.12.18 |
| AmazonCloudWatchAgent | 1.300032.2-amzn-0 | 1.300032.2-amzn-0 | 1.300032.2-amzn-0 | 1.300032.2-amzn-0 |
| Delta | 3.3.0-amzn-1 | 3.3.0-amzn-0 | 3.2.1-amzn-2 | 3.2.1-amzn-1 |
| Flink | 1.20.0-amzn-3 | 1.20.0-amzn-2 | 1.20.0-amzn-1 | 1.20.0-amzn-0 |
| Ganglia | - | - | - | - |
| HBase | 2.6.2-amzn-0 | 2.6.1-amzn-2 | 2.6.1-amzn-1 | 2.6.1-amzn-0 |
| HCatalog | 3.1.3-amzn-18 | 3.1.3-amzn-17 | 3.1.3-amzn-16 | 3.1.3-amzn-15 |
| Hadoop | 3.4.1-amzn-1 | 3.4.1-amzn-0 | 3.4.0-amzn-3 | 3.4.0-amzn-2 |
| Hive | 3.1.3-amzn-18 | 3.1.3-amzn-17 | 3.1.3-amzn-16 | 3.1.3-amzn-15 |
| Hudi | 0.15.0-amzn-6 | 0.15.0-amzn-5 | 0.15.0-amzn-4 | 0.15.0-amzn-3 |
| Hue | 4.11.0 | 4.11.0 | 4.11.0 | 4.11.0 |
| Iceberg | 1.7.1-amzn-2 | 1.7.1-amzn-1 | 1.7.1-amzn-0 | 1.6.1-amzn-2 |
| JupyterEnterpriseGateway | 2.6.0 | 2.6.0 | 2.6.0 | 2.6.0 |
| JupyterHub | 1.5.0 | 1.5.0 | 1.5.0 | 1.5.0 |
| Livy | 0.8.0-incubating | 0.8.0-incubating | 0.8.0-incubating | 0.8.0-incubating |
| MXNet | - | - | - | - |
| Mahout | - | - | - | - |
| Oozie | 5.2.1 | 5.2.1 | 5.2.1 | 5.2.1 |
| Phoenix | 5.2.1 | 5.2.1 | 5.2.1 | 5.2.0 |
| Pig | 0.17.0 | 0.17.0 | 0.17.0 | 0.17.0 |
| Presto | 0.287-amzn-3 | 0.287-amzn-2 | 0.287-amzn-1 | 0.287-amzn-1 |
| Spark | 3.5.5-amzn-0 | 3.5.4-amzn-0 | 3.5.3-amzn-1 | 3.5.3-amzn-0 |
| Sqoop | - | - | - | - |
| TensorFlow | 2.16.1 | 2.16.1 | 2.16.1 | 2.16.1 |
| Tez | 0.10.2-amzn-16 | 0.10.2-amzn-15 | 0.10.2-amzn-14 | 0.10.2-amzn-13 |
| Trino (PrestoSQL) | 467-amzn-2 | 467-amzn-1 | 467-amzn-0 | 457-amzn-0 |
| Zeppelin | 0.11.1 | 0.11.1 | 0.11.1 | 0.11.1 |
| ZooKeeper | 3.9.3-amzn-1 | 3.9.3-amzn-0 | 3.9.2-amzn-1 | 3.9.2-amzn-0 |
# 7.9.0 일반적인 취약성 및 노출
다음 표에는 Amazon EMR 7.9.0의 권장 구성에서 실행되는 EMR 클러스터에 영향을 주지 않는 모든 CVEs가 나열되어 있습니다. Amazon EMR은 업스트림 오픈 소스의 수정 사항 가용성에 종속되어 있으며, Amazon EMR이 수정 사항을 확인한 후 90일 이내에 코어 엔진 구성 요소의 일부로 안정적인 최신 버전을 제공합니다.
이 표는 2025년 5월 12일에 업데이트되었습니다.
| CVE ID | 심각도 | CVE 세부 정보 URL |
| --- | --- | --- |
| CVE-2015-1832 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2015-1832](https://nvd.nist.gov/vuln/detail/CVE-2015-1832) |
| CVE-2016-5018 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2016-5018](https://nvd.nist.gov/vuln/detail/CVE-2016-5018) |
| CVE-2017-15095 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2017-15095](https://nvd.nist.gov/vuln/detail/CVE-2017-15095) |
| CVE-2017-17485 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2017-17485](https://nvd.nist.gov/vuln/detail/CVE-2017-17485) |
| CVE-2017-7525 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2017-7525](https://nvd.nist.gov/vuln/detail/CVE-2017-7525) |
| CVE-2018-11307 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-11307](https://nvd.nist.gov/vuln/detail/CVE-2018-11307) |
| CVE-2018-11307 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-11307](https://nvd.nist.gov/vuln/detail/CVE-2018-11307) |
| CVE-2018-14718 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-14718](https://nvd.nist.gov/vuln/detail/CVE-2018-14718) |
| CVE-2018-14718 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-14718](https://nvd.nist.gov/vuln/detail/CVE-2018-14718) |
| CVE-2018-14719 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-14719](https://nvd.nist.gov/vuln/detail/CVE-2018-14719) |
| CVE-2018-14719 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-14719](https://nvd.nist.gov/vuln/detail/CVE-2018-14719) |
| CVE-2018-14720 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-14720](https://nvd.nist.gov/vuln/detail/CVE-2018-14720) |
| CVE-2018-14720 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-14720](https://nvd.nist.gov/vuln/detail/CVE-2018-14720) |
| CVE-2018-14721 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-14721](https://nvd.nist.gov/vuln/detail/CVE-2018-14721) |
| CVE-2018-14721 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-14721](https://nvd.nist.gov/vuln/detail/CVE-2018-14721) |
| CVE-2018-19360 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-19360](https://nvd.nist.gov/vuln/detail/CVE-2018-19360) |
| CVE-2018-19360 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-19360](https://nvd.nist.gov/vuln/detail/CVE-2018-19360) |
| CVE-2018-19361 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-19361](https://nvd.nist.gov/vuln/detail/CVE-2018-19361) |
| CVE-2018-19361 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-19361](https://nvd.nist.gov/vuln/detail/CVE-2018-19361) |
| CVE-2018-19362 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-19362](https://nvd.nist.gov/vuln/detail/CVE-2018-19362) |
| CVE-2018-19362 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-19362](https://nvd.nist.gov/vuln/detail/CVE-2018-19362) |
| CVE-2018-7489 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-7489](https://nvd.nist.gov/vuln/detail/CVE-2018-7489) |
| CVE-2018-7489 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-7489](https://nvd.nist.gov/vuln/detail/CVE-2018-7489) |
| CVE-2019-10202 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-10202](https://nvd.nist.gov/vuln/detail/CVE-2019-10202) |
| CVE-2019-14379 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14379](https://nvd.nist.gov/vuln/detail/CVE-2019-14379) |
| CVE-2019-14379 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14379](https://nvd.nist.gov/vuln/detail/CVE-2019-14379) |
| CVE-2019-14540 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14540](https://nvd.nist.gov/vuln/detail/CVE-2019-14540) |
| CVE-2019-14540 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14540](https://nvd.nist.gov/vuln/detail/CVE-2019-14540) |
| CVE-2019-14892 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14892](https://nvd.nist.gov/vuln/detail/CVE-2019-14892) |
| CVE-2019-14892 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14892](https://nvd.nist.gov/vuln/detail/CVE-2019-14892) |
| CVE-2019-14893 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14893](https://nvd.nist.gov/vuln/detail/CVE-2019-14893) |
| CVE-2019-14893 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14893](https://nvd.nist.gov/vuln/detail/CVE-2019-14893) |
| CVE-2019-16335 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-16335](https://nvd.nist.gov/vuln/detail/CVE-2019-16335) |
| CVE-2019-16335 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-16335](https://nvd.nist.gov/vuln/detail/CVE-2019-16335) |
| CVE-2019-16942 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-16942](https://nvd.nist.gov/vuln/detail/CVE-2019-16942) |
| CVE-2019-16942 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-16942](https://nvd.nist.gov/vuln/detail/CVE-2019-16942) |
| CVE-2019-16943 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-16943](https://nvd.nist.gov/vuln/detail/CVE-2019-16943) |
| CVE-2019-16943 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-16943](https://nvd.nist.gov/vuln/detail/CVE-2019-16943) |
| CVE-2019-17267 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-17267](https://nvd.nist.gov/vuln/detail/CVE-2019-17267) |
| CVE-2019-17267 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-17267](https://nvd.nist.gov/vuln/detail/CVE-2019-17267) |
| CVE-2019-17531 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-17531](https://nvd.nist.gov/vuln/detail/CVE-2019-17531) |
| CVE-2019-17531 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-17531](https://nvd.nist.gov/vuln/detail/CVE-2019-17531) |
| CVE-2019-20330 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-20330](https://nvd.nist.gov/vuln/detail/CVE-2019-20330) |
| CVE-2019-20330 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-20330](https://nvd.nist.gov/vuln/detail/CVE-2019-20330) |
| CVE-2020-8840 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8840](https://nvd.nist.gov/vuln/detail/CVE-2020-8840) |
| CVE-2020-8840 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8840](https://nvd.nist.gov/vuln/detail/CVE-2020-8840) |
| CVE-2020-9546 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-9546](https://nvd.nist.gov/vuln/detail/CVE-2020-9546) |
| CVE-2020-9546 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-9546](https://nvd.nist.gov/vuln/detail/CVE-2020-9546) |
| CVE-2020-9547 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-9547](https://nvd.nist.gov/vuln/detail/CVE-2020-9547) |
| CVE-2020-9547 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-9547](https://nvd.nist.gov/vuln/detail/CVE-2020-9547) |
| CVE-2020-9548 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-9548](https://nvd.nist.gov/vuln/detail/CVE-2020-9548) |
| CVE-2020-9548 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-9548](https://nvd.nist.gov/vuln/detail/CVE-2020-9548) |
| CVE-2022-1471 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-1471](https://nvd.nist.gov/vuln/detail/CVE-2022-1471) |
| CVE-2022-1471 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-1471](https://nvd.nist.gov/vuln/detail/CVE-2022-1471) |
| CVE-2022-37865 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-37865](https://nvd.nist.gov/vuln/detail/CVE-2022-37865) |
| CVE-2022-39135 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-39135](https://nvd.nist.gov/vuln/detail/CVE-2022-39135) |
| CVE-2022-42889 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42889](https://nvd.nist.gov/vuln/detail/CVE-2022-42889) |
| CVE-2022-46337 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-46337](https://nvd.nist.gov/vuln/detail/CVE-2022-46337) |
| CVE-2022-46337 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-46337](https://nvd.nist.gov/vuln/detail/CVE-2022-46337) |
| CVE-2024-51504 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2024-51504](https://nvd.nist.gov/vuln/detail/CVE-2024-51504) |
| CVE-2024-51504 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2024-51504](https://nvd.nist.gov/vuln/detail/CVE-2024-51504) |
| CVE-2024-52046 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2024-52046](https://nvd.nist.gov/vuln/detail/CVE-2024-52046) |
| CVE-2024-52046 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2024-52046](https://nvd.nist.gov/vuln/detail/CVE-2024-52046) |
| CVE-2024-52577 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2024-52577](https://nvd.nist.gov/vuln/detail/CVE-2024-52577) |
| CVE-2024-53990 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2024-53990](https://nvd.nist.gov/vuln/detail/CVE-2024-53990) |
| CVE-2024-56325 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2024-56325](https://nvd.nist.gov/vuln/detail/CVE-2024-56325) |
| CVE-2025-30065 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2025-30065](https://nvd.nist.gov/vuln/detail/CVE-2025-30065) |
| CVE-2015-5237 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2015-5237](https://nvd.nist.gov/vuln/detail/CVE-2015-5237) |
| CVE-2015-5237 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2015-5237](https://nvd.nist.gov/vuln/detail/CVE-2015-5237) |
| CVE-2016-6796 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2016-6796](https://nvd.nist.gov/vuln/detail/CVE-2016-6796) |
| CVE-2018-1000180 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-1000180](https://nvd.nist.gov/vuln/detail/CVE-2018-1000180) |
| CVE-2018-12022 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-12022](https://nvd.nist.gov/vuln/detail/CVE-2018-12022) |
| CVE-2018-12022 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-12022](https://nvd.nist.gov/vuln/detail/CVE-2018-12022) |
| CVE-2018-12023 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-12023](https://nvd.nist.gov/vuln/detail/CVE-2018-12023) |
| CVE-2018-12023 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-12023](https://nvd.nist.gov/vuln/detail/CVE-2018-12023) |
| CVE-2018-5968 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-5968](https://nvd.nist.gov/vuln/detail/CVE-2018-5968) |
| CVE-2019-0205 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-0205](https://nvd.nist.gov/vuln/detail/CVE-2019-0205) |
| CVE-2019-0205 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-0205](https://nvd.nist.gov/vuln/detail/CVE-2019-0205) |
| CVE-2019-10172 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-10172](https://nvd.nist.gov/vuln/detail/CVE-2019-10172) |
| CVE-2019-12086 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-12086](https://nvd.nist.gov/vuln/detail/CVE-2019-12086) |
| CVE-2019-12086 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-12086](https://nvd.nist.gov/vuln/detail/CVE-2019-12086) |
| CVE-2019-14439 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14439](https://nvd.nist.gov/vuln/detail/CVE-2019-14439) |
| CVE-2019-14439 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14439](https://nvd.nist.gov/vuln/detail/CVE-2019-14439) |
| CVE-2020-10650 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10650](https://nvd.nist.gov/vuln/detail/CVE-2020-10650) |
| CVE-2020-10650 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10650](https://nvd.nist.gov/vuln/detail/CVE-2020-10650) |
| CVE-2020-10672 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10672](https://nvd.nist.gov/vuln/detail/CVE-2020-10672) |
| CVE-2020-10672 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10672](https://nvd.nist.gov/vuln/detail/CVE-2020-10672) |
| CVE-2020-10673 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10673](https://nvd.nist.gov/vuln/detail/CVE-2020-10673) |
| CVE-2020-10673 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10673](https://nvd.nist.gov/vuln/detail/CVE-2020-10673) |
| CVE-2020-10968 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10968](https://nvd.nist.gov/vuln/detail/CVE-2020-10968) |
| CVE-2020-10968 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10968](https://nvd.nist.gov/vuln/detail/CVE-2020-10968) |
| CVE-2020-10969 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10969](https://nvd.nist.gov/vuln/detail/CVE-2020-10969) |
| CVE-2020-10969 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10969](https://nvd.nist.gov/vuln/detail/CVE-2020-10969) |
| CVE-2020-11111 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11111](https://nvd.nist.gov/vuln/detail/CVE-2020-11111) |
| CVE-2020-11111 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11111](https://nvd.nist.gov/vuln/detail/CVE-2020-11111) |
| CVE-2020-11112 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11112](https://nvd.nist.gov/vuln/detail/CVE-2020-11112) |
| CVE-2020-11112 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11112](https://nvd.nist.gov/vuln/detail/CVE-2020-11112) |
| CVE-2020-11113 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11113](https://nvd.nist.gov/vuln/detail/CVE-2020-11113) |
| CVE-2020-11113 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11113](https://nvd.nist.gov/vuln/detail/CVE-2020-11113) |
| CVE-2020-11619 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11619](https://nvd.nist.gov/vuln/detail/CVE-2020-11619) |
| CVE-2020-11619 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11619](https://nvd.nist.gov/vuln/detail/CVE-2020-11619) |
| CVE-2020-11620 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11620](https://nvd.nist.gov/vuln/detail/CVE-2020-11620) |
| CVE-2020-11620 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11620](https://nvd.nist.gov/vuln/detail/CVE-2020-11620) |
| CVE-2020-13949 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-13949](https://nvd.nist.gov/vuln/detail/CVE-2020-13949) |
| CVE-2020-13949 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-13949](https://nvd.nist.gov/vuln/detail/CVE-2020-13949) |
| CVE-2020-13949 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-13949](https://nvd.nist.gov/vuln/detail/CVE-2020-13949) |
| CVE-2020-14060 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14060](https://nvd.nist.gov/vuln/detail/CVE-2020-14060) |
| CVE-2020-14060 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14060](https://nvd.nist.gov/vuln/detail/CVE-2020-14060) |
| CVE-2020-14061 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14061](https://nvd.nist.gov/vuln/detail/CVE-2020-14061) |
| CVE-2020-14061 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14061](https://nvd.nist.gov/vuln/detail/CVE-2020-14061) |
| CVE-2020-14062 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14062](https://nvd.nist.gov/vuln/detail/CVE-2020-14062) |
| CVE-2020-14062 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14062](https://nvd.nist.gov/vuln/detail/CVE-2020-14062) |
| CVE-2020-14195 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14195](https://nvd.nist.gov/vuln/detail/CVE-2020-14195) |
| CVE-2020-14195 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14195](https://nvd.nist.gov/vuln/detail/CVE-2020-14195) |
| CVE-2020-24616 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-24616](https://nvd.nist.gov/vuln/detail/CVE-2020-24616) |
| CVE-2020-24616 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-24616](https://nvd.nist.gov/vuln/detail/CVE-2020-24616) |
| CVE-2020-24750 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-24750](https://nvd.nist.gov/vuln/detail/CVE-2020-24750) |
| CVE-2020-24750 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-24750](https://nvd.nist.gov/vuln/detail/CVE-2020-24750) |
| CVE-2020-25649 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-25649](https://nvd.nist.gov/vuln/detail/CVE-2020-25649) |
| CVE-2020-28052 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-28052](https://nvd.nist.gov/vuln/detail/CVE-2020-28052) |
| CVE-2020-35490 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-35490](https://nvd.nist.gov/vuln/detail/CVE-2020-35490) |
| CVE-2020-35490 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-35490](https://nvd.nist.gov/vuln/detail/CVE-2020-35490) |
| CVE-2020-35491 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-35491](https://nvd.nist.gov/vuln/detail/CVE-2020-35491) |
| CVE-2020-35491 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-35491](https://nvd.nist.gov/vuln/detail/CVE-2020-35491) |
| CVE-2020-35728 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-35728](https://nvd.nist.gov/vuln/detail/CVE-2020-35728) |
| CVE-2020-35728 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-35728](https://nvd.nist.gov/vuln/detail/CVE-2020-35728) |
| CVE-2020-36179 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36179](https://nvd.nist.gov/vuln/detail/CVE-2020-36179) |
| CVE-2020-36179 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36179](https://nvd.nist.gov/vuln/detail/CVE-2020-36179) |
| CVE-2020-36180 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36180](https://nvd.nist.gov/vuln/detail/CVE-2020-36180) |
| CVE-2020-36180 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36180](https://nvd.nist.gov/vuln/detail/CVE-2020-36180) |
| CVE-2020-36181 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36181](https://nvd.nist.gov/vuln/detail/CVE-2020-36181) |
| CVE-2020-36181 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36181](https://nvd.nist.gov/vuln/detail/CVE-2020-36181) |
| CVE-2020-36182 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36182](https://nvd.nist.gov/vuln/detail/CVE-2020-36182) |
| CVE-2020-36182 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36182](https://nvd.nist.gov/vuln/detail/CVE-2020-36182) |
| CVE-2020-36183 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36183](https://nvd.nist.gov/vuln/detail/CVE-2020-36183) |
| CVE-2020-36183 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36183](https://nvd.nist.gov/vuln/detail/CVE-2020-36183) |
| CVE-2020-36184 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36184](https://nvd.nist.gov/vuln/detail/CVE-2020-36184) |
| CVE-2020-36184 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36184](https://nvd.nist.gov/vuln/detail/CVE-2020-36184) |
| CVE-2020-36185 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36185](https://nvd.nist.gov/vuln/detail/CVE-2020-36185) |
| CVE-2020-36185 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36185](https://nvd.nist.gov/vuln/detail/CVE-2020-36185) |
| CVE-2020-36186 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36186](https://nvd.nist.gov/vuln/detail/CVE-2020-36186) |
| CVE-2020-36186 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36186](https://nvd.nist.gov/vuln/detail/CVE-2020-36186) |
| CVE-2020-36187 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36187](https://nvd.nist.gov/vuln/detail/CVE-2020-36187) |
| CVE-2020-36187 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36187](https://nvd.nist.gov/vuln/detail/CVE-2020-36187) |
| CVE-2020-36188 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36188](https://nvd.nist.gov/vuln/detail/CVE-2020-36188) |
| CVE-2020-36188 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36188](https://nvd.nist.gov/vuln/detail/CVE-2020-36188) |
| CVE-2020-36189 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36189](https://nvd.nist.gov/vuln/detail/CVE-2020-36189) |
| CVE-2020-36189 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36189](https://nvd.nist.gov/vuln/detail/CVE-2020-36189) |
| CVE-2020-36518 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36518](https://nvd.nist.gov/vuln/detail/CVE-2020-36518) |
| CVE-2020-36518 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36518](https://nvd.nist.gov/vuln/detail/CVE-2020-36518) |
| CVE-2021-20190 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-20190](https://nvd.nist.gov/vuln/detail/CVE-2021-20190) |
| CVE-2021-20190 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-20190](https://nvd.nist.gov/vuln/detail/CVE-2021-20190) |
| CVE-2021-31684 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-31684](https://nvd.nist.gov/vuln/detail/CVE-2021-31684) |
| CVE-2021-34538 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-34538](https://nvd.nist.gov/vuln/detail/CVE-2021-34538) |
| CVE-2021-34538 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-34538](https://nvd.nist.gov/vuln/detail/CVE-2021-34538) |
| CVE-2021-34538 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-34538](https://nvd.nist.gov/vuln/detail/CVE-2021-34538) |
| CVE-2022-25647 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-25647](https://nvd.nist.gov/vuln/detail/CVE-2022-25647) |
| CVE-2022-25647 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-25647](https://nvd.nist.gov/vuln/detail/CVE-2022-25647) |
| CVE-2022-25647 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-25647](https://nvd.nist.gov/vuln/detail/CVE-2022-25647) |
| CVE-2022-25857 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-25857](https://nvd.nist.gov/vuln/detail/CVE-2022-25857) |
| CVE-2022-3171 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3171](https://nvd.nist.gov/vuln/detail/CVE-2022-3171) |
| CVE-2022-3171 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3171](https://nvd.nist.gov/vuln/detail/CVE-2022-3171) |
| CVE-2022-3171 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3171](https://nvd.nist.gov/vuln/detail/CVE-2022-3171) |
| CVE-2022-3509 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3509](https://nvd.nist.gov/vuln/detail/CVE-2022-3509) |
| CVE-2022-3509 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3509](https://nvd.nist.gov/vuln/detail/CVE-2022-3509) |
| CVE-2022-3509 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3509](https://nvd.nist.gov/vuln/detail/CVE-2022-3509) |
| CVE-2022-3510 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3510](https://nvd.nist.gov/vuln/detail/CVE-2022-3510) |
| CVE-2022-3510 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3510](https://nvd.nist.gov/vuln/detail/CVE-2022-3510) |
| CVE-2022-3510 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3510](https://nvd.nist.gov/vuln/detail/CVE-2022-3510) |
| CVE-2022-36364 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-36364](https://nvd.nist.gov/vuln/detail/CVE-2022-36364) |
| CVE-2022-37866 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-37866](https://nvd.nist.gov/vuln/detail/CVE-2022-37866) |
| CVE-2022-40149 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-40149](https://nvd.nist.gov/vuln/detail/CVE-2022-40149) |
| CVE-2022-40149 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-40149](https://nvd.nist.gov/vuln/detail/CVE-2022-40149) |
| CVE-2022-40150 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-40150](https://nvd.nist.gov/vuln/detail/CVE-2022-40150) |
| CVE-2022-40150 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-40150](https://nvd.nist.gov/vuln/detail/CVE-2022-40150) |
| CVE-2022-42003 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42003](https://nvd.nist.gov/vuln/detail/CVE-2022-42003) |
| CVE-2022-42003 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42003](https://nvd.nist.gov/vuln/detail/CVE-2022-42003) |
| CVE-2022-42003 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42003](https://nvd.nist.gov/vuln/detail/CVE-2022-42003) |
| CVE-2022-42003 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42003](https://nvd.nist.gov/vuln/detail/CVE-2022-42003) |
| CVE-2022-42003 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42003](https://nvd.nist.gov/vuln/detail/CVE-2022-42003) |
| CVE-2022-42004 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42004](https://nvd.nist.gov/vuln/detail/CVE-2022-42004) |
| CVE-2022-42004 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42004](https://nvd.nist.gov/vuln/detail/CVE-2022-42004) |
| CVE-2022-42004 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42004](https://nvd.nist.gov/vuln/detail/CVE-2022-42004) |
| CVE-2022-42004 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42004](https://nvd.nist.gov/vuln/detail/CVE-2022-42004) |
| CVE-2022-45685 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-45685](https://nvd.nist.gov/vuln/detail/CVE-2022-45685) |
| CVE-2022-45685 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-45685](https://nvd.nist.gov/vuln/detail/CVE-2022-45685) |
| CVE-2022-45693 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-45693](https://nvd.nist.gov/vuln/detail/CVE-2022-45693) |
| CVE-2022-45693 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-45693](https://nvd.nist.gov/vuln/detail/CVE-2022-45693) |
| CVE-2022-46751 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-46751](https://nvd.nist.gov/vuln/detail/CVE-2022-46751) |
| CVE-2022-46751 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-46751](https://nvd.nist.gov/vuln/detail/CVE-2022-46751) |
| CVE-2023-1370 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-1370](https://nvd.nist.gov/vuln/detail/CVE-2023-1370) |
| CVE-2023-1436 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-1436](https://nvd.nist.gov/vuln/detail/CVE-2023-1436) |
| CVE-2023-1436 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-1436](https://nvd.nist.gov/vuln/detail/CVE-2023-1436) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-3635 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-3635](https://nvd.nist.gov/vuln/detail/CVE-2023-3635) |
| CVE-2023-39410 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-39410](https://nvd.nist.gov/vuln/detail/CVE-2023-39410) |
| CVE-2023-5072 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-5072](https://nvd.nist.gov/vuln/detail/CVE-2023-5072) |
| CVE-2023-6378 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-6378](https://nvd.nist.gov/vuln/detail/CVE-2023-6378) |
| CVE-2023-6378 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-6378](https://nvd.nist.gov/vuln/detail/CVE-2023-6378) |
| CVE-2023-6481 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-6481](https://nvd.nist.gov/vuln/detail/CVE-2023-6481) |
| CVE-2023-6481 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-6481](https://nvd.nist.gov/vuln/detail/CVE-2023-6481) |
| CVE-2024-13009 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-13009](https://nvd.nist.gov/vuln/detail/CVE-2024-13009) |
| CVE-2024-13009 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-13009](https://nvd.nist.gov/vuln/detail/CVE-2024-13009) |
| CVE-2024-29131 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-29131](https://nvd.nist.gov/vuln/detail/CVE-2024-29131) |
| CVE-2024-29857 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-29857](https://nvd.nist.gov/vuln/detail/CVE-2024-29857) |
| CVE-2024-29857 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-29857](https://nvd.nist.gov/vuln/detail/CVE-2024-29857) |
| CVE-2024-29857 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-29857](https://nvd.nist.gov/vuln/detail/CVE-2024-29857) |
| CVE-2024-30172 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-30172](https://nvd.nist.gov/vuln/detail/CVE-2024-30172) |
| CVE-2024-30172 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-30172](https://nvd.nist.gov/vuln/detail/CVE-2024-30172) |
| CVE-2024-34447 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-34447](https://nvd.nist.gov/vuln/detail/CVE-2024-34447) |
| CVE-2024-34447 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-34447](https://nvd.nist.gov/vuln/detail/CVE-2024-34447) |
| CVE-2024-36114 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-36114](https://nvd.nist.gov/vuln/detail/CVE-2024-36114) |
| CVE-2024-36114 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-36114](https://nvd.nist.gov/vuln/detail/CVE-2024-36114) |
| CVE-2024-47561 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-47561](https://nvd.nist.gov/vuln/detail/CVE-2024-47561) |
| CVE-2024-57699 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-57699](https://nvd.nist.gov/vuln/detail/CVE-2024-57699) |
| CVE-2024-7254 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-7254](https://nvd.nist.gov/vuln/detail/CVE-2024-7254) |
| CVE-2024-7254 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-7254](https://nvd.nist.gov/vuln/detail/CVE-2024-7254) |
| CVE-2024-7254 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-7254](https://nvd.nist.gov/vuln/detail/CVE-2024-7254) |
| CVE-2024-7254 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-7254](https://nvd.nist.gov/vuln/detail/CVE-2024-7254) |
| CVE-2024-7254 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-7254](https://nvd.nist.gov/vuln/detail/CVE-2024-7254) |
| CVE-2024-7254 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-7254](https://nvd.nist.gov/vuln/detail/CVE-2024-7254) |
| CVE-2025-1948 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-1948](https://nvd.nist.gov/vuln/detail/CVE-2025-1948) |
| CVE-2025-1948 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-1948](https://nvd.nist.gov/vuln/detail/CVE-2025-1948) |
| CVE-2025-24789 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-24789](https://nvd.nist.gov/vuln/detail/CVE-2025-24789) |
| CVE-2025-24970 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-24970](https://nvd.nist.gov/vuln/detail/CVE-2025-24970) |
| CVE-2025-24970 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-24970](https://nvd.nist.gov/vuln/detail/CVE-2025-24970) |
| CVE-2025-24970 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-24970](https://nvd.nist.gov/vuln/detail/CVE-2025-24970) |
| CVE-2025-27553 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-27553](https://nvd.nist.gov/vuln/detail/CVE-2025-27553) |
| CVE-2025-27820 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-27820](https://nvd.nist.gov/vuln/detail/CVE-2025-27820) |
| CVE-2025-27820 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-27820](https://nvd.nist.gov/vuln/detail/CVE-2025-27820) |
| CVE-2025-46762 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-46762](https://nvd.nist.gov/vuln/detail/CVE-2025-46762) |
| CVE-2012-5783 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2012-5783](https://nvd.nist.gov/vuln/detail/CVE-2012-5783) |
| CVE-2012-6153 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2012-6153](https://nvd.nist.gov/vuln/detail/CVE-2012-6153) |
| CVE-2018-10237 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2018-10237](https://nvd.nist.gov/vuln/detail/CVE-2018-10237) |
| CVE-2018-10237 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2018-10237](https://nvd.nist.gov/vuln/detail/CVE-2018-10237) |
| CVE-2018-10237 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2018-10237](https://nvd.nist.gov/vuln/detail/CVE-2018-10237) |
| CVE-2018-10237 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2018-10237](https://nvd.nist.gov/vuln/detail/CVE-2018-10237) |
| CVE-2018-10237 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2018-10237](https://nvd.nist.gov/vuln/detail/CVE-2018-10237) |
| CVE-2018-11798 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2018-11798](https://nvd.nist.gov/vuln/detail/CVE-2018-11798) |
| CVE-2018-1313 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2018-1313](https://nvd.nist.gov/vuln/detail/CVE-2018-1313) |
| CVE-2019-12384 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2019-12384](https://nvd.nist.gov/vuln/detail/CVE-2019-12384) |
| CVE-2019-12384 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2019-12384](https://nvd.nist.gov/vuln/detail/CVE-2019-12384) |
| CVE-2019-12814 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2019-12814](https://nvd.nist.gov/vuln/detail/CVE-2019-12814) |
| CVE-2019-12814 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2019-12814](https://nvd.nist.gov/vuln/detail/CVE-2019-12814) |
| CVE-2020-13955 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-13955](https://nvd.nist.gov/vuln/detail/CVE-2020-13955) |
| CVE-2020-13956 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-13956](https://nvd.nist.gov/vuln/detail/CVE-2020-13956) |
| CVE-2020-15250 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-15250](https://nvd.nist.gov/vuln/detail/CVE-2020-15250) |
| CVE-2020-15250 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-15250](https://nvd.nist.gov/vuln/detail/CVE-2020-15250) |
| CVE-2020-15522 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-15522](https://nvd.nist.gov/vuln/detail/CVE-2020-15522) |
| CVE-2020-15522 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-15522](https://nvd.nist.gov/vuln/detail/CVE-2020-15522) |
| CVE-2020-17521 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-17521](https://nvd.nist.gov/vuln/detail/CVE-2020-17521) |
| CVE-2020-17521 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-17521](https://nvd.nist.gov/vuln/detail/CVE-2020-17521) |
| CVE-2020-1945 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-1945](https://nvd.nist.gov/vuln/detail/CVE-2020-1945) |
| CVE-2020-26939 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-26939](https://nvd.nist.gov/vuln/detail/CVE-2020-26939) |
| CVE-2020-26939 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-26939](https://nvd.nist.gov/vuln/detail/CVE-2020-26939) |
| CVE-2021-22569 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2021-22569](https://nvd.nist.gov/vuln/detail/CVE-2021-22569) |
| CVE-2021-22569 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2021-22569](https://nvd.nist.gov/vuln/detail/CVE-2021-22569) |
| CVE-2021-22569 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2021-22569](https://nvd.nist.gov/vuln/detail/CVE-2021-22569) |
| CVE-2021-22570 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2021-22570](https://nvd.nist.gov/vuln/detail/CVE-2021-22570) |
| CVE-2021-22570 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2021-22570](https://nvd.nist.gov/vuln/detail/CVE-2021-22570) |
| CVE-2021-27568 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2021-27568](https://nvd.nist.gov/vuln/detail/CVE-2021-27568) |
| CVE-2021-28170 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2021-28170](https://nvd.nist.gov/vuln/detail/CVE-2021-28170) |
| CVE-2021-29425 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2021-29425](https://nvd.nist.gov/vuln/detail/CVE-2021-29425) |
| CVE-2021-36373 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2021-36373](https://nvd.nist.gov/vuln/detail/CVE-2021-36373) |
| CVE-2021-36374 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2021-36374](https://nvd.nist.gov/vuln/detail/CVE-2021-36374) |
| CVE-2022-38749 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2022-38749](https://nvd.nist.gov/vuln/detail/CVE-2022-38749) |
| CVE-2022-38750 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2022-38750](https://nvd.nist.gov/vuln/detail/CVE-2022-38750) |
| CVE-2022-38751 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2022-38751](https://nvd.nist.gov/vuln/detail/CVE-2022-38751) |
| CVE-2022-38752 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2022-38752](https://nvd.nist.gov/vuln/detail/CVE-2022-38752) |
| CVE-2022-41854 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2022-41854](https://nvd.nist.gov/vuln/detail/CVE-2022-41854) |
| CVE-2023-0833 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-0833](https://nvd.nist.gov/vuln/detail/CVE-2023-0833) |
| CVE-2023-33201 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-33201](https://nvd.nist.gov/vuln/detail/CVE-2023-33201) |
| CVE-2023-33201 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-33201](https://nvd.nist.gov/vuln/detail/CVE-2023-33201) |
| CVE-2023-33201 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-33201](https://nvd.nist.gov/vuln/detail/CVE-2023-33201) |
| CVE-2023-33202 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-33202](https://nvd.nist.gov/vuln/detail/CVE-2023-33202) |
| CVE-2023-33202 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-33202](https://nvd.nist.gov/vuln/detail/CVE-2023-33202) |
| CVE-2023-33202 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-33202](https://nvd.nist.gov/vuln/detail/CVE-2023-33202) |
| CVE-2023-42503 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-42503](https://nvd.nist.gov/vuln/detail/CVE-2023-42503) |
| CVE-2023-51074 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-51074](https://nvd.nist.gov/vuln/detail/CVE-2023-51074) |
| CVE-2024-12798 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-12798](https://nvd.nist.gov/vuln/detail/CVE-2024-12798) |
| CVE-2024-12798 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-12798](https://nvd.nist.gov/vuln/detail/CVE-2024-12798) |
| CVE-2024-12798 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-12798](https://nvd.nist.gov/vuln/detail/CVE-2024-12798) |
| CVE-2024-12798 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-12798](https://nvd.nist.gov/vuln/detail/CVE-2024-12798) |
| CVE-2024-12798 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-12798](https://nvd.nist.gov/vuln/detail/CVE-2024-12798) |
| CVE-2024-12798 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-12798](https://nvd.nist.gov/vuln/detail/CVE-2024-12798) |
| CVE-2024-12798 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-12798](https://nvd.nist.gov/vuln/detail/CVE-2024-12798) |
| CVE-2024-23944 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-23944](https://nvd.nist.gov/vuln/detail/CVE-2024-23944) |
| CVE-2024-23945 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-23945](https://nvd.nist.gov/vuln/detail/CVE-2024-23945) |
| CVE-2024-23945 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-23945](https://nvd.nist.gov/vuln/detail/CVE-2024-23945) |
| CVE-2024-23953 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-23953](https://nvd.nist.gov/vuln/detail/CVE-2024-23953) |
| CVE-2024-23953 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-23953](https://nvd.nist.gov/vuln/detail/CVE-2024-23953) |
| CVE-2024-25710 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-25710](https://nvd.nist.gov/vuln/detail/CVE-2024-25710) |
| CVE-2024-25710 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-25710](https://nvd.nist.gov/vuln/detail/CVE-2024-25710) |
| CVE-2024-26308 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-26308](https://nvd.nist.gov/vuln/detail/CVE-2024-26308) |
| CVE-2024-26308 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-26308](https://nvd.nist.gov/vuln/detail/CVE-2024-26308) |
| CVE-2024-29025 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-29025](https://nvd.nist.gov/vuln/detail/CVE-2024-29025) |
| CVE-2024-29133 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-29133](https://nvd.nist.gov/vuln/detail/CVE-2024-29133) |
| CVE-2024-29869 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-29869](https://nvd.nist.gov/vuln/detail/CVE-2024-29869) |
| CVE-2024-29869 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-29869](https://nvd.nist.gov/vuln/detail/CVE-2024-29869) |
| CVE-2024-30171 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-30171](https://nvd.nist.gov/vuln/detail/CVE-2024-30171) |
| CVE-2024-30171 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-30171](https://nvd.nist.gov/vuln/detail/CVE-2024-30171) |
| CVE-2024-30171 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-30171](https://nvd.nist.gov/vuln/detail/CVE-2024-30171) |
| CVE-2024-31141 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-31141](https://nvd.nist.gov/vuln/detail/CVE-2024-31141) |
| CVE-2024-43382 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-43382](https://nvd.nist.gov/vuln/detail/CVE-2024-43382) |
| CVE-2024-47535 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-47535](https://nvd.nist.gov/vuln/detail/CVE-2024-47535) |
| CVE-2024-47535 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-47535](https://nvd.nist.gov/vuln/detail/CVE-2024-47535) |
| CVE-2024-47535 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-47535](https://nvd.nist.gov/vuln/detail/CVE-2024-47535) |
| CVE-2024-47554 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-47554](https://nvd.nist.gov/vuln/detail/CVE-2024-47554) |
| CVE-2024-47554 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-47554](https://nvd.nist.gov/vuln/detail/CVE-2024-47554) |
| CVE-2024-47554 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-47554](https://nvd.nist.gov/vuln/detail/CVE-2024-47554) |
| CVE-2024-47554 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-47554](https://nvd.nist.gov/vuln/detail/CVE-2024-47554) |
| CVE-2024-52980 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-52980](https://nvd.nist.gov/vuln/detail/CVE-2024-52980) |
| CVE-2024-56128 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-56128](https://nvd.nist.gov/vuln/detail/CVE-2024-56128) |
| CVE-2024-6763 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-6763](https://nvd.nist.gov/vuln/detail/CVE-2024-6763) |
| CVE-2024-6763 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-6763](https://nvd.nist.gov/vuln/detail/CVE-2024-6763) |
| CVE-2024-6763 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-6763](https://nvd.nist.gov/vuln/detail/CVE-2024-6763) |
| CVE-2024-6763 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-6763](https://nvd.nist.gov/vuln/detail/CVE-2024-6763) |
| CVE-2024-6763 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-6763](https://nvd.nist.gov/vuln/detail/CVE-2024-6763) |
| CVE-2024-8184 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-8184](https://nvd.nist.gov/vuln/detail/CVE-2024-8184) |
| CVE-2024-9823 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-9823](https://nvd.nist.gov/vuln/detail/CVE-2024-9823) |
| CVE-2025-24790 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-24790](https://nvd.nist.gov/vuln/detail/CVE-2025-24790) |
| CVE-2025-25193 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-25193](https://nvd.nist.gov/vuln/detail/CVE-2025-25193) |
| CVE-2025-25193 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-25193](https://nvd.nist.gov/vuln/detail/CVE-2025-25193) |
| CVE-2025-25193 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-25193](https://nvd.nist.gov/vuln/detail/CVE-2025-25193) |
| CVE-2025-25193 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-25193](https://nvd.nist.gov/vuln/detail/CVE-2025-25193) |
| CVE-2025-30474 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-30474](https://nvd.nist.gov/vuln/detail/CVE-2025-30474) |
| CVE-2025-3588 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-3588](https://nvd.nist.gov/vuln/detail/CVE-2025-3588) |
| CVE-2025-46551 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2025-46551](https://nvd.nist.gov/vuln/detail/CVE-2025-46551) |
| CVE-2020-8908 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8908](https://nvd.nist.gov/vuln/detail/CVE-2020-8908) |
| CVE-2020-8908 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8908](https://nvd.nist.gov/vuln/detail/CVE-2020-8908) |
| CVE-2020-8908 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8908](https://nvd.nist.gov/vuln/detail/CVE-2020-8908) |
| CVE-2020-8908 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8908](https://nvd.nist.gov/vuln/detail/CVE-2020-8908) |
| CVE-2020-8908 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8908](https://nvd.nist.gov/vuln/detail/CVE-2020-8908) |
| CVE-2020-8908 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8908](https://nvd.nist.gov/vuln/detail/CVE-2020-8908) |
| CVE-2020-8908 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8908](https://nvd.nist.gov/vuln/detail/CVE-2020-8908) |
| CVE-2020-8908 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8908](https://nvd.nist.gov/vuln/detail/CVE-2020-8908) |
| CVE-2020-8908 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8908](https://nvd.nist.gov/vuln/detail/CVE-2020-8908) |
| CVE-2020-8908 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8908](https://nvd.nist.gov/vuln/detail/CVE-2020-8908) |
| CVE-2024-12801 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-12801](https://nvd.nist.gov/vuln/detail/CVE-2024-12801) |
| CVE-2024-12801 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-12801](https://nvd.nist.gov/vuln/detail/CVE-2024-12801) |
| CVE-2024-12801 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-12801](https://nvd.nist.gov/vuln/detail/CVE-2024-12801) |
| CVE-2024-12801 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-12801](https://nvd.nist.gov/vuln/detail/CVE-2024-12801) |
| CVE-2025-27496 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-27496](https://nvd.nist.gov/vuln/detail/CVE-2025-27496) |
| CVE-2025-46392 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-46392](https://nvd.nist.gov/vuln/detail/CVE-2025-46392) |
## 7.9.0 릴리스 정보
다음 릴리스 정보에는 Amazon EMR 릴리스 7.9.0에 대한 정보가 포함되어 있습니다.
**새로운 기능**
+ **애플리케이션 업그레이드** – Amazon EMR 7.9.0 application upgrades include AWS SDK for Java 2.31.16/1.12.782, Delta 3.3.0-amzn-1, Hadoop 3.4.1, Hudi 0.15.0-amzn-6, Iceberg 1.7.1-amzn-2, Spark 3.5.5, and Zookeeper 3.9.3.
+ **영구 앱 UI에 대한 CM-CMK 지원** - 이 기능은 고객 관리형 사용자 지정 마스터 키(CM-CMK)를 준수하기 위해 EMR 서비스 버킷에서 관리되는 로그에 적용되는 SSE 암호화를 확장합니다. 이 기능을 통해 고객은 클러스터 종료 후 로그의 접근성을 관리할 수 있습니다.
**알려진 문제**
+ EC2의 EMR에 대한 로깅 옵션을 비활성화하면 클러스터가 종료되고 영구 애플리케이션 UI가 포함되지 않은 후에는 로그를 사용할 수 없습니다.
+ **EMR-EC2 SecretAgent 구성 요소를 사용한 KMS 암호화** - EMR 버전 7.8 및 7.9에서 Lake Formation 지원 클러스터에 대해 저장된 KMS 암호화를 활성화할 때 발생하는 오류가 있습니다. Lake Formation 지원 작업이 경우 *NoSuchMethodError*가 발생하면서 실패합니다. 다음의 두 가지 해결 방법을 사용할 수 있습니다.
+ 영향을 받는 클러스터에 대해 미사용 시 KMS 암호화를 일시적으로 비활성화합니다.
+ KMS 암호화를 유지해야 하는 경우 AWS Support에 문의하여 부트스트랩 작업 아티팩트를 요청합니다.
**참고**
**영구 수정** - 2025년 8월에 위의 문제를 해결하기 위한 업데이트가 모든 리전에 배포되었습니다. 미사용 시 KMS 암호화를 비활성화할 필요가 없습니다.
+ **단계 로그 업로드 **- 일부 클러스터는 경합 조건으로 인해 단계 로그를 S3 버킷에 업로드하지 못할 수 있습니다. 이 문제가 발생하면 AWS 지원 팀에 문의하세요.
+ **Glue 카탈로그를 사용하여 HBase 테이블을 Hive에 생성** - EMR-7.3.0에서 EMR-7.10.0으로의 Hive Iceberg 통합으로 인해 버그가 발생하여 Glue Data Catalog를 메타스토어로 사용할 때 Hive에서 HBase 테이블 생성이 실패합니다. 이 문제가 발생하면 AWS 지원 팀에 문의하십시오.
+ **Tez UI** - EMR-7.3에서 EMR-7.10까지, 전송 중 암호화가 활성화된 경우 YARN Resource Manager Web UI를 통해 Tez UI에 액세스하지 못하는 버그가 있습니다. 이 문제는 Tez UI에 HTTPS가 필요한 동안 YARN 프록시가 HTTP 프로토콜을 사용하려고 시도하기 때문에 발생합니다. 이 문제를 해결하려면 `tez-site`의 `tez.tez-ui.history-url.base` 구성을 `http`에서 `https`로 수정하세요.
**변경 사항, 향상된 기능 및 해결된 문제**
+ Spark 3.3.1(EMR 버전 6.10 이상에서 지원됨)부터 폐기 호스트의 모든 실행기는 *DECOMMISSIONING* 상태라는 새로운 `ExecutorState` 상태로 설정됩니다. Yarn은 폐기 중인 실행기를 사용하여 작업을 할당할 수 없으므로 필요한 경우 실행 중인 작업에 대해 새 실행기를 요청하세요. 따라서 EMR Managed Scaling, EMR Auto Scaling 또는 EMR-EC2 클러스터의 사용자 지정 조정 메커니즘을 사용하는 동안 Spark DRA를 비활성화하면 Yarn이 각 작업에 허용되는 최대 실행기를 요청할 수 있습니다. 이 문제를 방지하려면 위의 기능 조합을 사용할 때 `spark.dynamicAllocation.enabled` 속성을 `TRUE`(기본값)로 설정한 상태로 둡니다. 또한 Spark 작업의 `spark.dynamicAllocation.maxExecutors` 및 `spark.dynamicAllocation.minExecutors` 속성 값을 설정하여 작업 실행 중에 할당된 실행기 수를 제한하여 최소 및 최대 실행기 제약 조건을 설정할 수도 있습니다.
+ *Oozie 사용 중단* - OSS Oozie가 Attic 모드로 전환되었으므로 Amazon EMR 릴리스 8.x 시리즈에서 Apache Oozie가 제거될 예정입니다. Oozie는 계속해서 7.x 시리즈의 일부로 포함됩니다. Oozie 대신 MWAA를 사용하는 것이 좋습니다. 고객은 GitHub의 유틸리티 [oozie-to-airflow-emr](https://github.com/dgghosalaws/oozie-to-airflow-emr)를 참조하여 기존 Oozie 워크플로를 MWAA로 마이그레이션할 수 있습니다.
+ *YARN 컨테이너 빈 패킹* - Amazon EMR 버전 7.9.0부터 YARN의 다중 노드 배치 정책을 기반으로 구축된 YARN 용량 스케줄러에 컨테이너 빈 패킹 정책을 사용할 수 있습니다.
+ *hudi-cli.sh* - EMR 릴리스 7.9.0 이상에서는 **hudi-cli.sh** 스크립트가 더 이상 사용되지 않습니다. Amazon EMR 릴리스 7.9.0 이상에서는 **hudi-cli-bundle.jar**을 사용합니다.
+ *FIPS 지원 AL2023 AMI의 EMR 클러스터* - EMR 7.9부터 고객은 [FIPS 지원 AL2023 AMI](https://docs.aws.amazon.com/linux/al2023/ug/fips-mode.html)에서 EMR 클러스터를 시작할 수 있습니다. 이 변경 사항은 EMR의 디지털 서명 및 해시 알고리즘을 업데이트하여 모든 EMR 패키지가 FIPS 140-3에 대한 권장 암호화 정책을 준수하도록 합니다. 참고: EMR 또는 AL2023의 FIPS 인증 상태는 여기에 포함되지 않습니다. FIPS 140-3 검증 상태에 대한 최신 정보는 [AL2023 FIPS FAQ](https://aws.amazon.com/linux/amazon-linux-2023/faqs/)를 참조하세요.
+ *단계 지연 시간* - 이 릴리스에서는 설치를 위해 Hadoop 애플리케이션을 명시적으로 선택하지 않고 전송 중 데이터 암호화를 사용할 때 단계 지연 시간이 증가하는 문제를 해결합니다.
+ *EBS 암호화 볼륨을 사용한 클러스터 시작* - 이 릴리스에서는 EBS 암호화 볼륨에 대한 KMS 호출로 인해 EMR 클러스터 시작이 실패할 수 있는 문제를 해결합니다.
+
[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/ko_kr/emr/latest/ReleaseGuide/emr-790-release.html)
## 7.9.0 기본 Java 버전
Amazon EMR 릴리스 7.9 이상은 Apache Livy를 제외하고 Corretto 17(OpenJDK)을 지원하는 애플리케이션에 기본적으로 Amazon Corretto 17(OpenJDK 기반)과 함께 제공됩니다.
다음 표에는 Amazon EMR 7.9.0의 애플리케이션에 대한 기본 Java 버전이 나와 있습니다. 클러스터의 기본 JVM을 변경하려면 클러스터에서 실행되는 각 애플리케이션에 대해 [특정 Java 가상 머신을 사용하도록 애플리케이션 구성](configuring-java8.md)의 지침을 따릅니다. 클러스터에서는 Java 런타임 버전 1개만 사용할 수 있습니다. Amazon EMR은 동일한 클러스터에서 다양한 런타임 버전을 사용해 서로 다른 노드 또는 애플리케이션을 실행하는 것을 지원하지 않습니다.
| 애플리케이션 | Java 및 Amazon Corretto 버전(기본값은 굵은체로 표시) |
| --- | --- |
| 델타 | 17, 11, 8 |
| Flink | 17, 11, 8 |
| HBase | 17, 11, 8 |
| HCatalog | 17, 11, 8 |
| Hadoop | 17, 11, 8 |
| Hive | 17, 11, 8 |
| Hudi | 17, 11, 8 |
| Iceberg | 17, 11 |
| Livy | 17, 11, 8 |
| Oozie | 17, 11, 8 |
| 피닉스 | 17, 11, 8 |
| PrestoDB | 8 |
| Spark | 17, 11, 8 |
| Spark RAPIDS | 17, 11, 8 |
| Tez의 Hive 실행 시간 비교 | 17, 11, 8 |
| Trino | 21, 17 |
| Zeppelin | 17, 11, 8 |
| Pig | 17, 11, 8 |
| Zookeeper | 17, 11, 8 |
## 7.9.0 구성 요소 버전
이 릴리스를 통해 Amazon EMR이 설치하는 구성 요소는 다음과 같습니다. 일부는 빅 데이터 애플리케이션 패키지의 일부로 설치됩니다. 나머지는 Amazon EMR에 고유하며 시스템 프로세스 및 기능을 위해 설치됩니다. 이는 일반적으로 `emr` 또는 `aws`로 시작됩니다. 최근 Amazon EMR 릴리스의 빅 데이터 애플리케이션 패키지는 일반적으로 커뮤니티에서 발견된 최신 버전입니다. 가능한 한 빨리 Amazon EMR에서 커뮤니티 릴리스를 제공합니다.
Amazon EMR의 일부 구성 요소는 커뮤니티 버전과 다릅니다. 이러한 구성 요소에는 `CommunityVersion-amzn-EmrVersion` 양식의 버전 레이블이 있습니다. `EmrVersion`은 0에서 시작합니다. 예를 들어, 버전 2.2의 `myapp-component`라는 오픈 소스 커뮤니티 구성 요소가 다른 Amazon EMR 릴리스에 포함되도록 세 번 수정된 경우 해당 릴리스 버전은 `2.2-amzn-2`로 나열됩니다.
| 구성 요소 | 버전 | 설명 |
| --- | --- | --- |
| adot-java-agent | 1.31.0 | 애플리케이션 대몬(daemon)에서 지표를 수집하는 Java 에이전트입니다. |
| delta | 3.3.0-amzn-1 | Delta Lake는 방대한 분석 데이터 세트를 위한 오픈 테이블 형식입니다. |
| emr-amazon-cloudwatch-agent | 1.300032.2-amzn-0 | Amazon EC2 인스턴스에서 내부 시스템 수준 지표와 사용자 지정 애플리케이션 지표를 수집하는 애플리케이션입니다. |
| emr-ddb | 5.7.0 | 하둡 에코시스템 애플리케이션용 Amazon DynamoDB 커넥터 |
| emr-goodies | 3.18.0 | 편리한 하둡 에코시스템용 추가 라이브러리 |
| emr-kinesis | 3.22.0 | 하둡 에코시스템 애플리케이션용 Amazon Kinesis 커넥터. |
| emr-notebook-env | 1.18.0 | Jupyter Enterprise Gateway가 포함된 EMR 노트북용 Conda 환경 |
| emr-s3-dist-cp | 2.39.0 | Amazon S3용으로 최적화된 분사 복사 애플리케이션. |
| emr-s3-select | 2.18.0 | EMR S3Select 커넥터 |
| emr-wal-cli | 1.3.4 | emrwal 목록/삭제에 사용되는 CLI입니다. |
| emrfs | 2.70.0 | 하둡 에코시스템 애플리케이션용 Amazon S3 커넥터. |
| flink-client | 1.20.0-amzn-3 | Apache Flink 명령줄 클라이언트 스크립트 및 애플리케이션 |
| flink-jobmanager-config | 1.20.0-amzn-3 | Apache Flink JobManager에 대한 EMR 노드에서 리소스를 관리합니다. |
| hadoop-client | 3.4.1-amzn-1 | 'hdfs', 'hadoop', 'yarn' 등과 같은 하둡 명령줄 클라이언트 |
| hadoop-hdfs-datanode | 3.4.1-amzn-1 | 블록을 저장하는 HDFS 노드 수준 서비스 |
| hadoop-hdfs-library | 3.4.1-amzn-1 | HDFS 명령줄 클라이언트 및 라이브러리 |
| hadoop-hdfs-namenode | 3.4.1-amzn-1 | 파일 이름 및 블록 위치를 추적하는 HDFS 서비스 |
| hadoop-hdfs-journalnode | 3.4.1-amzn-1 | HA 클러스터에서 하둡 파일 시스템 저널을 관리하기 위한 HDFS 서비스 |
| hadoop-httpfs-server | 3.4.1-amzn-1 | HDFS 작업에 대한 HTTP 엔드포인트 |
| hadoop-kms-server | 3.4.1-amzn-1 | 하둡의 KeyProvider API를 기반으로 하는 암호화 키 관리 서버 |
| hadoop-mapred | 3.4.1-amzn-1 | MapReduce 애플리케이션을 실행하는 MapReduce 실행 엔진 라이브러리 |
| hadoop-yarn-nodemanager | 3.4.1-amzn-1 | 개별 노드의 컨테이너를 관리하는 YARN 서비스 |
| hadoop-yarn-resourcemanager | 3.4.1-amzn-1 | 클러스터 리소스 및 분산 애플리케이션을 할당 및 관리하는 YARN 서비스 |
| hadoop-yarn-timeline-server | 3.4.1-amzn-1 | YARN 애플리케이션의 현재 및 기록 정보를 가져오는 서비스 |
| hbase-hmaster | 2.6.2-amzn-0 | 리전 조정 및 관리 명령의 실행을 담당하는 HBase 클러스터용 서비스 |
| hbase-region-server | 2.6.2-amzn-0 | 한 개 이상의 HBase 리전에 서비스를 제공하는 서비스 |
| hbase-client | 2.6.2-amzn-0 | HBase 명령줄 클라이언트 |
| hbase-rest-server | 2.6.2-amzn-0 | HBase용 RESTful HTTP 엔드포인트를 제공하는 서비스 |
| hbase-thrift-server | 2.6.2-amzn-0 | HBase에 Thrift 엔드포인트를 제공하는 서비스 |
| hbase-operator-tools | 2.6.2-amzn-0 | Apache HBase 클러스터용 복구 도구. |
| hcatalog-client | 3.1.3-amzn-18 | hcatalog-server를 조정하기 위한 'hcat' 명령줄 클라이언트 |
| hcatalog-server | 3.1.3-amzn-18 | 분산 애플리케이션용 스토리지 관리 계층, 테이블 및 HCatalog를 제공하는 서비스 |
| hcatalog-webhcat-server | 3.1.3-amzn-18 | HCatalog에 REST 인터페이스를 제공하는 HTTP 엔드포인트 |
| hive-client | 3.1.3-amzn-18 | Hive 명령줄 클라이언트 |
| hive-hbase | 3.1.3-amzn-18 | Hive-hbase 클라이언트 |
| hive-metastore-server | 3.1.3-amzn-18 | 하둡 작업에 대한 SQL용 메타데이터가 저장되는 시맨틱 리포지토리인 Hive 메타스토어에 액세스하기 위한 서비스 |
| hive-server2 | 3.1.3-amzn-18 | Hive 쿼리를 웹 요청으로 수락하기 위한 서비스 |
| hudi | 0.15.0-amzn-6 | 짧은 지연 시간 및 높은 효율성으로 데이터 파이프라인을 구동하는 증분 처리 프레임워크. |
| hudi-presto | 0.15.0-amzn-6 | Hudi로 Presto를 실행하기 위한 번들 라이브러리. |
| hudi-trino | 0.15.0-amzn-6 | Hudi와 함께 Trnio를 실행하기 위한 번들 라이브러리. |
| hudi-spark | 0.15.0-amzn-6 | Hudi와 함께 Spark를 실행하기 위한 번들 라이브러리. |
| hue-server | 4.11.0 | 하둡 에코시스템 애플리케이션을 사용하여 데이터를 분석하는 웹 애플리케이션. |
| iceberg | 1.7.1-amzn-2 | Apache Iceberg는 방대한 분석 데이터 세트를 위한 오픈 테이블 형식입니다. |
| jupyterhub | 1.5.0 | Jupyter Notebook용 다중 사용자 서버 |
| livy-server | 0.8.0-incubating | Apache Spark와 상호작용하기 위한 REST 인터페이스 |
| nginx | 1.12.1 | HTTP인 nginx [engine x] 및 역방향 프록시 서버 |
| mariadb-server | 5.5.68 이상 | MariaDB 데이터베이스 서버. |
| nvidia-cuda | 12.3.0 | Nvidia 드라이버와 Cuda 도구 키트 |
| oozie-client | 5.2.1 | Oozie 명령줄 클라이언트 |
| oozie-server | 5.2.1 | Oozie 워크플로 요청을 수락하는 서비스 |
| opencv | 4.7.0 | 오픈 소스 컴퓨터 비전 라이브러리. |
| phoenix-library | 5.2.1 | 서버 및 클라이언트의 phoenix 라이브러리 |
| phoenix-connectors | 6.0.0 | Spark-3용 Apache Phoenix 커넥터 |
| phoenix-query-server | 6.0.0 | Avatica API에 대한 JSON 형식 액세스 및 프로토콜 버퍼 액세스를 비롯하여 JDBC 액세스를 제공하는 경량 서버 |
| presto-coordinator | 0.287-amzn-3 | presto-worker의 쿼리를 수락하고 쿼리 실행을 관리하는 서비스. |
| presto-worker | 0.287-amzn-3 | 여러 쿼리를 실행하는 서비스. |
| presto-client | 0.287-amzn-3 | Presto 서버가 시작되지 않은 HA 클러스터의 대기 마스터에 설치된 Presto 명령줄 클라이언트. |
| trino-coordinator | 467-amzn-2 | trino-workers의 쿼리를 수락하고 쿼리 실행을 관리하는 서비스. |
| trino-worker | 467-amzn-2 | 여러 쿼리를 실행하는 서비스. |
| trino-client | 467-amzn-2 | Trino 서버가 시작되지 않은 HA 클러스터의 대기 마스터에 설치된 Trino 명령줄 클라이언트. |
| pig-client | 0.17.0 | Pig 명령줄 클라이언트. |
| r | 4.3.2 | 통계 컴퓨팅용 R 프로젝트 |
| ranger-kms-server | 2.0.0 | Apache Ranger 키 관리 시스템 |
| spark-client | 3.5.5-amzn-0 | Spark 명령줄 클라이언트. |
| spark-history-server | 3.5.5-amzn-0 | 완료된 Spark 애플리케이션의 수명에 대해 기록된 이벤트를 조회하는 웹 UI. |
| spark-on-yarn | 3.5.5-amzn-0 | YARN용 인 메모리 실행 엔진. |
| spark-yarn-slave | 3.5.5-amzn-0 | YARN 슬레이브에서 필요한 Apache Spark 라이브러리. |
| spark-rapids | 25.02.1-amzn-0 | GPU로 Apache Spark를 가속화하는 Nvidia Spark RAPIDS 플러그인. |
| tensorflow | 2.16.1 | TensorFlow는 고성능 수치 계산용 오픈 소스 소프트웨어 라이브러리입니다. |
| tez-on-yarn | 0.10.2-amzn-16 | tez YARN 애플리케이션 및 라이브러리. |
| tez-on-worker | 0.10.2-amzn-16 | 워커 노드에 대한 tez YARN 애플리케이션 및 라이브러리. |
| zeppelin-server | 0.11.1 | 대화형 데이터 분석이 가능한 웹 기반 노트북 |
| zookeeper-server | 3.9.3-amzn-1 | 구성 정보 유지 관리, 이름 지정, 분산 동기화 제공 및 그룹 서비스 제공을 위한 중앙 집중식 서비스. |
| zookeeper-client | 3.9.3-amzn-1 | ZooKeeper 명령줄 클라이언트. |
## 7.9.0 구성 분류
구성 분류를 사용하면 애플리케이션을 사용자 지정할 수 있습니다. 이는 종종 `hive-site.xml`과 같이 애플리케이션의 구성 XML 파일에 해당합니다. 자세한 내용은 [애플리케이션 구성](emr-configure-apps.md) 단원을 참조하십시오.
재구성 작업은 실행 중인 클러스터의 인스턴스 그룹에 대한 구성을 지정할 때 수행됩니다. Amazon EMR은 사용자가 수정한 분류에 대한 재구성 작업만 시작합니다. 자세한 내용은 [실행 중인 클러스터에서 인스턴스 그룹 재구성](emr-configure-apps-running-cluster.md) 단원을 참조하십시오.
**emr-7.9.0 분류**
| 분류 | 설명 | 재구성 작업 |
| --- | --- | --- |
| capacity-scheduler | Hadoop capacity-scheduler.xml 파일에서 값을 변경합니다. | Restarts the ResourceManager service. |
| container-executor | Hadoop YARN container-executor.cfg 파일에서 값을 변경합니다. | Not available. |
| container-log4j | Hadoop YARN container-log4j.properties 파일에서 값을 변경합니다. | Not available. |
| core-site | Hadoop core-site.xml 파일에서 값을 변경합니다. | Restarts the Hadoop HDFS services Namenode, SecondaryNamenode, Datanode, ZKFC, and Journalnode. Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts Hadoop KMS, Ranger KMS, HiveServer2, Hive MetaStore, Hadoop Httpfs, and MapReduce-HistoryServer. |
| docker-conf | Docker 관련 설정을 변경합니다. | Not available. |
| emrfs-site | EMRFS 설정을 변경합니다. | Restarts the Hadoop HDFS services Namenode, SecondaryNamenode, Datanode, ZKFC, and Journalnode. Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts HBaseRegionserver, HBaseMaster, HBaseThrift, HBaseRest, HiveServer2, Hive MetaStore, Hadoop Httpfs, and MapReduce-HistoryServer. |
| flink-conf | flink-conf.yaml 설정을 변경합니다. | Restarts Flink history server. |
| flink-log4j | Flink log4j.properties 설정을 변경합니다. | Restarts Flink history server. |
| flink-log4j-session | Kubernetes 및 Yarn 세션에 대한 Flink log4j-session.properties 설정을 변경합니다. | Restarts Flink history server. |
| flink-log4j-cli | Flink log4j-cli.properties 설정을 변경합니다. | Restarts Flink history server. |
| hadoop-env | 모든 Hadoop 구성 요소에 대한 Hadoop 환경에서 값을 변경합니다. | Restarts the Hadoop HDFS services Namenode, SecondaryNamenode, Datanode, ZKFC, and Journalnode. Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts PhoenixQueryserver, HiveServer2, Hive MetaStore, and MapReduce-HistoryServer. |
| hadoop-log4j | Hadoop log4j.properties 파일에서 값을 변경합니다. | Restarts the Hadoop HDFS services SecondaryNamenode, Datanode, and Journalnode. Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts Hadoop KMS, Hadoop Httpfs, and MapReduce-HistoryServer. |
| hadoop-ssl-server | hadoop ssl 서버 구성을 변경합니다. | Not available. |
| hadoop-ssl-client | hadoop ssl 클라이언트 구성을 변경합니다. | Not available. |
| hbase | Apache HBase에 대한 Amazon EMR 큐레이트 설정입니다. | Custom EMR specific property. Sets emrfs-site and hbase-site configs. See those for their associated restarts. |
| hbase-env | HBase 환경에서 값을 변경합니다. | Restarts the HBase services RegionServer, HBaseMaster, ThriftServer, RestServer. |
| hbase-log4j2 | HBase hbase-log4j.properties 파일에서 값을 변경합니다. | Restarts the HBase services RegionServer, HBaseMaster, ThriftServer, RestServer. |
| hbase-metrics | HBase hadoop-metrics2-hbase.properties 파일에서 값을 변경합니다. | Restarts the HBase services RegionServer, HBaseMaster, ThriftServer, RestServer. |
| hbase-policy | HBase hbase-policy.xml 파일에서 값을 변경합니다. | Not available. |
| hbase-site | HBase hbase-site.xml 파일에서 값을 변경합니다. | Restarts the HBase services RegionServer, HBaseMaster, ThriftServer, RestServer. Additionally restarts Phoenix QueryServer. |
| hdfs-encryption-zones | HDFS 암호화 영역을 구성합니다. | This classification should not be reconfigured. |
| hdfs-env | HDFS 환경에서 값을 변경합니다. | Restarts Hadoop HDFS services Namenode, Datanode, and ZKFC. |
| hdfs-site | HDFS hdfs-site.xml에서 값을 변경합니다. | Restarts the Hadoop HDFS services Namenode, SecondaryNamenode, Datanode, ZKFC, and Journalnode. Additionally restarts Hadoop Httpfs. |
| hcatalog-env | HCatalog 환경에서 값을 변경합니다. | Restarts Hive HCatalog Server. |
| hcatalog-server-jndi | HCatalog jndi.properties 환경에서 값을 변경합니다. | Restarts Hive HCatalog Server. |
| hcatalog-server-proto-hive-site | HCatalog proto-hive-site.xml에서 값을 변경합니다. | Restarts Hive HCatalog Server. |
| hcatalog-webhcat-env | HCatalog WebHCat 환경에서 값을 변경합니다. | Restarts Hive WebHCat server. |
| hcatalog-webhcat-log4j2 | HCatalog WebHCat log4j2.properties에서 값을 변경합니다. | Restarts Hive WebHCat server. |
| hcatalog-webhcat-site | HCatalog WebHCat webhcat-site.xml 파일에서 값을 변경합니다. | Restarts Hive WebHCat server. |
| hive | Apache Hive에 대한 Amazon EMR 큐레이트 설정입니다. | Sets configurations to launch Hive LLAP service. |
| hive-beeline-log4j2 | Hive beeline-log4j2.properties 파일에서 값을 변경합니다. | Not available. |
| hive-parquet-logging | Hive parquet-logging.properties 파일에서 값을 변경합니다. | Not available. |
| hive-env | Hive 환경에서 값을 변경합니다. | Restarts HiveServer2, HiveMetastore, and Hive HCatalog-Server. Runs Hive schemaTool CLI commands to verify hive-metastore. |
| hive-exec-log4j2 | Hive hive-exec-log4j2.properties 파일에서 값을 변경합니다. | Not available. |
| hive-llap-daemon-log4j2 | Hive llap-daemon-log4j2.properties 파일에서 값을 변경합니다. | Not available. |
| hive-log4j2 | Hive hive-log4j2.properties 파일에서 값을 변경합니다. | Not available. |
| hive-site | Hive hive-site.xml 파일에서 값을 변경합니다. | Restarts HiveServer2, HiveMetastore, and Hive HCatalog-Server. Runs Hive schemaTool CLI commands to verify hive-metastore. Also restarts Oozie and Zeppelin. |
| hiveserver2-site | Hive Server2 hiveserver2-site.xml 파일에서 값을 변경합니다. | Not available. |
| hue-ini | Hue ini 파일에서 값을 변경합니다. | Restarts Hue. Also activates Hue config override CLI commands to pick up new configurations. |
| httpfs-env | HTTPFS 환경에서 값을 변경합니다. | Restarts Hadoop Httpfs service. |
| httpfs-site | Hadoop httpfs-site.xml 파일에서 값을 변경합니다. | Restarts Hadoop Httpfs service. |
| hadoop-kms-acls | Hadoop kms-acls.xml 파일에서 값을 변경합니다. | Not available. |
| hadoop-kms-env | Hadoop KMS 환경에서 값을 변경합니다. | Restarts Hadoop-KMS service. |
| hadoop-kms-java-home | Hadoop의 KMS java 홈 변경 | Not available. |
| hadoop-kms-log4j | Hadoop kms-log4j.properties 파일에서 값을 변경합니다. | Not available. |
| hadoop-kms-site | Hadoop kms-site.xml 파일에서 값을 변경합니다. | Restarts Hadoop-KMS and Ranger-KMS service. |
| hudi-env | Hudi 환경에서 값을 변경합니다. | Not available. |
| hudi-defaults | Hudi hudi-defaults.conf 파일에서 값을 변경합니다. | Not available. |
| iceberg-defaults | Iceberg iceberg-defaults.conf 파일에서 값을 변경합니다. | Not available. |
| delta-defaults | Delta delta-defaults.conf 파일에서 값을 변경합니다. | Not available. |
| jupyter-notebook-conf | Jupyter Notebook jupyter\$1notebook\$1config.py 파일에서 값을 변경합니다. | Not available. |
| jupyter-hub-conf | JupyterHubs jupyterhub\$1config.py 파일에서 값을 변경합니다. | Not available. |
| jupyter-s3-conf | Jupyter Notebook S3 지속성 구성 | Not available. |
| jupyter-sparkmagic-conf | Sparkmagic config.json 파일에서 값을 변경합니다. | Not available. |
| livy-conf | Livy livy.conf 파일에서 값을 변경합니다. | Restarts Livy Server. |
| livy-env | Livy 환경에서 값을 변경합니다. | Restarts Livy Server. |
| livy-log4j2 | Livy log4j2.properties 설정을 변경합니다. | Restarts Livy Server. |
| mapred-env | MapReduce 애플리케이션 환경에서 값을 변경합니다. | Restarts Hadoop MapReduce-HistoryServer. |
| mapred-site | MapReduce 애플리케이션 mapred-site.xml 파일에서 값을 변경합니다. | Restarts Hadoop MapReduce-HistoryServer. |
| oozie-env | Oozie 환경에서 값을 변경합니다. | Restarts Oozie. |
| oozie-log4j | Oozie oozie-log4j.properties 파일에서 값을 변경합니다. | Restarts Oozie. |
| oozie-site | Oozie oozie-site.xml 파일에서 값을 변경합니다. | Restarts Oozie. |
| phoenix-hbase-metrics | Phoenix hadoop-metrics2-hbase.properties 파일에서 값을 변경합니다. | Not available. |
| phoenix-hbase-site | Phoenix hbase-site.xml 파일에서 값을 변경합니다. | Not available. |
| phoenix-log4j2 | Phoenix log4j2.properties 파일에서 값을 변경합니다. | Restarts Phoenix-QueryServer. |
| phoenix-metrics | Phoenix hadoop-metrics2-phoenix.properties 파일에서 값을 변경합니다. | Not available. |
| pig-env | Pig 환경에서 값을 변경합니다. | Not available. |
| pig-properties | Pig pig.properties 파일에서 값을 변경합니다. | Restarts Oozie. |
| pig-log4j | Pig log4j.properties 파일에서 값을 변경합니다. | Not available. |
| presto-log | Presto log.properties 파일에서 값을 변경합니다. | Restarts Presto-Server (for PrestoDB) |
| presto-config | Presto config.properties 파일에서 값을 변경합니다. | Restarts Presto-Server (for PrestoDB) |
| presto-password-authenticator | Presto password-authenticator.properties 파일에서 값을 변경합니다. | Not available. |
| presto-env | Presto presto-env.sh 파일에서 값을 변경합니다. | Restarts Presto-Server (for PrestoDB) |
| presto-node | Presto node.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-blackhole | Presto blackhole.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-cassandra | Presto cassandra.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-hive | Presto hive.properties 파일에서 값을 변경합니다. | Restarts Presto-Server (for PrestoDB) |
| presto-connector-jmx | Presto jmx.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-kafka | Presto kafka.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-lakeformation | Presto lakeformation.properties 파일에서 값을 변경합니다. | Restarts Presto-Server (for PrestoDB) |
| presto-connector-localfile | Presto localfile.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-memory | Presto memory.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-mongodb | Presto mongodb.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-mysql | Presto mysql.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-postgresql | Presto postgresql.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-raptor | Presto raptor.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-redis | Presto redis.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-redshift | Presto redshift.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-tpch | Presto tpch.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-tpcds | Presto tpcds.properties 파일에서 값을 변경합니다. | Not available. |
| trino-log | Trino log.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-config | Trino config.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-password-authenticator | Trino password-authenticator.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-env | Trino trino-env.sh 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-node | Trino node.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-blackhole | Trino blackhole.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-cassandra | Trino cassandra.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-delta | Trino delta.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-connector-hive | Trino hive.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-exchange-manager | Trino exchange-manager.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-connector-iceberg | Trino iceberg.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-connector-hudi | Trino hudi.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-connector-jmx | Trino jmx.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-kafka | Trino kafka.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-localfile | Trino localfile.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-memory | Trino memory.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-mongodb | Trino mongodb.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-mysql | Trino mysql.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-postgresql | Trino postgresql.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-raptor | Trino raptor.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-redis | Trino redis.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-redshift | Trino redshift.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-tpch | Trino tpch.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-tpcds | Trino tpcds.properties 파일에서 값을 변경합니다. | Not available. |
| ranger-kms-dbks-site | Ranger KMS dbks-site.xml 파일에서 값을 변경합니다. | Restarts Ranger KMS Server. |
| ranger-kms-site | Ranger KMS ranger-kms-site.xml 파일에서 값을 변경합니다. | Restarts Ranger KMS Server. |
| ranger-kms-env | Ranger KMS 환경에서 값을 변경합니다. | Restarts Ranger KMS Server. |
| ranger-kms-logback | Ranger KMS kms-logback.xml 파일에서 값을 변경합니다. | Not available. |
| ranger-kms-db-ca | Ranger KMS와의 MySQL SSL 연결에서 CA 파일의 값을 변경합니다. | Not available. |
| spark | Apache Spark에 대한 Amazon EMR 큐레이트 설정입니다. | This property modifies spark-defaults. See actions there. |
| spark-defaults | Spark spark-defaults.conf 파일에서 값을 변경합니다. | Restarts Spark history server and Spark thrift server. |
| spark-env | Spark 환경에서 값을 변경합니다. | Restarts Spark history server and Spark thrift server. |
| spark-hive-site | Spark hive-site.xml 파일에서 값을 변경합니다. | Not available. |
| spark-log4j2 | Spark log4j2.properties 파일에서 값을 변경합니다. | Restarts Spark history server and Spark thrift server. |
| spark-metrics | Spark metrics.properties 파일에서 값을 변경합니다. | Restarts Spark history server and Spark thrift server. |
| tez-site | Tez tez-site.xml 파일에서 값을 변경합니다. | Restart Oozie and HiveServer2. |
| yarn-env | YARN 환경에서 값을 변경합니다. | Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts MapReduce-HistoryServer. |
| yarn-site | YARN yarn-site.xml 파일에서 값을 변경합니다. | Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts Livy Server and MapReduce-HistoryServer. |
| zeppelin-env | Zeppelin 환경에서 값을 변경합니다. | Restarts Zeppelin. |
| zeppelin-site | zeppelin-site.xml에서 구성 설정을 변경합니다. | Restarts Zeppelin. |
| zookeeper-config | ZooKeeper zoo.cfg 파일에서 값을 변경합니다. | Restarts Zookeeper server. |
| zookeeper-logback | ZooKeeper logback.xml 파일에서 값을 변경합니다. | Restarts Zookeeper server. |
| emr-metrics | 이 노드에 대한 emr 지표 설정을 변경합니다. | Restarts the CloudWatchAgent service. |
## 7.9.0 변경 로그
**7.9.0 릴리스 및 릴리스 정보에 대한 변경 로그**
| Date | 이벤트 | 설명 |
| --- | --- | --- |
| 2025-05-19 | 문서 게시 | Amazon EMR 7.9.0 릴리스 정보가 처음 게시됨 |
| 2025-05-19 | 배포 완료 | [지원되는 모든 리전](https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/)에 Amazon EMR 7.9.0 완전 배포 |
| 2025-05-19 | 초기 제한 릴리스 | Amazon EMR 7.9.0이 초기 상용 리전에 처음 배포됨 |
# Amazon EMR 릴리스 7.8.0
## 7.8.0 지원 수명 주기
다음 표에서는 Amazon EMR 릴리스 7.8.0에 지원되는 수명 주기 날짜를 설명합니다.
| 지원 단계 | Date |
| --- | --- |
| 초기 릴리스 날짜 | 2025년 3월 7일 |
| 표준 지원 종료 시점 | 2027년 3월 6일 |
| 지원 종료 | 2027년 3월 7일 |
| 수명 종료 | 2028년 3월 7일 |
## 7.8.0 애플리케이션 버전
이 릴리스에 포함된 애플리케이션은 [https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Install-CloudWatch-Agent.html](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Install-CloudWatch-Agent.html), [https://delta.io/](https://delta.io/), [https://flink.apache.org/](https://flink.apache.org/), [http://hbase.apache.org/](http://hbase.apache.org/), [https://cwiki.apache.org/confluence/display/Hive/HCatalog](https://cwiki.apache.org/confluence/display/Hive/HCatalog), [http://hadoop.apache.org/docs/current/](http://hadoop.apache.org/docs/current/), [http://hive.apache.org/](http://hive.apache.org/), [https://hudi.apache.org](https://hudi.apache.org), [http://gethue.com/](http://gethue.com/), [https://iceberg.apache.org/](https://iceberg.apache.org/), [https://jupyter-enterprise-gateway.readthedocs.io/en/latest/](https://jupyter-enterprise-gateway.readthedocs.io/en/latest/), [https://jupyterhub.readthedocs.io/en/latest/#](https://jupyterhub.readthedocs.io/en/latest/#), [https://livy.incubator.apache.org/](https://livy.incubator.apache.org/), [http://oozie.apache.org/](http://oozie.apache.org/), [https://phoenix.apache.org/](https://phoenix.apache.org/), [http://pig.apache.org/](http://pig.apache.org/), [https://prestodb.io/](https://prestodb.io/), [https://spark.apache.org/docs/latest/](https://spark.apache.org/docs/latest/), [https://www.tensorflow.org/](https://www.tensorflow.org/), [https://tez.apache.org/](https://tez.apache.org/), [https://trino.io/](https://trino.io/), [https://zeppelin.incubator.apache.org/](https://zeppelin.incubator.apache.org/), [https://zookeeper.apache.org](https://zookeeper.apache.org)입니다.
아래 테이블에는 이번 Amazon EMR 릴리스에서 사용할 수 있는 애플리케이션 버전과 이전 세 가지 Amazon EMR 릴리스(해당하는 경우)의 애플리케이션 버전이 나와 있습니다.
각 Amazon EMR 릴리스에서 애플리케이션 버전의 전체 기록은 다음 주제를 참조하세요.
+ [Amazon EMR 7.x 릴리스의 애플리케이션 버전](emr-release-app-versions-7.x.md)
+ [Amazon EMR 6.x 릴리스의 애플리케이션 버전](emr-release-app-versions-6.x.md)
+ [Amazon EMR 5.x 릴리스의 애플리케이션 버전](emr-release-app-versions-5.x.md)
+ [Amazon EMR 4.x 릴리스의 애플리케이션 버전](emr-release-app-versions-4.x.md)
**애플리케이션 버전 정보**
| | emr-7.8.0 | emr-7.7.0 | emr-7.6.0 | emr-7.5.0 |
| --- | --- | --- | --- | --- |
| AWS Java용 SDK | 2.29.52, 1.12.780 | 2.29.44, 1.12.780 | 2.29.25, 1.12.779 | 2.28.8, 1.12.772 |
| Python | 3.9, 3.11 | 3.9, 3.11 | 3.9, 3.11 | 3.9, 3.11 |
| Scala | 2.12.18 | 2.12.18 | 2.12.18 | 2.12.18 |
| AmazonCloudWatchAgent | 1.300032.2-amzn-0 | 1.300032.2-amzn-0 | 1.300032.2-amzn-0 | 1.300032.2-amzn-0 |
| Delta | 3.3.0-amzn-0 | 3.2.1-amzn-2 | 3.2.1-amzn-1 | 3.2.1-amzn-0 |
| Flink | 1.20.0-amzn-2 | 1.20.0-amzn-1 | 1.20.0-amzn-0 | 1.19.1-amzn-1 |
| Ganglia | - | - | - | - |
| HBase | 2.6.1-amzn-2 | 2.6.1-amzn-1 | 2.6.1-amzn-0 | 2.5.10-amzn-0 |
| HCatalog | 3.1.3-amzn-17 | 3.1.3-amzn-16 | 3.1.3-amzn-15 | 3.1.3-amzn-14 |
| Hadoop | 3.4.1-amzn-0 | 3.4.0-amzn-3 | 3.4.0-amzn-2 | 3.4.0-amzn-1 |
| Hive | 3.1.3-amzn-17 | 3.1.3-amzn-16 | 3.1.3-amzn-15 | 3.1.3-amzn-14 |
| Hudi | 0.15.0-amzn-5 | 0.15.0-amzn-4 | 0.15.0-amzn-3 | 0.15.0-amzn-2 |
| Hue | 4.11.0 | 4.11.0 | 4.11.0 | 4.11.0 |
| Iceberg | 1.7.1-amzn-1 | 1.7.1-amzn-0 | 1.6.1-amzn-2 | 1.6.1-amzn-1 |
| JupyterEnterpriseGateway | 2.6.0 | 2.6.0 | 2.6.0 | 2.6.0 |
| JupyterHub | 1.5.0 | 1.5.0 | 1.5.0 | 1.5.0 |
| Livy | 0.8.0-incubating | 0.8.0-incubating | 0.8.0-incubating | 0.8.0-incubating |
| MXNet | - | - | - | - |
| Mahout | - | - | - | - |
| Oozie | 5.2.1 | 5.2.1 | 5.2.1 | 5.2.1 |
| Phoenix | 5.2.1 | 5.2.1 | 5.2.0 | 5.2.0 |
| Pig | 0.17.0 | 0.17.0 | 0.17.0 | 0.17.0 |
| Presto | 0.287-amzn-2 | 0.287-amzn-1 | 0.287-amzn-1 | 0.287-amzn-0 |
| Spark | 3.5.4-amzn-0 | 3.5.3-amzn-1 | 3.5.3-amzn-0 | 3.5.2-amzn-1 |
| Sqoop | - | - | - | - |
| TensorFlow | 2.16.1 | 2.16.1 | 2.16.1 | 2.16.1 |
| Tez | 0.10.2-amzn-15 | 0.10.2-amzn-14 | 0.10.2-amzn-13 | 0.10.2-amzn-12 |
| Trino (PrestoSQL) | 467-amzn-1 | 467-amzn-0 | 457-amzn-0 | 446-amzn-0 |
| Zeppelin | 0.11.1 | 0.11.1 | 0.11.1 | 0.11.1 |
| ZooKeeper | 3.9.3-amzn-0 | 3.9.2-amzn-1 | 3.9.2-amzn-0 | 3.9.2-amzn-0 |
# 7.8.0 릴리스 구성 요소 세부 정보
Amazon EMR 7.7.0의 *추가* 패키지에 대한 자세한 내용은 다음 표를 참조하세요.
| 애플리케이션 | 애플리케이션 유형 | 패키지 | 패키지 유형 | 패키지 버전 |
| --- | --- | --- | --- | --- |
| AmazonCloudWatchAgent | Core | hadoop-hdfs-journalnode | 추가 항목 | 3.4.1-amzn-0-1.amzn2023 |
| AmazonCloudWatchAgent | Core | ranger-kms | 추가 항목 | 2.0.0-1.amzn2023 |
| AmazonCloudWatchAgent | Core | s3-dist-cp | 추가 항목 | 2.38.0-1.amzn2023 |
| AmazonCloudWatchAgent | Core | zookeeper | 추가 항목 | 3.9.3-amzn-0-1.amzn2023 |
| AmazonCloudWatchAgent | Core | zookeeper-server | 추가 항목 | 3.9.3-amzn-0-1.amzn2023 |
| Flink | Core | hadoop-client | 추가 항목 | 3.4.0.amzn.3-1.amzn2023 |
| Flink | Core | hadoop-hdfs | 추가 항목 | 3.4.1-amzn-0-1.amzn2023 |
| Flink | Core | hadoop-hdfs-datanode | 추가 항목 | 3.4.1-amzn-0-1.amzn2023 |
| Flink | Core | hadoop-hdfs-journalnode | 추가 항목 | 3.4.1-amzn-0-1.amzn2023 |
| Flink | Core | hadoop-hdfs-namenode | 추가 항목 | 3.4.1-amzn-0-1.amzn2023 |
| Flink | Core | hadoop-httpfs | 추가 항목 | 3.4.1-amzn-0-1.amzn2023 |
| Flink | Core | hadoop-kms | 추가 항목 | 3.4.1-amzn-0-1.amzn2023 |
| Flink | Core | hadoop-mapreduce | 추가 항목 | 3.4.1-amzn-0-1.amzn2023 |
| Flink | Core | hadoop-mapreduce-historyserver | 추가 항목 | 3.4.1-amzn-0-1.amzn2023 |
| Flink | Core | hadoop-yarn | 추가 항목 | 3.4.1-amzn-0-1.amzn2023 |
| Flink | Core | hadoop-yarn-nodemanager | 추가 항목 | 3.4.1-amzn-0-1.amzn2023 |
| Flink | Core | hadoop-yarn-proxyserver | 추가 항목 | 3.4.1-amzn-0-1.amzn2023 |
| Flink | Core | hadoop-yarn-resourcemanager | 추가 항목 | 3.4.1-amzn-0-1.amzn2023 |
| Flink | Core | hadoop-yarn-timelineserver | 추가 항목 | 3.4.1-amzn-0-1.amzn2023 |
| Flink | Core | hudi | 추가 항목 | 0.15.0-amzn-5-1.amzn2023 |
| Flink | Core | ranger-kms | 추가 항목 | 2.0.0-1.amzn2023 |
| Flink | Core | hadoop | 추가 항목 | 3.4.1-amzn-0-1.amzn2023 |
| HBase | Core | s3-dist-cp | 추가 항목 | 2.38.0-1.amzn2023 |
| HCatalog | Core | hadoop-yarn-proxyserver | 추가 항목 | 3.4.1-amzn-0-1.amzn2023 |
| HCatalog | Core | mariadb-connector-java | 추가 항목 | |
| Hive | Core | hadoop-httpfs | 추가 항목 | 3.4.1-amzn-0-1.amzn2023 |
| Hive | Core | hadoop-yarn-proxyserver | 추가 항목 | 3.4.1-amzn-0-1.amzn2023 |
| Hive | Core | hive-hbase | 추가 항목 | 3.1.3-amzn-17-1.amzn2023 |
| Hive | Core | mariadb-connector-java | 추가 항목 | 3.1.3-amzn-17-1 |
| Hive | Core | s3-dist-cp | 추가 항목 | 2.38.0-1.amzn2023 |
| 피닉스 | Core | s3-dist-cp | 추가 항목 | 2.38.0-1.amzn2023 |
| Spark | Core | spark-datanucleus | 추가 항목 | 3.5.3.amzn.1-1.amzn2023 |
| Tez의 Hive 실행 시간 비교 | Core | hadoop-mapreduce | 추가 항목 | 3.4.1-amzn-0-1.amzn2023 |
| Tez의 Hive 실행 시간 비교 | Core | hadoop-mapreduce-historyserver | 추가 항목 | 3.4.1-amzn-0-1.amzn2023 |
| Tez의 Hive 실행 시간 비교 | Core | hadoop-yarn-proxyserver | 추가 항목 | 3.4.1-amzn-0-1.amzn2023 |
| Trino | Core | bigtop-utils | 추가 항목 | 1.2.0-1.amzn2023 |
| Trino | Core | hadoop-client | 추가 항목 | 3.4.1.amzn.0-1.amzn2023 |
| Trino | Core | hadoop-hdfs | 추가 항목 | 3.4.1.amzn.0-1.amzn2023 |
| Trino | Core | hadoop-hdfs-datanode | 추가 항목 | 3.4.1.amzn.0-1.amzn2023 |
| Trino | Core | hadoop-hdfs-journalnode | 추가 항목 | 3.4.1.amzn.0-1.amzn2023 |
| Trino | Core | hadoop-hdfs-namenode | 추가 항목 | 3.4.1.amzn.0-1.amzn2023 |
| Trino | Core | hadoop-kms | 추가 항목 | 3.4.1.amzn.0-1.amzn2023 |
| Trino | Core | hadoop-mapreduce | 추가 항목 | 3.4.1.amzn.0-1.amzn2023 |
| Trino | Core | hadoop-mapreduce-historyserver | 추가 항목 | 3.4.1.amzn.0-1.amzn2023 |
| Trino | Core | hadoop-yarn | 추가 항목 | 3.4.1.amzn.0-1.amzn2023 |
| Trino | Core | hadoop-yarn-nodemanager | 추가 항목 | 3.4.1.amzn.0-1.amzn2023 |
| Trino | Core | hadoop-yarn-proxyserver | 추가 항목 | 3.4.1.amzn.0-1.amzn2023 |
| Trino | Core | hadoop-yarn-resourcemanager | 추가 항목 | 3.4.1.amzn.0-1.amzn2023 |
| Trino | Core | hadoop-yarn-timelineserver | 추가 항목 | 3.4.1.amzn.0-1.amzn2023 |
| Trino | Core | hive | 추가 항목 | 3.1.3.amzn.17-1.amzn2023 |
| Trino | Core | hive-hcatalog-server | 추가 항목 | 3.1.3.amzn.17-1.amzn2023 |
| Trino | Core | mariadb-connector-java | 추가 항목 | 2.7.2-1 |
| Trino | Core | ranger-kms | 추가 항목 | 2.0.0-1.amzn2023 |
| Trino | Core | zookeeper | 추가 항목 | 3.9.3.amzn.0-1.amzn2023 |
| Trino | Core | zookeeper-server | 추가 항목 | 3.9.3.amzn.0-1.amzn2023 |
| Trino | Core | bigtop-groovy | 추가 항목 | 2.5.4-1.amzn2023 |
| Trino | Core | bigtop-jsvc | 추가 항목 | 1.2.4-1.amzn2023 |
| Trino | Core | hadoop | 추가 항목 | 3.4.1.amzn.0-1.amzn2023 |
| Trino | Core | hadoop-lzo | 추가 항목 | 0.4.19-1.amzn2023 |
| Trino | Core | hive-hcatalog | 추가 항목 | 3.1.3.amzn.17-1.amzn2023 |
| Trino | Core | hive-jdbc | 추가 항목 | 3.1.3.amzn.17-1.amzn2023 |
| Zookeeper | Core | emrfs | 추가 항목 | 3.9.3.amzn.0-1.amzn2023 |
| Zookeeper | Core | hadoop-client | 추가 항목 | 3.9.3.amzn.0-1.amzn2023 |
| Zookeeper | Core | hadoop-hdfs | 추가 항목 | 3.9.3.amzn.0-1.amzn2023 |
| Zookeeper | Core | hadoop-hdfs-datanode | 추가 항목 | 3.9.3.amzn.0-1.amzn2023 |
| Zookeeper | Core | hadoop-hdfs-journalnode | 추가 항목 | 3.9.3.amzn.0-1.amzn2023 |
| Zookeeper | Core | hadoop-hdfs-namenode | 추가 항목 | 3.9.3.amzn.0-1.amzn2023 |
| Zookeeper | Core | hadoop-httpfs | 추가 항목 | 3.9.3.amzn.0-1.amzn2023 |
| Zookeeper | Core | hadoop-kms | 추가 항목 | 3.9.3.amzn.0-1.amzn2023 |
| Zookeeper | Core | hadoop-mapreduce | 추가 항목 | 3.4.1.amzn.0-1.amzn2023 |
| Zookeeper | Core | hadoop-mapreduce-historyserver | 추가 항목 | 3.4.1.amzn.0-1.amzn2023 |
| Zookeeper | Core | hadoop-yarn | 추가 항목 | 3.4.1.amzn.0-1.amzn2023 |
| Zookeeper | Core | hadoop-yarn-nodemanager | 추가 항목 | 3.4.1.amzn.0-1.amzn2023 |
| Zookeeper | Core | hadoop-yarn-proxyserver | 추가 항목 | 3.4.1.amzn.0-1.amzn2023 |
| Zookeeper | Core | hadoop-yarn-resourcemanager | 추가 항목 | 3.4.1.amzn.0-1.amzn2023 |
| Zookeeper | Core | hadoop-yarn-timelineserver | 추가 항목 | 3.4.1.amzn.0-1.amzn2023 |
| Zookeeper | Core | ranger-kms | 추가 항목 | 2.0.0-1.amzn2023 |
# 7.8.0 일반적인 취약성 및 노출
다음 표에는 Amazon EMR 7.8.0의 권장 구성에서 실행되는 EMR 클러스터에 영향을 주지 않는 모든 CVEs가 나열되어 있습니다. Amazon EMR은 업스트림 오픈 소스의 수정 사항 가용성에 종속되어 있으며, Amazon EMR이 수정 사항을 확인한 후 90일 이내에 코어 엔진 구성 요소의 일부로 안정적인 최신 버전을 제공합니다.
이 표는 2025년 3월 6일에 업데이트되었습니다.
| CVE ID | 심각도 | CVE 세부 정보 URL |
| --- | --- | --- |
| CVE-2015-1832 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2015-1832](https://nvd.nist.gov/vuln/detail/CVE-2015-1832) |
| CVE-2016-5018 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2016-5018](https://nvd.nist.gov/vuln/detail/CVE-2016-5018) |
| CVE-2017-15095 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2017-15095](https://nvd.nist.gov/vuln/detail/CVE-2017-15095) |
| CVE-2017-17485 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2017-17485](https://nvd.nist.gov/vuln/detail/CVE-2017-17485) |
| CVE-2017-7525 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2017-7525](https://nvd.nist.gov/vuln/detail/CVE-2017-7525) |
| CVE-2018-11307 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-11307](https://nvd.nist.gov/vuln/detail/CVE-2018-11307) |
| CVE-2018-11307 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-11307](https://nvd.nist.gov/vuln/detail/CVE-2018-11307) |
| CVE-2018-14718 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-14718](https://nvd.nist.gov/vuln/detail/CVE-2018-14718) |
| CVE-2018-14718 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-14718](https://nvd.nist.gov/vuln/detail/CVE-2018-14718) |
| CVE-2018-14719 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-14719](https://nvd.nist.gov/vuln/detail/CVE-2018-14719) |
| CVE-2018-14719 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-14719](https://nvd.nist.gov/vuln/detail/CVE-2018-14719) |
| CVE-2018-14720 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-14720](https://nvd.nist.gov/vuln/detail/CVE-2018-14720) |
| CVE-2018-14720 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-14720](https://nvd.nist.gov/vuln/detail/CVE-2018-14720) |
| CVE-2018-14721 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-14721](https://nvd.nist.gov/vuln/detail/CVE-2018-14721) |
| CVE-2018-14721 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-14721](https://nvd.nist.gov/vuln/detail/CVE-2018-14721) |
| CVE-2018-19360 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-19360](https://nvd.nist.gov/vuln/detail/CVE-2018-19360) |
| CVE-2018-19360 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-19360](https://nvd.nist.gov/vuln/detail/CVE-2018-19360) |
| CVE-2018-19361 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-19361](https://nvd.nist.gov/vuln/detail/CVE-2018-19361) |
| CVE-2018-19361 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-19361](https://nvd.nist.gov/vuln/detail/CVE-2018-19361) |
| CVE-2018-19362 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-19362](https://nvd.nist.gov/vuln/detail/CVE-2018-19362) |
| CVE-2018-19362 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-19362](https://nvd.nist.gov/vuln/detail/CVE-2018-19362) |
| CVE-2018-7489 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-7489](https://nvd.nist.gov/vuln/detail/CVE-2018-7489) |
| CVE-2018-7489 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-7489](https://nvd.nist.gov/vuln/detail/CVE-2018-7489) |
| CVE-2019-10202 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-10202](https://nvd.nist.gov/vuln/detail/CVE-2019-10202) |
| CVE-2019-14379 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14379](https://nvd.nist.gov/vuln/detail/CVE-2019-14379) |
| CVE-2019-14379 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14379](https://nvd.nist.gov/vuln/detail/CVE-2019-14379) |
| CVE-2019-14540 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14540](https://nvd.nist.gov/vuln/detail/CVE-2019-14540) |
| CVE-2019-14540 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14540](https://nvd.nist.gov/vuln/detail/CVE-2019-14540) |
| CVE-2019-14892 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14892](https://nvd.nist.gov/vuln/detail/CVE-2019-14892) |
| CVE-2019-14892 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14892](https://nvd.nist.gov/vuln/detail/CVE-2019-14892) |
| CVE-2019-14893 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14893](https://nvd.nist.gov/vuln/detail/CVE-2019-14893) |
| CVE-2019-14893 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14893](https://nvd.nist.gov/vuln/detail/CVE-2019-14893) |
| CVE-2019-16335 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-16335](https://nvd.nist.gov/vuln/detail/CVE-2019-16335) |
| CVE-2019-16335 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-16335](https://nvd.nist.gov/vuln/detail/CVE-2019-16335) |
| CVE-2019-16942 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-16942](https://nvd.nist.gov/vuln/detail/CVE-2019-16942) |
| CVE-2019-16942 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-16942](https://nvd.nist.gov/vuln/detail/CVE-2019-16942) |
| CVE-2019-16943 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-16943](https://nvd.nist.gov/vuln/detail/CVE-2019-16943) |
| CVE-2019-16943 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-16943](https://nvd.nist.gov/vuln/detail/CVE-2019-16943) |
| CVE-2019-17267 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-17267](https://nvd.nist.gov/vuln/detail/CVE-2019-17267) |
| CVE-2019-17267 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-17267](https://nvd.nist.gov/vuln/detail/CVE-2019-17267) |
| CVE-2019-17531 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-17531](https://nvd.nist.gov/vuln/detail/CVE-2019-17531) |
| CVE-2019-17531 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-17531](https://nvd.nist.gov/vuln/detail/CVE-2019-17531) |
| CVE-2019-20330 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-20330](https://nvd.nist.gov/vuln/detail/CVE-2019-20330) |
| CVE-2019-20330 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-20330](https://nvd.nist.gov/vuln/detail/CVE-2019-20330) |
| CVE-2020-8840 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8840](https://nvd.nist.gov/vuln/detail/CVE-2020-8840) |
| CVE-2020-8840 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8840](https://nvd.nist.gov/vuln/detail/CVE-2020-8840) |
| CVE-2020-9546 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-9546](https://nvd.nist.gov/vuln/detail/CVE-2020-9546) |
| CVE-2020-9546 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-9546](https://nvd.nist.gov/vuln/detail/CVE-2020-9546) |
| CVE-2020-9547 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-9547](https://nvd.nist.gov/vuln/detail/CVE-2020-9547) |
| CVE-2020-9547 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-9547](https://nvd.nist.gov/vuln/detail/CVE-2020-9547) |
| CVE-2020-9548 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-9548](https://nvd.nist.gov/vuln/detail/CVE-2020-9548) |
| CVE-2020-9548 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-9548](https://nvd.nist.gov/vuln/detail/CVE-2020-9548) |
| CVE-2022-1471 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-1471](https://nvd.nist.gov/vuln/detail/CVE-2022-1471) |
| CVE-2022-1471 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-1471](https://nvd.nist.gov/vuln/detail/CVE-2022-1471) |
| CVE-2022-37865 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-37865](https://nvd.nist.gov/vuln/detail/CVE-2022-37865) |
| CVE-2022-39135 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-39135](https://nvd.nist.gov/vuln/detail/CVE-2022-39135) |
| CVE-2022-42889 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42889](https://nvd.nist.gov/vuln/detail/CVE-2022-42889) |
| CVE-2022-46337 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-46337](https://nvd.nist.gov/vuln/detail/CVE-2022-46337) |
| CVE-2022-46337 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-46337](https://nvd.nist.gov/vuln/detail/CVE-2022-46337) |
| CVE-2024-47561 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2024-47561](https://nvd.nist.gov/vuln/detail/CVE-2024-47561) |
| CVE-2024-47561 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2024-47561](https://nvd.nist.gov/vuln/detail/CVE-2024-47561) |
| CVE-2024-47561 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2024-47561](https://nvd.nist.gov/vuln/detail/CVE-2024-47561) |
| CVE-2024-47561 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2024-47561](https://nvd.nist.gov/vuln/detail/CVE-2024-47561) |
| CVE-2024-47561 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2024-47561](https://nvd.nist.gov/vuln/detail/CVE-2024-47561) |
| CVE-2024-52046 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2024-52046](https://nvd.nist.gov/vuln/detail/CVE-2024-52046) |
| CVE-2024-52046 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2024-52046](https://nvd.nist.gov/vuln/detail/CVE-2024-52046) |
| CVE-2024-53990 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2024-53990](https://nvd.nist.gov/vuln/detail/CVE-2024-53990) |
| CVE-2024-53990 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2024-53990](https://nvd.nist.gov/vuln/detail/CVE-2024-53990) |
| CVE-2015-5237 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2015-5237](https://nvd.nist.gov/vuln/detail/CVE-2015-5237) |
| CVE-2015-5237 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2015-5237](https://nvd.nist.gov/vuln/detail/CVE-2015-5237) |
| CVE-2016-6796 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2016-6796](https://nvd.nist.gov/vuln/detail/CVE-2016-6796) |
| CVE-2018-1000180 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-1000180](https://nvd.nist.gov/vuln/detail/CVE-2018-1000180) |
| CVE-2018-12022 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-12022](https://nvd.nist.gov/vuln/detail/CVE-2018-12022) |
| CVE-2018-12022 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-12022](https://nvd.nist.gov/vuln/detail/CVE-2018-12022) |
| CVE-2018-12023 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-12023](https://nvd.nist.gov/vuln/detail/CVE-2018-12023) |
| CVE-2018-12023 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-12023](https://nvd.nist.gov/vuln/detail/CVE-2018-12023) |
| CVE-2018-5968 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-5968](https://nvd.nist.gov/vuln/detail/CVE-2018-5968) |
| CVE-2019-0205 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-0205](https://nvd.nist.gov/vuln/detail/CVE-2019-0205) |
| CVE-2019-0205 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-0205](https://nvd.nist.gov/vuln/detail/CVE-2019-0205) |
| CVE-2019-10172 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-10172](https://nvd.nist.gov/vuln/detail/CVE-2019-10172) |
| CVE-2019-12086 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-12086](https://nvd.nist.gov/vuln/detail/CVE-2019-12086) |
| CVE-2019-12086 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-12086](https://nvd.nist.gov/vuln/detail/CVE-2019-12086) |
| CVE-2019-14439 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14439](https://nvd.nist.gov/vuln/detail/CVE-2019-14439) |
| CVE-2019-14439 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14439](https://nvd.nist.gov/vuln/detail/CVE-2019-14439) |
| CVE-2020-10650 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10650](https://nvd.nist.gov/vuln/detail/CVE-2020-10650) |
| CVE-2020-10650 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10650](https://nvd.nist.gov/vuln/detail/CVE-2020-10650) |
| CVE-2020-10672 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10672](https://nvd.nist.gov/vuln/detail/CVE-2020-10672) |
| CVE-2020-10672 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10672](https://nvd.nist.gov/vuln/detail/CVE-2020-10672) |
| CVE-2020-10673 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10673](https://nvd.nist.gov/vuln/detail/CVE-2020-10673) |
| CVE-2020-10673 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10673](https://nvd.nist.gov/vuln/detail/CVE-2020-10673) |
| CVE-2020-10968 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10968](https://nvd.nist.gov/vuln/detail/CVE-2020-10968) |
| CVE-2020-10968 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10968](https://nvd.nist.gov/vuln/detail/CVE-2020-10968) |
| CVE-2020-10969 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10969](https://nvd.nist.gov/vuln/detail/CVE-2020-10969) |
| CVE-2020-10969 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10969](https://nvd.nist.gov/vuln/detail/CVE-2020-10969) |
| CVE-2020-11111 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11111](https://nvd.nist.gov/vuln/detail/CVE-2020-11111) |
| CVE-2020-11111 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11111](https://nvd.nist.gov/vuln/detail/CVE-2020-11111) |
| CVE-2020-11112 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11112](https://nvd.nist.gov/vuln/detail/CVE-2020-11112) |
| CVE-2020-11112 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11112](https://nvd.nist.gov/vuln/detail/CVE-2020-11112) |
| CVE-2020-11113 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11113](https://nvd.nist.gov/vuln/detail/CVE-2020-11113) |
| CVE-2020-11113 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11113](https://nvd.nist.gov/vuln/detail/CVE-2020-11113) |
| CVE-2020-11619 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11619](https://nvd.nist.gov/vuln/detail/CVE-2020-11619) |
| CVE-2020-11619 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11619](https://nvd.nist.gov/vuln/detail/CVE-2020-11619) |
| CVE-2020-11620 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11620](https://nvd.nist.gov/vuln/detail/CVE-2020-11620) |
| CVE-2020-11620 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11620](https://nvd.nist.gov/vuln/detail/CVE-2020-11620) |
| CVE-2020-13936 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-13936](https://nvd.nist.gov/vuln/detail/CVE-2020-13936) |
| CVE-2020-13949 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-13949](https://nvd.nist.gov/vuln/detail/CVE-2020-13949) |
| CVE-2020-13949 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-13949](https://nvd.nist.gov/vuln/detail/CVE-2020-13949) |
| CVE-2020-13949 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-13949](https://nvd.nist.gov/vuln/detail/CVE-2020-13949) |
| CVE-2020-14060 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14060](https://nvd.nist.gov/vuln/detail/CVE-2020-14060) |
| CVE-2020-14060 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14060](https://nvd.nist.gov/vuln/detail/CVE-2020-14060) |
| CVE-2020-14061 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14061](https://nvd.nist.gov/vuln/detail/CVE-2020-14061) |
| CVE-2020-14061 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14061](https://nvd.nist.gov/vuln/detail/CVE-2020-14061) |
| CVE-2020-14062 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14062](https://nvd.nist.gov/vuln/detail/CVE-2020-14062) |
| CVE-2020-14062 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14062](https://nvd.nist.gov/vuln/detail/CVE-2020-14062) |
| CVE-2020-14195 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14195](https://nvd.nist.gov/vuln/detail/CVE-2020-14195) |
| CVE-2020-14195 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14195](https://nvd.nist.gov/vuln/detail/CVE-2020-14195) |
| CVE-2020-24616 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-24616](https://nvd.nist.gov/vuln/detail/CVE-2020-24616) |
| CVE-2020-24616 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-24616](https://nvd.nist.gov/vuln/detail/CVE-2020-24616) |
| CVE-2020-24750 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-24750](https://nvd.nist.gov/vuln/detail/CVE-2020-24750) |
| CVE-2020-24750 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-24750](https://nvd.nist.gov/vuln/detail/CVE-2020-24750) |
| CVE-2020-25649 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-25649](https://nvd.nist.gov/vuln/detail/CVE-2020-25649) |
| CVE-2020-28052 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-28052](https://nvd.nist.gov/vuln/detail/CVE-2020-28052) |
| CVE-2020-35490 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-35490](https://nvd.nist.gov/vuln/detail/CVE-2020-35490) |
| CVE-2020-35490 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-35490](https://nvd.nist.gov/vuln/detail/CVE-2020-35490) |
| CVE-2020-35491 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-35491](https://nvd.nist.gov/vuln/detail/CVE-2020-35491) |
| CVE-2020-35491 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-35491](https://nvd.nist.gov/vuln/detail/CVE-2020-35491) |
| CVE-2020-35728 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-35728](https://nvd.nist.gov/vuln/detail/CVE-2020-35728) |
| CVE-2020-35728 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-35728](https://nvd.nist.gov/vuln/detail/CVE-2020-35728) |
| CVE-2020-36179 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36179](https://nvd.nist.gov/vuln/detail/CVE-2020-36179) |
| CVE-2020-36179 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36179](https://nvd.nist.gov/vuln/detail/CVE-2020-36179) |
| CVE-2020-36180 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36180](https://nvd.nist.gov/vuln/detail/CVE-2020-36180) |
| CVE-2020-36180 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36180](https://nvd.nist.gov/vuln/detail/CVE-2020-36180) |
| CVE-2020-36181 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36181](https://nvd.nist.gov/vuln/detail/CVE-2020-36181) |
| CVE-2020-36181 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36181](https://nvd.nist.gov/vuln/detail/CVE-2020-36181) |
| CVE-2020-36182 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36182](https://nvd.nist.gov/vuln/detail/CVE-2020-36182) |
| CVE-2020-36182 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36182](https://nvd.nist.gov/vuln/detail/CVE-2020-36182) |
| CVE-2020-36183 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36183](https://nvd.nist.gov/vuln/detail/CVE-2020-36183) |
| CVE-2020-36183 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36183](https://nvd.nist.gov/vuln/detail/CVE-2020-36183) |
| CVE-2020-36184 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36184](https://nvd.nist.gov/vuln/detail/CVE-2020-36184) |
| CVE-2020-36184 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36184](https://nvd.nist.gov/vuln/detail/CVE-2020-36184) |
| CVE-2020-36185 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36185](https://nvd.nist.gov/vuln/detail/CVE-2020-36185) |
| CVE-2020-36185 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36185](https://nvd.nist.gov/vuln/detail/CVE-2020-36185) |
| CVE-2020-36186 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36186](https://nvd.nist.gov/vuln/detail/CVE-2020-36186) |
| CVE-2020-36186 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36186](https://nvd.nist.gov/vuln/detail/CVE-2020-36186) |
| CVE-2020-36187 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36187](https://nvd.nist.gov/vuln/detail/CVE-2020-36187) |
| CVE-2020-36187 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36187](https://nvd.nist.gov/vuln/detail/CVE-2020-36187) |
| CVE-2020-36188 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36188](https://nvd.nist.gov/vuln/detail/CVE-2020-36188) |
| CVE-2020-36188 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36188](https://nvd.nist.gov/vuln/detail/CVE-2020-36188) |
| CVE-2020-36189 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36189](https://nvd.nist.gov/vuln/detail/CVE-2020-36189) |
| CVE-2020-36189 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36189](https://nvd.nist.gov/vuln/detail/CVE-2020-36189) |
| CVE-2020-36518 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36518](https://nvd.nist.gov/vuln/detail/CVE-2020-36518) |
| CVE-2020-36518 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36518](https://nvd.nist.gov/vuln/detail/CVE-2020-36518) |
| CVE-2021-20190 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-20190](https://nvd.nist.gov/vuln/detail/CVE-2021-20190) |
| CVE-2021-20190 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-20190](https://nvd.nist.gov/vuln/detail/CVE-2021-20190) |
| CVE-2021-31684 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-31684](https://nvd.nist.gov/vuln/detail/CVE-2021-31684) |
| CVE-2021-34538 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-34538](https://nvd.nist.gov/vuln/detail/CVE-2021-34538) |
| CVE-2021-34538 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-34538](https://nvd.nist.gov/vuln/detail/CVE-2021-34538) |
| CVE-2021-34538 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-34538](https://nvd.nist.gov/vuln/detail/CVE-2021-34538) |
| CVE-2022-25647 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-25647](https://nvd.nist.gov/vuln/detail/CVE-2022-25647) |
| CVE-2022-25647 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-25647](https://nvd.nist.gov/vuln/detail/CVE-2022-25647) |
| CVE-2022-25647 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-25647](https://nvd.nist.gov/vuln/detail/CVE-2022-25647) |
| CVE-2022-25857 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-25857](https://nvd.nist.gov/vuln/detail/CVE-2022-25857) |
| CVE-2022-3171 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3171](https://nvd.nist.gov/vuln/detail/CVE-2022-3171) |
| CVE-2022-3171 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3171](https://nvd.nist.gov/vuln/detail/CVE-2022-3171) |
| CVE-2022-3509 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3509](https://nvd.nist.gov/vuln/detail/CVE-2022-3509) |
| CVE-2022-3509 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3509](https://nvd.nist.gov/vuln/detail/CVE-2022-3509) |
| CVE-2022-3510 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3510](https://nvd.nist.gov/vuln/detail/CVE-2022-3510) |
| CVE-2022-3510 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3510](https://nvd.nist.gov/vuln/detail/CVE-2022-3510) |
| CVE-2022-36364 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-36364](https://nvd.nist.gov/vuln/detail/CVE-2022-36364) |
| CVE-2022-37866 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-37866](https://nvd.nist.gov/vuln/detail/CVE-2022-37866) |
| CVE-2022-40149 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-40149](https://nvd.nist.gov/vuln/detail/CVE-2022-40149) |
| CVE-2022-40149 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-40149](https://nvd.nist.gov/vuln/detail/CVE-2022-40149) |
| CVE-2022-40150 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-40150](https://nvd.nist.gov/vuln/detail/CVE-2022-40150) |
| CVE-2022-40150 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-40150](https://nvd.nist.gov/vuln/detail/CVE-2022-40150) |
| CVE-2022-42003 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42003](https://nvd.nist.gov/vuln/detail/CVE-2022-42003) |
| CVE-2022-42003 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42003](https://nvd.nist.gov/vuln/detail/CVE-2022-42003) |
| CVE-2022-42003 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42003](https://nvd.nist.gov/vuln/detail/CVE-2022-42003) |
| CVE-2022-42003 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42003](https://nvd.nist.gov/vuln/detail/CVE-2022-42003) |
| CVE-2022-42003 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42003](https://nvd.nist.gov/vuln/detail/CVE-2022-42003) |
| CVE-2022-42004 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42004](https://nvd.nist.gov/vuln/detail/CVE-2022-42004) |
| CVE-2022-42004 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42004](https://nvd.nist.gov/vuln/detail/CVE-2022-42004) |
| CVE-2022-42004 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42004](https://nvd.nist.gov/vuln/detail/CVE-2022-42004) |
| CVE-2022-42004 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42004](https://nvd.nist.gov/vuln/detail/CVE-2022-42004) |
| CVE-2022-45685 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-45685](https://nvd.nist.gov/vuln/detail/CVE-2022-45685) |
| CVE-2022-45685 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-45685](https://nvd.nist.gov/vuln/detail/CVE-2022-45685) |
| CVE-2022-45693 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-45693](https://nvd.nist.gov/vuln/detail/CVE-2022-45693) |
| CVE-2022-45693 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-45693](https://nvd.nist.gov/vuln/detail/CVE-2022-45693) |
| CVE-2022-46751 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-46751](https://nvd.nist.gov/vuln/detail/CVE-2022-46751) |
| CVE-2022-46751 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-46751](https://nvd.nist.gov/vuln/detail/CVE-2022-46751) |
| CVE-2023-1370 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-1370](https://nvd.nist.gov/vuln/detail/CVE-2023-1370) |
| CVE-2023-1370 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-1370](https://nvd.nist.gov/vuln/detail/CVE-2023-1370) |
| CVE-2023-1436 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-1436](https://nvd.nist.gov/vuln/detail/CVE-2023-1436) |
| CVE-2023-1436 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-1436](https://nvd.nist.gov/vuln/detail/CVE-2023-1436) |
| CVE-2023-20883 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-20883](https://nvd.nist.gov/vuln/detail/CVE-2023-20883) |
| CVE-2023-25194 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-25194](https://nvd.nist.gov/vuln/detail/CVE-2023-25194) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-34453 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-34453](https://nvd.nist.gov/vuln/detail/CVE-2023-34453) |
| CVE-2023-34454 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-34454](https://nvd.nist.gov/vuln/detail/CVE-2023-34454) |
| CVE-2023-34455 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-34455](https://nvd.nist.gov/vuln/detail/CVE-2023-34455) |
| CVE-2023-3635 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-3635](https://nvd.nist.gov/vuln/detail/CVE-2023-3635) |
| CVE-2023-3635 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-3635](https://nvd.nist.gov/vuln/detail/CVE-2023-3635) |
| CVE-2023-39410 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-39410](https://nvd.nist.gov/vuln/detail/CVE-2023-39410) |
| CVE-2023-39410 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-39410](https://nvd.nist.gov/vuln/detail/CVE-2023-39410) |
| CVE-2023-39410 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-39410](https://nvd.nist.gov/vuln/detail/CVE-2023-39410) |
| CVE-2023-39410 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-39410](https://nvd.nist.gov/vuln/detail/CVE-2023-39410) |
| CVE-2023-43642 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-43642](https://nvd.nist.gov/vuln/detail/CVE-2023-43642) |
| CVE-2023-5072 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-5072](https://nvd.nist.gov/vuln/detail/CVE-2023-5072) |
| CVE-2023-6378 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-6378](https://nvd.nist.gov/vuln/detail/CVE-2023-6378) |
| CVE-2023-6378 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-6378](https://nvd.nist.gov/vuln/detail/CVE-2023-6378) |
| CVE-2023-6481 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-6481](https://nvd.nist.gov/vuln/detail/CVE-2023-6481) |
| CVE-2023-6481 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-6481](https://nvd.nist.gov/vuln/detail/CVE-2023-6481) |
| CVE-2024-7254 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-7254](https://nvd.nist.gov/vuln/detail/CVE-2024-7254) |
| CVE-2024-7254 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-7254](https://nvd.nist.gov/vuln/detail/CVE-2024-7254) |
| CVE-2024-7254 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-7254](https://nvd.nist.gov/vuln/detail/CVE-2024-7254) |
| CVE-2024-7254 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-7254](https://nvd.nist.gov/vuln/detail/CVE-2024-7254) |
| CVE-2024-7254 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-7254](https://nvd.nist.gov/vuln/detail/CVE-2024-7254) |
| CVE-2024-7254 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-7254](https://nvd.nist.gov/vuln/detail/CVE-2024-7254) |
| CVE-2024-7254 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-7254](https://nvd.nist.gov/vuln/detail/CVE-2024-7254) |
| CVE-2012-5783 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2012-5783](https://nvd.nist.gov/vuln/detail/CVE-2012-5783) |
| CVE-2012-6153 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2012-6153](https://nvd.nist.gov/vuln/detail/CVE-2012-6153) |
| CVE-2018-10237 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2018-10237](https://nvd.nist.gov/vuln/detail/CVE-2018-10237) |
| CVE-2018-10237 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2018-10237](https://nvd.nist.gov/vuln/detail/CVE-2018-10237) |
| CVE-2018-10237 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2018-10237](https://nvd.nist.gov/vuln/detail/CVE-2018-10237) |
| CVE-2018-10237 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2018-10237](https://nvd.nist.gov/vuln/detail/CVE-2018-10237) |
| CVE-2018-10237 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2018-10237](https://nvd.nist.gov/vuln/detail/CVE-2018-10237) |
| CVE-2018-10237 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2018-10237](https://nvd.nist.gov/vuln/detail/CVE-2018-10237) |
| CVE-2018-11798 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2018-11798](https://nvd.nist.gov/vuln/detail/CVE-2018-11798) |
| CVE-2018-1313 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2018-1313](https://nvd.nist.gov/vuln/detail/CVE-2018-1313) |
| CVE-2019-10219 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2019-10219](https://nvd.nist.gov/vuln/detail/CVE-2019-10219) |
| CVE-2019-12384 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2019-12384](https://nvd.nist.gov/vuln/detail/CVE-2019-12384) |
| CVE-2019-12384 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2019-12384](https://nvd.nist.gov/vuln/detail/CVE-2019-12384) |
| CVE-2019-12814 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2019-12814](https://nvd.nist.gov/vuln/detail/CVE-2019-12814) |
| CVE-2019-12814 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2019-12814](https://nvd.nist.gov/vuln/detail/CVE-2019-12814) |
| CVE-2020-10693 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10693](https://nvd.nist.gov/vuln/detail/CVE-2020-10693) |
| CVE-2020-13955 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-13955](https://nvd.nist.gov/vuln/detail/CVE-2020-13955) |
| CVE-2020-13956 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-13956](https://nvd.nist.gov/vuln/detail/CVE-2020-13956) |
| CVE-2020-15250 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-15250](https://nvd.nist.gov/vuln/detail/CVE-2020-15250) |
| CVE-2020-15250 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-15250](https://nvd.nist.gov/vuln/detail/CVE-2020-15250) |
| CVE-2020-15522 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-15522](https://nvd.nist.gov/vuln/detail/CVE-2020-15522) |
| CVE-2020-15522 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-15522](https://nvd.nist.gov/vuln/detail/CVE-2020-15522) |
| CVE-2020-17521 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-17521](https://nvd.nist.gov/vuln/detail/CVE-2020-17521) |
| CVE-2020-17521 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-17521](https://nvd.nist.gov/vuln/detail/CVE-2020-17521) |
| CVE-2020-1945 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-1945](https://nvd.nist.gov/vuln/detail/CVE-2020-1945) |
| CVE-2020-26939 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-26939](https://nvd.nist.gov/vuln/detail/CVE-2020-26939) |
| CVE-2020-26939 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-26939](https://nvd.nist.gov/vuln/detail/CVE-2020-26939) |
| CVE-2020-29582 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-29582](https://nvd.nist.gov/vuln/detail/CVE-2020-29582) |
| CVE-2021-22569 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2021-22569](https://nvd.nist.gov/vuln/detail/CVE-2021-22569) |
| CVE-2021-22569 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2021-22569](https://nvd.nist.gov/vuln/detail/CVE-2021-22569) |
| CVE-2021-22570 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2021-22570](https://nvd.nist.gov/vuln/detail/CVE-2021-22570) |
| CVE-2021-22570 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2021-22570](https://nvd.nist.gov/vuln/detail/CVE-2021-22570) |
| CVE-2021-27568 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2021-27568](https://nvd.nist.gov/vuln/detail/CVE-2021-27568) |
| CVE-2021-28170 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2021-28170](https://nvd.nist.gov/vuln/detail/CVE-2021-28170) |
| CVE-2021-28170 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2021-28170](https://nvd.nist.gov/vuln/detail/CVE-2021-28170) |
| CVE-2021-28170 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2021-28170](https://nvd.nist.gov/vuln/detail/CVE-2021-28170) |
| CVE-2021-28170 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2021-28170](https://nvd.nist.gov/vuln/detail/CVE-2021-28170) |
| CVE-2021-29425 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2021-29425](https://nvd.nist.gov/vuln/detail/CVE-2021-29425) |
| CVE-2021-36373 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2021-36373](https://nvd.nist.gov/vuln/detail/CVE-2021-36373) |
| CVE-2021-36374 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2021-36374](https://nvd.nist.gov/vuln/detail/CVE-2021-36374) |
| CVE-2021-38153 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2021-38153](https://nvd.nist.gov/vuln/detail/CVE-2021-38153) |
| CVE-2022-24329 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2022-24329](https://nvd.nist.gov/vuln/detail/CVE-2022-24329) |
| CVE-2022-38749 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2022-38749](https://nvd.nist.gov/vuln/detail/CVE-2022-38749) |
| CVE-2022-38750 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2022-38750](https://nvd.nist.gov/vuln/detail/CVE-2022-38750) |
| CVE-2022-38751 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2022-38751](https://nvd.nist.gov/vuln/detail/CVE-2022-38751) |
| CVE-2022-38752 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2022-38752](https://nvd.nist.gov/vuln/detail/CVE-2022-38752) |
| CVE-2022-41854 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2022-41854](https://nvd.nist.gov/vuln/detail/CVE-2022-41854) |
| CVE-2023-0833 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-0833](https://nvd.nist.gov/vuln/detail/CVE-2023-0833) |
| CVE-2023-20863 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-20863](https://nvd.nist.gov/vuln/detail/CVE-2023-20863) |
| CVE-2023-33201 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-33201](https://nvd.nist.gov/vuln/detail/CVE-2023-33201) |
| CVE-2023-33201 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-33201](https://nvd.nist.gov/vuln/detail/CVE-2023-33201) |
| CVE-2023-33201 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-33201](https://nvd.nist.gov/vuln/detail/CVE-2023-33201) |
| CVE-2023-33201 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-33201](https://nvd.nist.gov/vuln/detail/CVE-2023-33201) |
| CVE-2023-33201 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-33201](https://nvd.nist.gov/vuln/detail/CVE-2023-33201) |
| CVE-2023-33202 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-33202](https://nvd.nist.gov/vuln/detail/CVE-2023-33202) |
| CVE-2023-33202 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-33202](https://nvd.nist.gov/vuln/detail/CVE-2023-33202) |
| CVE-2023-33202 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-33202](https://nvd.nist.gov/vuln/detail/CVE-2023-33202) |
| CVE-2023-33202 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-33202](https://nvd.nist.gov/vuln/detail/CVE-2023-33202) |
| CVE-2023-33202 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-33202](https://nvd.nist.gov/vuln/detail/CVE-2023-33202) |
| CVE-2023-42503 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-42503](https://nvd.nist.gov/vuln/detail/CVE-2023-42503) |
| CVE-2023-51074 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-51074](https://nvd.nist.gov/vuln/detail/CVE-2023-51074) |
| CVE-2023-51074 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-51074](https://nvd.nist.gov/vuln/detail/CVE-2023-51074) |
| CVE-2024-12798 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-12798](https://nvd.nist.gov/vuln/detail/CVE-2024-12798) |
| CVE-2024-12798 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-12798](https://nvd.nist.gov/vuln/detail/CVE-2024-12798) |
| CVE-2024-12798 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-12798](https://nvd.nist.gov/vuln/detail/CVE-2024-12798) |
| CVE-2024-12798 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-12798](https://nvd.nist.gov/vuln/detail/CVE-2024-12798) |
| CVE-2024-12798 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-12798](https://nvd.nist.gov/vuln/detail/CVE-2024-12798) |
| CVE-2024-12798 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-12798](https://nvd.nist.gov/vuln/detail/CVE-2024-12798) |
| CVE-2024-25710 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-25710](https://nvd.nist.gov/vuln/detail/CVE-2024-25710) |
| CVE-2024-25710 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-25710](https://nvd.nist.gov/vuln/detail/CVE-2024-25710) |
| CVE-2024-25710 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-25710](https://nvd.nist.gov/vuln/detail/CVE-2024-25710) |
| CVE-2024-26308 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-26308](https://nvd.nist.gov/vuln/detail/CVE-2024-26308) |
| CVE-2024-26308 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-26308](https://nvd.nist.gov/vuln/detail/CVE-2024-26308) |
| CVE-2024-26308 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-26308](https://nvd.nist.gov/vuln/detail/CVE-2024-26308) |
| CVE-2024-38820 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-38820](https://nvd.nist.gov/vuln/detail/CVE-2024-38820) |
| CVE-2024-38820 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-38820](https://nvd.nist.gov/vuln/detail/CVE-2024-38820) |
| CVE-2024-6763 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-6763](https://nvd.nist.gov/vuln/detail/CVE-2024-6763) |
| CVE-2024-6763 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-6763](https://nvd.nist.gov/vuln/detail/CVE-2024-6763) |
| CVE-2024-6763 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-6763](https://nvd.nist.gov/vuln/detail/CVE-2024-6763) |
| CVE-2024-6763 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-6763](https://nvd.nist.gov/vuln/detail/CVE-2024-6763) |
| CVE-2024-6763 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-6763](https://nvd.nist.gov/vuln/detail/CVE-2024-6763) |
| CVE-2024-8184 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-8184](https://nvd.nist.gov/vuln/detail/CVE-2024-8184) |
| CVE-2020-8908 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8908](https://nvd.nist.gov/vuln/detail/CVE-2020-8908) |
| CVE-2020-8908 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8908](https://nvd.nist.gov/vuln/detail/CVE-2020-8908) |
| CVE-2020-8908 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8908](https://nvd.nist.gov/vuln/detail/CVE-2020-8908) |
| CVE-2020-8908 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8908](https://nvd.nist.gov/vuln/detail/CVE-2020-8908) |
| CVE-2020-8908 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8908](https://nvd.nist.gov/vuln/detail/CVE-2020-8908) |
| CVE-2020-8908 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8908](https://nvd.nist.gov/vuln/detail/CVE-2020-8908) |
| CVE-2020-8908 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8908](https://nvd.nist.gov/vuln/detail/CVE-2020-8908) |
| CVE-2020-8908 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8908](https://nvd.nist.gov/vuln/detail/CVE-2020-8908) |
| CVE-2020-8908 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8908](https://nvd.nist.gov/vuln/detail/CVE-2020-8908) |
| CVE-2020-8908 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8908](https://nvd.nist.gov/vuln/detail/CVE-2020-8908) |
| CVE-2024-12801 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-12801](https://nvd.nist.gov/vuln/detail/CVE-2024-12801) |
| CVE-2024-12801 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-12801](https://nvd.nist.gov/vuln/detail/CVE-2024-12801) |
| CVE-2024-12801 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-12801](https://nvd.nist.gov/vuln/detail/CVE-2024-12801) |
| CVE-2024-12801 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-12801](https://nvd.nist.gov/vuln/detail/CVE-2024-12801) |
| GHSA-chfm-68vv-pvw5 | 낮음 | [https://nvd.nist.gov/vuln/detail/GHSA-chfm-68vv-pvw5](https://nvd.nist.gov/vuln/detail/GHSA-chfm-68vv-pvw5) |
| CVE-2024-23454 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-23454](https://nvd.nist.gov/vuln/detail/CVE-2024-23454) |
| CVE-2024-23944 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-23944](https://nvd.nist.gov/vuln/detail/CVE-2024-23944) |
| CVE-2024-23945 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-23945](https://nvd.nist.gov/vuln/detail/CVE-2024-23945) |
| CVE-2024-23945 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-23945](https://nvd.nist.gov/vuln/detail/CVE-2024-23945) |
| CVE-2024-23953 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-23953](https://nvd.nist.gov/vuln/detail/CVE-2024-23953) |
| CVE-2024-23953 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-23953](https://nvd.nist.gov/vuln/detail/CVE-2024-23953) |
| CVE-2024-27137 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-27137](https://nvd.nist.gov/vuln/detail/CVE-2024-27137) |
| CVE-2024-29025 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-29025](https://nvd.nist.gov/vuln/detail/CVE-2024-29025) |
| CVE-2024-29131 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-29131](https://nvd.nist.gov/vuln/detail/CVE-2024-29131) |
| CVE-2024-29133 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-29133](https://nvd.nist.gov/vuln/detail/CVE-2024-29133) |
| CVE-2024-29857 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-29857](https://nvd.nist.gov/vuln/detail/CVE-2024-29857) |
| CVE-2024-29857 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-29857](https://nvd.nist.gov/vuln/detail/CVE-2024-29857) |
| CVE-2024-29857 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-29857](https://nvd.nist.gov/vuln/detail/CVE-2024-29857) |
| CVE-2024-29857 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-29857](https://nvd.nist.gov/vuln/detail/CVE-2024-29857) |
| CVE-2024-29869 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-29869](https://nvd.nist.gov/vuln/detail/CVE-2024-29869) |
| CVE-2024-29869 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-29869](https://nvd.nist.gov/vuln/detail/CVE-2024-29869) |
| CVE-2024-30171 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-30171](https://nvd.nist.gov/vuln/detail/CVE-2024-30171) |
| CVE-2024-30171 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-30171](https://nvd.nist.gov/vuln/detail/CVE-2024-30171) |
| CVE-2024-30171 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-30171](https://nvd.nist.gov/vuln/detail/CVE-2024-30171) |
| CVE-2024-30171 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-30171](https://nvd.nist.gov/vuln/detail/CVE-2024-30171) |
| CVE-2024-30172 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-30172](https://nvd.nist.gov/vuln/detail/CVE-2024-30172) |
| CVE-2024-30172 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-30172](https://nvd.nist.gov/vuln/detail/CVE-2024-30172) |
| CVE-2024-31141 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-31141](https://nvd.nist.gov/vuln/detail/CVE-2024-31141) |
| CVE-2024-31141 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-31141](https://nvd.nist.gov/vuln/detail/CVE-2024-31141) |
| CVE-2024-34447 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-34447](https://nvd.nist.gov/vuln/detail/CVE-2024-34447) |
| CVE-2024-34447 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-34447](https://nvd.nist.gov/vuln/detail/CVE-2024-34447) |
| CVE-2024-36114 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-36114](https://nvd.nist.gov/vuln/detail/CVE-2024-36114) |
| CVE-2024-36114 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-36114](https://nvd.nist.gov/vuln/detail/CVE-2024-36114) |
| CVE-2024-36114 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-36114](https://nvd.nist.gov/vuln/detail/CVE-2024-36114) |
| CVE-2024-36114 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-36114](https://nvd.nist.gov/vuln/detail/CVE-2024-36114) |
| CVE-2024-38808 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-38808](https://nvd.nist.gov/vuln/detail/CVE-2024-38808) |
| CVE-2024-47535 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-47535](https://nvd.nist.gov/vuln/detail/CVE-2024-47535) |
| CVE-2024-47535 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-47535](https://nvd.nist.gov/vuln/detail/CVE-2024-47535) |
| CVE-2024-47535 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-47535](https://nvd.nist.gov/vuln/detail/CVE-2024-47535) |
| CVE-2024-47554 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-47554](https://nvd.nist.gov/vuln/detail/CVE-2024-47554) |
| CVE-2024-47554 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-47554](https://nvd.nist.gov/vuln/detail/CVE-2024-47554) |
| CVE-2024-47554 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-47554](https://nvd.nist.gov/vuln/detail/CVE-2024-47554) |
| CVE-2024-47554 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-47554](https://nvd.nist.gov/vuln/detail/CVE-2024-47554) |
| CVE-2024-51504 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-51504](https://nvd.nist.gov/vuln/detail/CVE-2024-51504) |
| CVE-2024-51504 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-51504](https://nvd.nist.gov/vuln/detail/CVE-2024-51504) |
| CVE-2024-56128 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-56128](https://nvd.nist.gov/vuln/detail/CVE-2024-56128) |
| CVE-2024-56128 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-56128](https://nvd.nist.gov/vuln/detail/CVE-2024-56128) |
| CVE-2024-57699 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-57699](https://nvd.nist.gov/vuln/detail/CVE-2024-57699) |
| CVE-2024-9823 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-9823](https://nvd.nist.gov/vuln/detail/CVE-2024-9823) |
| CVE-2025-23015 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-23015](https://nvd.nist.gov/vuln/detail/CVE-2025-23015) |
| CVE-2025-24860 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-24860](https://nvd.nist.gov/vuln/detail/CVE-2025-24860) |
| CVE-2025-24970 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-24970](https://nvd.nist.gov/vuln/detail/CVE-2025-24970) |
| CVE-2025-24970 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-24970](https://nvd.nist.gov/vuln/detail/CVE-2025-24970) |
| CVE-2025-24970 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-24970](https://nvd.nist.gov/vuln/detail/CVE-2025-24970) |
| CVE-2025-24970 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-24970](https://nvd.nist.gov/vuln/detail/CVE-2025-24970) |
| CVE-2025-25193 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-25193](https://nvd.nist.gov/vuln/detail/CVE-2025-25193) |
| CVE-2025-25193 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-25193](https://nvd.nist.gov/vuln/detail/CVE-2025-25193) |
| CVE-2025-25193 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-25193](https://nvd.nist.gov/vuln/detail/CVE-2025-25193) |
| CVE-2025-25193 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-25193](https://nvd.nist.gov/vuln/detail/CVE-2025-25193) |
| CVE-2025-25193 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-25193](https://nvd.nist.gov/vuln/detail/CVE-2025-25193) |
## 7.8.0 릴리스 정보
다음 릴리스 정보에는 Amazon EMR 릴리스 7.8.0에 대한 정보가 포함되어 있습니다.
**새로운 기능**
+ **애플리케이션 업그레이드** – Amazon EMR 7.8.0 application upgrades include AWS SDK for Java 2.29.52/1.12.780, Delta 3.3.0-amzn-0, Hadoop 3.4.1, Hudi 0.15.0-amzn-5, Iceberg 1.7.1-amzn-1, Spark 3.5.4, and Zookeeper 3.9.3.
**알려진 문제**
+ **EMR-EC2 SecretAgent 구성 요소를 사용한 KMS 암호화** - EMR 버전 7.8 및 7.9에서 Lake Formation 지원 클러스터에 대해 저장된 KMS 암호화를 활성화할 때 발생하는 오류가 있습니다. Lake Formation 지원 작업이 경우 *NoSuchMethodError*가 발생하면서 실패합니다. 다음의 두 가지 해결 방법을 사용할 수 있습니다.
+ 영향을 받는 클러스터에 대해 미사용 시 KMS 암호화를 일시적으로 비활성화합니다.
+ KMS 암호화를 유지해야 하는 경우 AWS Support에 문의하여 부트스트랩 작업 아티팩트를 요청합니다.
**참고**
**수정 업데이트** - 2025년 8월, 위의 문제를 해결하기 위한 업데이트가 모든 리전에 배포되었습니다. 미사용 시 KMS 암호화를 비활성화할 필요가 없습니다.
+ **Glue 카탈로그를 사용하여 HBase 테이블을 Hive에 생성** - EMR-7.3.0에서 EMR-7.10.0으로의 Hive Iceberg 통합으로 인해 버그가 발생하여 Glue Data Catalog를 메타스토어로 사용할 때 Hive에서 HBase 테이블 생성이 실패합니다. 이 문제가 발생하면 AWS 지원 팀에 문의하십시오.
+ **Tez UI** - EMR-7.3에서 EMR-7.10까지, 전송 중 암호화가 활성화된 경우 YARN Resource Manager Web UI를 통해 Tez UI에 액세스하지 못하는 버그가 있습니다. 이 문제는 Tez UI에 HTTPS가 필요한 동안 YARN 프록시가 HTTP 프로토콜을 사용하려고 시도하기 때문에 발생합니다. 이 문제를 해결하려면 `tez-site`의 `tez.tez-ui.history-url.base` 구성을 `http`에서 `https`로 수정하세요.
**변경 사항, 향상된 기능 및 해결된 문제**
+ Spark 3.3.1(EMR 버전 6.10 이상에서 지원됨)부터 폐기 호스트의 모든 실행기는 *DECOMMISSIONING* 상태라는 새로운 `ExecutorState` 상태로 설정됩니다. Yarn은 폐기 중인 실행기를 사용하여 작업을 할당할 수 없으므로 필요한 경우 실행 중인 작업에 대해 새 실행기를 요청하세요. 따라서 EMR Managed Scaling, EMR Auto Scaling 또는 EMR-EC2 클러스터의 사용자 지정 조정 메커니즘을 사용하는 동안 Spark DRA를 비활성화하면 Yarn이 각 작업에 허용되는 최대 실행기를 요청할 수 있습니다. 이 문제를 방지하려면 위의 기능 조합을 사용할 때 `spark.dynamicAllocation.enabled` 속성을 `TRUE`(기본값)로 설정한 상태로 둡니다. 또한 Spark 작업의 `spark.dynamicAllocation.maxExecutors` 및 `spark.dynamicAllocation.minExecutors` 속성 값을 설정하여 작업 실행 중에 할당된 실행기 수를 제한하여 최소 및 최대 실행기 제약 조건을 설정할 수도 있습니다.
+
[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/ko_kr/emr/latest/ReleaseGuide/emr-780-release.html)
## 7.8.0 기본 Java 버전
Amazon EMR 릴리스 7.8 이상은 Apache Livy를 제외하고 Corretto 17(OpenJDK)을 지원하는 애플리케이션에 기본적으로 Amazon Corretto 17(OpenJDK 기반)과 함께 제공됩니다.
다음 표에는 Amazon EMR 7.8.0의 애플리케이션에 대한 기본 Java 버전이 나와 있습니다. 클러스터의 기본 JVM을 변경하려면 클러스터에서 실행되는 각 애플리케이션에 대해 [특정 Java 가상 머신을 사용하도록 애플리케이션 구성](configuring-java8.md)의 지침을 따릅니다. 클러스터에서는 Java 런타임 버전 1개만 사용할 수 있습니다. Amazon EMR은 동일한 클러스터에서 다양한 런타임 버전을 사용해 서로 다른 노드 또는 애플리케이션을 실행하는 것을 지원하지 않습니다.
| 애플리케이션 | Java 및 Amazon Corretto 버전(기본값은 굵은체로 표시) |
| --- | --- |
| 델타 | 17, 11, 8 |
| Flink | 17, 11, 8 |
| HBase | 17, 11, 8 |
| HCatalog | 17, 11, 8 |
| Hadoop | 17, 11, 8 |
| Hive | 17, 11, 8 |
| Hudi | 17, 11, 8 |
| Iceberg | 17, 11 |
| Livy | 17, 11, 8 |
| Oozie | 17, 11, 8 |
| 피닉스 | 17, 11, 8 |
| PrestoDB | 8 |
| Spark | 17, 11, 8 |
| Spark RAPIDS | 17, 11, 8 |
| Tez의 Hive 실행 시간 비교 | 17, 11, 8 |
| Trino | 21, 17 |
| Zeppelin | 17, 11, 8 |
| Pig | 17, 11, 8 |
| Zookeeper | 17, 11, 8 |
## 7.8.0 구성 요소 버전
이 릴리스를 통해 Amazon EMR이 설치하는 구성 요소는 다음과 같습니다. 일부는 빅 데이터 애플리케이션 패키지의 일부로 설치됩니다. 나머지는 Amazon EMR에 고유하며 시스템 프로세스 및 기능을 위해 설치됩니다. 이는 일반적으로 `emr` 또는 `aws`로 시작됩니다. 최근 Amazon EMR 릴리스의 빅 데이터 애플리케이션 패키지는 일반적으로 커뮤니티에서 발견된 최신 버전입니다. 가능한 한 빨리 Amazon EMR에서 커뮤니티 릴리스를 제공합니다.
Amazon EMR의 일부 구성 요소는 커뮤니티 버전과 다릅니다. 이러한 구성 요소에는 `CommunityVersion-amzn-EmrVersion` 양식의 버전 레이블이 있습니다. `EmrVersion`은 0에서 시작합니다. 예를 들어, 버전 2.2의 `myapp-component`라는 오픈 소스 커뮤니티 구성 요소가 다른 Amazon EMR 릴리스에 포함되도록 세 번 수정된 경우 해당 릴리스 버전은 `2.2-amzn-2`로 나열됩니다.
| 구성 요소 | 버전 | 설명 |
| --- | --- | --- |
| adot-java-agent | 1.31.0 | 애플리케이션 대몬(daemon)에서 지표를 수집하는 Java 에이전트입니다. |
| delta | 3.3.0-amzn-0 | Delta Lake는 방대한 분석 데이터 세트를 위한 오픈 테이블 형식입니다. |
| emr-amazon-cloudwatch-agent | 1.300032.2-amzn-0 | Amazon EC2 인스턴스에서 내부 시스템 수준 지표와 사용자 지정 애플리케이션 지표를 수집하는 애플리케이션입니다. |
| emr-ddb | 5.6.0 | 하둡 에코시스템 애플리케이션용 Amazon DynamoDB 커넥터 |
| emr-goodies | 3.17.0 | 편리한 하둡 에코시스템용 추가 라이브러리 |
| emr-kinesis | 3.21.0 | 하둡 에코시스템 애플리케이션용 Amazon Kinesis 커넥터. |
| emr-notebook-env | 1.18.0 | Jupyter Enterprise Gateway가 포함된 EMR 노트북용 Conda 환경 |
| emr-s3-dist-cp | 2.38.0 | Amazon S3용으로 최적화된 분사 복사 애플리케이션. |
| emr-s3-select | 2.17.0 | EMR S3Select 커넥터 |
| emr-wal-cli | 1.3.3 | emrwal 목록/삭제에 사용되는 CLI입니다. |
| emrfs | 2.69.0 | 하둡 에코시스템 애플리케이션용 Amazon S3 커넥터. |
| flink-client | 1.20.0-amzn-2 | Apache Flink 명령줄 클라이언트 스크립트 및 애플리케이션 |
| flink-jobmanager-config | 1.20.0-amzn-2 | Apache Flink JobManager에 대한 EMR 노드에서 리소스를 관리합니다. |
| hadoop-client | 3.4.1-amzn-0 | 'hdfs', 'hadoop', 'yarn' 등과 같은 하둡 명령줄 클라이언트 |
| hadoop-hdfs-datanode | 3.4.1-amzn-0 | 블록을 저장하는 HDFS 노드 수준 서비스 |
| hadoop-hdfs-library | 3.4.1-amzn-0 | HDFS 명령줄 클라이언트 및 라이브러리 |
| hadoop-hdfs-namenode | 3.4.1-amzn-0 | 파일 이름 및 블록 위치를 추적하는 HDFS 서비스 |
| hadoop-hdfs-journalnode | 3.4.1-amzn-0 | HA 클러스터에서 하둡 파일 시스템 저널을 관리하기 위한 HDFS 서비스 |
| hadoop-httpfs-server | 3.4.1-amzn-0 | HDFS 작업에 대한 HTTP 엔드포인트 |
| hadoop-kms-server | 3.4.1-amzn-0 | 하둡의 KeyProvider API를 기반으로 하는 암호화 키 관리 서버 |
| hadoop-mapred | 3.4.1-amzn-0 | MapReduce 애플리케이션을 실행하는 MapReduce 실행 엔진 라이브러리 |
| hadoop-yarn-nodemanager | 3.4.1-amzn-0 | 개별 노드의 컨테이너를 관리하는 YARN 서비스 |
| hadoop-yarn-resourcemanager | 3.4.1-amzn-0 | 클러스터 리소스 및 분산 애플리케이션을 할당 및 관리하는 YARN 서비스 |
| hadoop-yarn-timeline-server | 3.4.1-amzn-0 | YARN 애플리케이션의 현재 및 기록 정보를 가져오는 서비스 |
| hbase-hmaster | 2.6.1-amzn-2 | 리전 조정 및 관리 명령의 실행을 담당하는 HBase 클러스터용 서비스 |
| hbase-region-server | 2.6.1-amzn-2 | 한 개 이상의 HBase 리전에 서비스를 제공하는 서비스 |
| hbase-client | 2.6.1-amzn-2 | HBase 명령줄 클라이언트 |
| hbase-rest-server | 2.6.1-amzn-2 | HBase용 RESTful HTTP 엔드포인트를 제공하는 서비스 |
| hbase-thrift-server | 2.6.1-amzn-2 | HBase에 Thrift 엔드포인트를 제공하는 서비스 |
| hbase-operator-tools | 2.6.1-amzn-2 | Apache HBase 클러스터용 복구 도구. |
| hcatalog-client | 3.1.3-amzn-17 | hcatalog-server를 조정하기 위한 'hcat' 명령줄 클라이언트 |
| hcatalog-server | 3.1.3-amzn-17 | 분산 애플리케이션용 스토리지 관리 계층, 테이블 및 HCatalog를 제공하는 서비스 |
| hcatalog-webhcat-server | 3.1.3-amzn-17 | HCatalog에 REST 인터페이스를 제공하는 HTTP 엔드포인트 |
| hive-client | 3.1.3-amzn-17 | Hive 명령줄 클라이언트 |
| hive-hbase | 3.1.3-amzn-17 | Hive-hbase 클라이언트 |
| hive-metastore-server | 3.1.3-amzn-17 | 하둡 작업에 대한 SQL용 메타데이터가 저장되는 시맨틱 리포지토리인 Hive 메타스토어에 액세스하기 위한 서비스 |
| hive-server2 | 3.1.3-amzn-17 | Hive 쿼리를 웹 요청으로 수락하기 위한 서비스 |
| hudi | 0.15.0-amzn-5 | 짧은 지연 시간 및 높은 효율성으로 데이터 파이프라인을 구동하는 증분 처리 프레임워크. |
| hudi-presto | 0.15.0-amzn-5 | Hudi로 Presto를 실행하기 위한 번들 라이브러리. |
| hudi-trino | 0.15.0-amzn-5 | Hudi와 함께 Trnio를 실행하기 위한 번들 라이브러리. |
| hudi-spark | 0.15.0-amzn-5 | Hudi와 함께 Spark를 실행하기 위한 번들 라이브러리. |
| hue-server | 4.11.0 | 하둡 에코시스템 애플리케이션을 사용하여 데이터를 분석하는 웹 애플리케이션. |
| iceberg | 1.7.1-amzn-1 | Apache Iceberg는 방대한 분석 데이터 세트를 위한 오픈 테이블 형식입니다. |
| jupyterhub | 1.5.0 | Jupyter Notebook용 다중 사용자 서버 |
| livy-server | 0.8.0-incubating | Apache Spark와 상호작용하기 위한 REST 인터페이스 |
| nginx | 1.12.1 | HTTP인 nginx [engine x] 및 역방향 프록시 서버 |
| mariadb-server | 5.5.68 이상 | MariaDB 데이터베이스 서버. |
| nvidia-cuda | 12.3.0 | Nvidia 드라이버와 Cuda 도구 키트 |
| oozie-client | 5.2.1 | Oozie 명령줄 클라이언트 |
| oozie-server | 5.2.1 | Oozie 워크플로 요청을 수락하는 서비스 |
| opencv | 4.7.0 | 오픈 소스 컴퓨터 비전 라이브러리. |
| phoenix-library | 5.2.1 | 서버 및 클라이언트의 phoenix 라이브러리 |
| phoenix-connectors | 6.0.0 | Spark-3용 Apache Phoenix 커넥터 |
| phoenix-query-server | 6.0.0 | Avatica API에 대한 JSON 형식 액세스 및 프로토콜 버퍼 액세스를 비롯하여 JDBC 액세스를 제공하는 경량 서버 |
| presto-coordinator | 0.287-amzn-2 | presto-worker의 쿼리를 수락하고 쿼리 실행을 관리하는 서비스. |
| presto-worker | 0.287-amzn-2 | 여러 쿼리를 실행하는 서비스. |
| presto-client | 0.287-amzn-2 | Presto 서버가 시작되지 않은 HA 클러스터의 대기 마스터에 설치된 Presto 명령줄 클라이언트. |
| trino-coordinator | 467-amzn-1 | trino-workers의 쿼리를 수락하고 쿼리 실행을 관리하는 서비스. |
| trino-worker | 467-amzn-1 | 여러 쿼리를 실행하는 서비스. |
| trino-client | 467-amzn-1 | Trino 서버가 시작되지 않은 HA 클러스터의 대기 마스터에 설치된 Trino 명령줄 클라이언트. |
| pig-client | 0.17.0 | Pig 명령줄 클라이언트. |
| r | 4.3.2 | 통계 컴퓨팅용 R 프로젝트 |
| ranger-kms-server | 2.0.0 | Apache Ranger 키 관리 시스템 |
| spark-client | 3.5.4-amzn-0 | Spark 명령줄 클라이언트. |
| spark-history-server | 3.5.4-amzn-0 | 완료된 Spark 애플리케이션의 수명에 대해 기록된 이벤트를 조회하는 웹 UI. |
| spark-on-yarn | 3.5.4-amzn-0 | YARN용 인 메모리 실행 엔진. |
| spark-yarn-slave | 3.5.4-amzn-0 | YARN 슬레이브에서 필요한 Apache Spark 라이브러리. |
| spark-rapids | 24.12.0-amzn-0 | GPU로 Apache Spark를 가속화하는 Nvidia Spark RAPIDS 플러그인. |
| tensorflow | 2.16.1 | TensorFlow는 고성능 수치 계산용 오픈 소스 소프트웨어 라이브러리입니다. |
| tez-on-yarn | 0.10.2-amzn-15 | tez YARN 애플리케이션 및 라이브러리. |
| tez-on-worker | 0.10.2-amzn-15 | 워커 노드에 대한 tez YARN 애플리케이션 및 라이브러리. |
| zeppelin-server | 0.11.1 | 대화형 데이터 분석이 가능한 웹 기반 노트북 |
| zookeeper-server | 3.9.3-amzn-0 | 구성 정보 유지 관리, 이름 지정, 분산 동기화 제공 및 그룹 서비스 제공을 위한 중앙 집중식 서비스. |
| zookeeper-client | 3.9.3-amzn-0 | ZooKeeper 명령줄 클라이언트. |
## 7.8.0 구성 분류
구성 분류를 사용하면 애플리케이션을 사용자 지정할 수 있습니다. 이는 종종 `hive-site.xml`과 같이 애플리케이션의 구성 XML 파일에 해당합니다. 자세한 내용은 [애플리케이션 구성](emr-configure-apps.md) 단원을 참조하십시오.
재구성 작업은 실행 중인 클러스터의 인스턴스 그룹에 대한 구성을 지정할 때 수행됩니다. Amazon EMR은 사용자가 수정한 분류에 대한 재구성 작업만 시작합니다. 자세한 내용은 [실행 중인 클러스터에서 인스턴스 그룹 재구성](emr-configure-apps-running-cluster.md) 단원을 참조하십시오.
**emr-7.8.0 분류**
| 분류 | 설명 | 재구성 작업 |
| --- | --- | --- |
| capacity-scheduler | Hadoop capacity-scheduler.xml 파일에서 값을 변경합니다. | Restarts the ResourceManager service. |
| container-executor | Hadoop YARN container-executor.cfg 파일에서 값을 변경합니다. | Not available. |
| container-log4j | Hadoop YARN container-log4j.properties 파일에서 값을 변경합니다. | Not available. |
| core-site | Hadoop core-site.xml 파일에서 값을 변경합니다. | Restarts the Hadoop HDFS services Namenode, SecondaryNamenode, Datanode, ZKFC, and Journalnode. Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts Hadoop KMS, Ranger KMS, HiveServer2, Hive MetaStore, Hadoop Httpfs, and MapReduce-HistoryServer. |
| docker-conf | Docker 관련 설정을 변경합니다. | Not available. |
| emrfs-site | EMRFS 설정을 변경합니다. | Restarts the Hadoop HDFS services Namenode, SecondaryNamenode, Datanode, ZKFC, and Journalnode. Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts HBaseRegionserver, HBaseMaster, HBaseThrift, HBaseRest, HiveServer2, Hive MetaStore, Hadoop Httpfs, and MapReduce-HistoryServer. |
| flink-conf | flink-conf.yaml 설정을 변경합니다. | Restarts Flink history server. |
| flink-log4j | Flink log4j.properties 설정을 변경합니다. | Restarts Flink history server. |
| flink-log4j-session | Kubernetes 및 Yarn 세션에 대한 Flink log4j-session.properties 설정을 변경합니다. | Restarts Flink history server. |
| flink-log4j-cli | Flink log4j-cli.properties 설정을 변경합니다. | Restarts Flink history server. |
| hadoop-env | 모든 Hadoop 구성 요소에 대한 Hadoop 환경에서 값을 변경합니다. | Restarts the Hadoop HDFS services Namenode, SecondaryNamenode, Datanode, ZKFC, and Journalnode. Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts PhoenixQueryserver, HiveServer2, Hive MetaStore, and MapReduce-HistoryServer. |
| hadoop-log4j | Hadoop log4j.properties 파일에서 값을 변경합니다. | Restarts the Hadoop HDFS services SecondaryNamenode, Datanode, and Journalnode. Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts Hadoop KMS, Hadoop Httpfs, and MapReduce-HistoryServer. |
| hadoop-ssl-server | hadoop ssl 서버 구성을 변경합니다. | Not available. |
| hadoop-ssl-client | hadoop ssl 클라이언트 구성을 변경합니다. | Not available. |
| hbase | Apache HBase에 대한 Amazon EMR 큐레이트 설정입니다. | Custom EMR specific property. Sets emrfs-site and hbase-site configs. See those for their associated restarts. |
| hbase-env | HBase 환경에서 값을 변경합니다. | Restarts the HBase services RegionServer, HBaseMaster, ThriftServer, RestServer. |
| hbase-log4j | HBase hbase-log4j.properties 파일에서 값을 변경합니다. | Restarts the HBase services RegionServer, HBaseMaster, ThriftServer, RestServer. |
| hbase-metrics | HBase hadoop-metrics2-hbase.properties 파일에서 값을 변경합니다. | Restarts the HBase services RegionServer, HBaseMaster, ThriftServer, RestServer. |
| hbase-policy | HBase hbase-policy.xml 파일에서 값을 변경합니다. | Not available. |
| hbase-site | HBase hbase-site.xml 파일에서 값을 변경합니다. | Restarts the HBase services RegionServer, HBaseMaster, ThriftServer, RestServer. Additionally restarts Phoenix QueryServer. |
| hdfs-encryption-zones | HDFS 암호화 영역을 구성합니다. | This classification should not be reconfigured. |
| hdfs-env | HDFS 환경에서 값을 변경합니다. | Restarts Hadoop HDFS services Namenode, Datanode, and ZKFC. |
| hdfs-site | HDFS hdfs-site.xml에서 값을 변경합니다. | Restarts the Hadoop HDFS services Namenode, SecondaryNamenode, Datanode, ZKFC, and Journalnode. Additionally restarts Hadoop Httpfs. |
| hcatalog-env | HCatalog 환경에서 값을 변경합니다. | Restarts Hive HCatalog Server. |
| hcatalog-server-jndi | HCatalog jndi.properties 환경에서 값을 변경합니다. | Restarts Hive HCatalog Server. |
| hcatalog-server-proto-hive-site | HCatalog proto-hive-site.xml에서 값을 변경합니다. | Restarts Hive HCatalog Server. |
| hcatalog-webhcat-env | HCatalog WebHCat 환경에서 값을 변경합니다. | Restarts Hive WebHCat server. |
| hcatalog-webhcat-log4j2 | HCatalog WebHCat log4j2.properties에서 값을 변경합니다. | Restarts Hive WebHCat server. |
| hcatalog-webhcat-site | HCatalog WebHCat webhcat-site.xml 파일에서 값을 변경합니다. | Restarts Hive WebHCat server. |
| hive | Apache Hive에 대한 Amazon EMR 큐레이트 설정입니다. | Sets configurations to launch Hive LLAP service. |
| hive-beeline-log4j2 | Hive beeline-log4j2.properties 파일에서 값을 변경합니다. | Not available. |
| hive-parquet-logging | Hive parquet-logging.properties 파일에서 값을 변경합니다. | Not available. |
| hive-env | Hive 환경에서 값을 변경합니다. | Restarts HiveServer2, HiveMetastore, and Hive HCatalog-Server. Runs Hive schemaTool CLI commands to verify hive-metastore. |
| hive-exec-log4j2 | Hive hive-exec-log4j2.properties 파일에서 값을 변경합니다. | Not available. |
| hive-llap-daemon-log4j2 | Hive llap-daemon-log4j2.properties 파일에서 값을 변경합니다. | Not available. |
| hive-log4j2 | Hive hive-log4j2.properties 파일에서 값을 변경합니다. | Not available. |
| hive-site | Hive hive-site.xml 파일에서 값을 변경합니다. | Restarts HiveServer2, HiveMetastore, and Hive HCatalog-Server. Runs Hive schemaTool CLI commands to verify hive-metastore. Also restarts Oozie and Zeppelin. |
| hiveserver2-site | Hive Server2 hiveserver2-site.xml 파일에서 값을 변경합니다. | Not available. |
| hue-ini | Hue ini 파일에서 값을 변경합니다. | Restarts Hue. Also activates Hue config override CLI commands to pick up new configurations. |
| httpfs-env | HTTPFS 환경에서 값을 변경합니다. | Restarts Hadoop Httpfs service. |
| httpfs-site | Hadoop httpfs-site.xml 파일에서 값을 변경합니다. | Restarts Hadoop Httpfs service. |
| hadoop-kms-acls | Hadoop kms-acls.xml 파일에서 값을 변경합니다. | Not available. |
| hadoop-kms-env | Hadoop KMS 환경에서 값을 변경합니다. | Restarts Hadoop-KMS service. |
| hadoop-kms-java-home | Hadoop의 KMS java 홈 변경 | Not available. |
| hadoop-kms-log4j | Hadoop kms-log4j.properties 파일에서 값을 변경합니다. | Not available. |
| hadoop-kms-site | Hadoop kms-site.xml 파일에서 값을 변경합니다. | Restarts Hadoop-KMS and Ranger-KMS service. |
| hudi-env | Hudi 환경에서 값을 변경합니다. | Not available. |
| hudi-defaults | Hudi hudi-defaults.conf 파일에서 값을 변경합니다. | Not available. |
| iceberg-defaults | Iceberg iceberg-defaults.conf 파일에서 값을 변경합니다. | Not available. |
| delta-defaults | Delta delta-defaults.conf 파일에서 값을 변경합니다. | Not available. |
| jupyter-notebook-conf | Jupyter Notebook jupyter\$1notebook\$1config.py 파일에서 값을 변경합니다. | Not available. |
| jupyter-hub-conf | JupyterHubs jupyterhub\$1config.py 파일에서 값을 변경합니다. | Not available. |
| jupyter-s3-conf | Jupyter Notebook S3 지속성 구성 | Not available. |
| jupyter-sparkmagic-conf | Sparkmagic config.json 파일에서 값을 변경합니다. | Not available. |
| livy-conf | Livy livy.conf 파일에서 값을 변경합니다. | Restarts Livy Server. |
| livy-env | Livy 환경에서 값을 변경합니다. | Restarts Livy Server. |
| livy-log4j2 | Livy log4j2.properties 설정을 변경합니다. | Restarts Livy Server. |
| mapred-env | MapReduce 애플리케이션 환경에서 값을 변경합니다. | Restarts Hadoop MapReduce-HistoryServer. |
| mapred-site | MapReduce 애플리케이션 mapred-site.xml 파일에서 값을 변경합니다. | Restarts Hadoop MapReduce-HistoryServer. |
| oozie-env | Oozie 환경에서 값을 변경합니다. | Restarts Oozie. |
| oozie-log4j | Oozie oozie-log4j.properties 파일에서 값을 변경합니다. | Restarts Oozie. |
| oozie-site | Oozie oozie-site.xml 파일에서 값을 변경합니다. | Restarts Oozie. |
| phoenix-hbase-metrics | Phoenix hadoop-metrics2-hbase.properties 파일에서 값을 변경합니다. | Not available. |
| phoenix-hbase-site | Phoenix hbase-site.xml 파일에서 값을 변경합니다. | Not available. |
| phoenix-log4j2 | Phoenix log4j2.properties 파일에서 값을 변경합니다. | Restarts Phoenix-QueryServer. |
| phoenix-metrics | Phoenix hadoop-metrics2-phoenix.properties 파일에서 값을 변경합니다. | Not available. |
| pig-env | Pig 환경에서 값을 변경합니다. | Not available. |
| pig-properties | Pig pig.properties 파일에서 값을 변경합니다. | Restarts Oozie. |
| pig-log4j | Pig log4j.properties 파일에서 값을 변경합니다. | Not available. |
| presto-log | Presto log.properties 파일에서 값을 변경합니다. | Restarts Presto-Server (for PrestoDB) |
| presto-config | Presto config.properties 파일에서 값을 변경합니다. | Restarts Presto-Server (for PrestoDB) |
| presto-password-authenticator | Presto password-authenticator.properties 파일에서 값을 변경합니다. | Not available. |
| presto-env | Presto presto-env.sh 파일에서 값을 변경합니다. | Restarts Presto-Server (for PrestoDB) |
| presto-node | Presto node.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-blackhole | Presto blackhole.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-cassandra | Presto cassandra.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-hive | Presto hive.properties 파일에서 값을 변경합니다. | Restarts Presto-Server (for PrestoDB) |
| presto-connector-jmx | Presto jmx.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-kafka | Presto kafka.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-lakeformation | Presto lakeformation.properties 파일에서 값을 변경합니다. | Restarts Presto-Server (for PrestoDB) |
| presto-connector-localfile | Presto localfile.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-memory | Presto memory.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-mongodb | Presto mongodb.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-mysql | Presto mysql.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-postgresql | Presto postgresql.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-raptor | Presto raptor.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-redis | Presto redis.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-redshift | Presto redshift.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-tpch | Presto tpch.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-tpcds | Presto tpcds.properties 파일에서 값을 변경합니다. | Not available. |
| trino-log | Trino log.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-config | Trino config.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-password-authenticator | Trino password-authenticator.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-env | Trino trino-env.sh 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-node | Trino node.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-blackhole | Trino blackhole.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-cassandra | Trino cassandra.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-delta | Trino delta.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-connector-hive | Trino hive.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-exchange-manager | Trino exchange-manager.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-connector-iceberg | Trino iceberg.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-connector-hudi | Trino hudi.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-connector-jmx | Trino jmx.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-kafka | Trino kafka.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-localfile | Trino localfile.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-memory | Trino memory.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-mongodb | Trino mongodb.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-mysql | Trino mysql.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-postgresql | Trino postgresql.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-raptor | Trino raptor.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-redis | Trino redis.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-redshift | Trino redshift.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-tpch | Trino tpch.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-tpcds | Trino tpcds.properties 파일에서 값을 변경합니다. | Not available. |
| ranger-kms-dbks-site | Ranger KMS dbks-site.xml 파일에서 값을 변경합니다. | Restarts Ranger KMS Server. |
| ranger-kms-site | Ranger KMS ranger-kms-site.xml 파일에서 값을 변경합니다. | Restarts Ranger KMS Server. |
| ranger-kms-env | Ranger KMS 환경에서 값을 변경합니다. | Restarts Ranger KMS Server. |
| ranger-kms-logback | Ranger KMS kms-logback.xml 파일에서 값을 변경합니다. | Not available. |
| ranger-kms-db-ca | Ranger KMS와의 MySQL SSL 연결에서 CA 파일의 값을 변경합니다. | Not available. |
| spark | Apache Spark에 대한 Amazon EMR 큐레이트 설정입니다. | This property modifies spark-defaults. See actions there. |
| spark-defaults | Spark spark-defaults.conf 파일에서 값을 변경합니다. | Restarts Spark history server and Spark thrift server. |
| spark-env | Spark 환경에서 값을 변경합니다. | Restarts Spark history server and Spark thrift server. |
| spark-hive-site | Spark hive-site.xml 파일에서 값을 변경합니다. | Not available. |
| spark-log4j2 | Spark log4j2.properties 파일에서 값을 변경합니다. | Restarts Spark history server and Spark thrift server. |
| spark-metrics | Spark metrics.properties 파일에서 값을 변경합니다. | Restarts Spark history server and Spark thrift server. |
| tez-site | Tez tez-site.xml 파일에서 값을 변경합니다. | Restart Oozie and HiveServer2. |
| yarn-env | YARN 환경에서 값을 변경합니다. | Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts MapReduce-HistoryServer. |
| yarn-site | YARN yarn-site.xml 파일에서 값을 변경합니다. | Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts Livy Server and MapReduce-HistoryServer. |
| zeppelin-env | Zeppelin 환경에서 값을 변경합니다. | Restarts Zeppelin. |
| zeppelin-site | zeppelin-site.xml에서 구성 설정을 변경합니다. | Restarts Zeppelin. |
| zookeeper-config | ZooKeeper zoo.cfg 파일에서 값을 변경합니다. | Restarts Zookeeper server. |
| zookeeper-logback | ZooKeeper logback.xml 파일에서 값을 변경합니다. | Restarts Zookeeper server. |
| emr-metrics | 이 노드에 대한 emr 지표 설정을 변경합니다. | Restarts the CloudWatchAgent service. |
## 7.8.0 변경 로그
**7.8.0 릴리스 및 릴리스 정보에 대한 변경 로그**
| Date | 이벤트 | 설명 |
| --- | --- | --- |
| 2025-03-07 | 문서 게시 | Amazon EMR 7.8.0 릴리스 정보 최초 게시 |
| 2025-03-06 | 배포 완료 | [지원되는 모든 리전](https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/)에 Amazon EMR 7.8.0 완전 배포 |
| 2025-02-28 | 초기 제한 릴리스 | Amazon EMR 7.8.0이 초기 상용 리전에 처음 배포됨 |
# Amazon EMR 릴리스 7.7.0
## 7.7.0 지원 수명 주기
다음 표에서는 Amazon EMR 릴리스 7.7.0에 지원되는 수명 주기 날짜를 설명합니다.
| 지원 단계 | Date |
| --- | --- |
| 초기 릴리스 날짜 | 2025년 2월 6일 |
| 표준 지원 종료 시점 | 2027년 2월 5일 |
| 지원 종료 | 2027년 2월 6일 |
| 수명 종료 | 2028년 2월 6일 |
## 7.7.0 애플리케이션 버전
이 릴리스에 포함된 애플리케이션은 [https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Install-CloudWatch-Agent.html](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Install-CloudWatch-Agent.html), [https://delta.io/](https://delta.io/), [https://flink.apache.org/](https://flink.apache.org/), [http://hbase.apache.org/](http://hbase.apache.org/), [https://cwiki.apache.org/confluence/display/Hive/HCatalog](https://cwiki.apache.org/confluence/display/Hive/HCatalog), [http://hadoop.apache.org/docs/current/](http://hadoop.apache.org/docs/current/), [http://hive.apache.org/](http://hive.apache.org/), [https://hudi.apache.org](https://hudi.apache.org), [http://gethue.com/](http://gethue.com/), [https://iceberg.apache.org/](https://iceberg.apache.org/), [https://jupyter-enterprise-gateway.readthedocs.io/en/latest/](https://jupyter-enterprise-gateway.readthedocs.io/en/latest/), [https://jupyterhub.readthedocs.io/en/latest/#](https://jupyterhub.readthedocs.io/en/latest/#), [https://livy.incubator.apache.org/](https://livy.incubator.apache.org/), [http://oozie.apache.org/](http://oozie.apache.org/), [https://phoenix.apache.org/](https://phoenix.apache.org/), [http://pig.apache.org/](http://pig.apache.org/), [https://prestodb.io/](https://prestodb.io/), [https://spark.apache.org/docs/latest/](https://spark.apache.org/docs/latest/), [https://www.tensorflow.org/](https://www.tensorflow.org/), [https://tez.apache.org/](https://tez.apache.org/), [https://trino.io/](https://trino.io/), [https://zeppelin.incubator.apache.org/](https://zeppelin.incubator.apache.org/), [https://zookeeper.apache.org](https://zookeeper.apache.org)입니다.
아래 테이블에는 이번 Amazon EMR 릴리스에서 사용할 수 있는 애플리케이션 버전과 이전 세 가지 Amazon EMR 릴리스(해당하는 경우)의 애플리케이션 버전이 나와 있습니다.
각 Amazon EMR 릴리스에서 애플리케이션 버전의 전체 기록은 다음 주제를 참조하세요.
+ [Amazon EMR 7.x 릴리스의 애플리케이션 버전](emr-release-app-versions-7.x.md)
+ [Amazon EMR 6.x 릴리스의 애플리케이션 버전](emr-release-app-versions-6.x.md)
+ [Amazon EMR 5.x 릴리스의 애플리케이션 버전](emr-release-app-versions-5.x.md)
+ [Amazon EMR 4.x 릴리스의 애플리케이션 버전](emr-release-app-versions-4.x.md)
**애플리케이션 버전 정보**
| | emr-7.7.0 | emr-7.6.0 | emr-7.5.0 | emr-7.4.0 |
| --- | --- | --- | --- | --- |
| AWS Java용 SDK | 2.29.44, 1.12.780 | 2.29.25, 1.12.779 | 2.28.8, 1.12.772 | 2.28.8, 1.12.772 |
| Python | 3.9, 3.11 | 3.9, 3.11 | 3.9, 3.11 | 3.9, 3.11 |
| Scala | 2.12.18 | 2.12.18 | 2.12.18 | 2.12.18 |
| AmazonCloudWatchAgent | 1.300032.2-amzn-0 | 1.300032.2-amzn-0 | 1.300032.2-amzn-0 | 1.300032.2-amzn-0 |
| Delta | 3.2.1-amzn-2 | 3.2.1-amzn-1 | 3.2.1-amzn-0 | 3.2.0-amzn-1 |
| Flink | 1.20.0-amzn-1 | 1.20.0-amzn-0 | 1.19.1-amzn-1 | 1.19.1-amzn-0 |
| Ganglia | - | - | - | - |
| HBase | 2.6.1-amzn-1 | 2.6.1-amzn-0 | 2.5.10-amzn-0 | 2.5.5-amzn-0 |
| HCatalog | 3.1.3-amzn-16 | 3.1.3-amzn-15 | 3.1.3-amzn-14 | 3.1.3-amzn-13 |
| Hadoop | 3.4.0-amzn-3 | 3.4.0-amzn-2 | 3.4.0-amzn-1 | 3.4.0-amzn-0 |
| Hive | 3.1.3-amzn-16 | 3.1.3-amzn-15 | 3.1.3-amzn-14 | 3.1.3-amzn-13 |
| Hudi | 0.15.0-amzn-4 | 0.15.0-amzn-3 | 0.15.0-amzn-2 | 0.15.0-amzn-1 |
| Hue | 4.11.0 | 4.11.0 | 4.11.0 | 4.11.0 |
| Iceberg | 1.7.1-amzn-0 | 1.6.1-amzn-2 | 1.6.1-amzn-1 | 1.6.1-amzn-0 |
| JupyterEnterpriseGateway | 2.6.0 | 2.6.0 | 2.6.0 | 2.6.0 |
| JupyterHub | 1.5.0 | 1.5.0 | 1.5.0 | 1.5.0 |
| Livy | 0.8.0-incubating | 0.8.0-incubating | 0.8.0-incubating | 0.8.0-incubating |
| MXNet | - | - | - | - |
| Mahout | - | - | - | - |
| Oozie | 5.2.1 | 5.2.1 | 5.2.1 | 5.2.1 |
| Phoenix | 5.2.1 | 5.2.0 | 5.2.0 | 5.2.0 |
| Pig | 0.17.0 | 0.17.0 | 0.17.0 | 0.17.0 |
| Presto | 0.287-amzn-1 | 0.287-amzn-1 | 0.287-amzn-0 | 0.287-amzn-0 |
| Spark | 3.5.3-amzn-1 | 3.5.3-amzn-0 | 3.5.2-amzn-1 | 3.5.2-amzn-0 |
| Sqoop | - | - | - | 1.4.7 |
| TensorFlow | 2.16.1 | 2.16.1 | 2.16.1 | 2.16.1 |
| Tez | 0.10.2-amzn-14 | 0.10.2-amzn-13 | 0.10.2-amzn-12 | 0.10.2-amzn-11 |
| Trino (PrestoSQL) | 467-amzn-0 | 457-amzn-0 | 446-amzn-0 | 446-amzn-0 |
| Zeppelin | 0.11.1 | 0.11.1 | 0.11.1 | 0.11.1 |
| ZooKeeper | 3.9.2-amzn-1 | 3.9.2-amzn-0 | 3.9.2-amzn-0 | 3.9.2-amzn-0 |
# 7.7.0 릴리스 구성 요소 세부 정보
Amazon EMR 7.7.0의 *추가* 패키지에 대한 자세한 내용은 다음 표를 참조하세요.
| 애플리케이션 | 애플리케이션 유형 | 패키지 | 패키지 유형 | 패키지 버전 |
| --- | --- | --- | --- | --- |
| AmazonCloudWatchAgent | Core | hadoop-hdfs-journalnode | 추가 항목 | 3.4.0-amzn-3-1.amzn2023 |
| AmazonCloudWatchAgent | Core | ranger-kms | 추가 항목 | 2.0.0-1.amzn2023 |
| AmazonCloudWatchAgent | Core | s3-dist-cp | 추가 항목 | 2.37.0-1.amzn2023 |
| AmazonCloudWatchAgent | Core | zookeeper | 추가 항목 | 3.9.2.amzn.1-1.amzn2023 |
| AmazonCloudWatchAgent | Core | zookeeper-server | 추가 항목 | 3.9.2.amzn.1-1.amzn2023 |
| Flink | Core | hadoop-client | 추가 항목 | 3.4.0.amzn.3-1.amzn2023 |
| Flink | Core | hadoop-hdfs | 추가 항목 | 3.4.0.amzn.3-1.amzn2023 |
| Flink | Core | hadoop-hdfs-datanode | 추가 항목 | 3.4.0.amzn.3-1.amzn2023 |
| Flink | Core | hadoop-hdfs-journalnode | 추가 항목 | 3.4.0.amzn.3-1.amzn2023 |
| Flink | Core | hadoop-hdfs-namenode | 추가 항목 | 3.4.0.amzn.3-1.amzn2023 |
| Flink | Core | hadoop-httpfs | 추가 항목 | 3.4.0.amzn.3-1.amzn2023 |
| Flink | Core | hadoop-kms | 추가 항목 | 3.4.0.amzn.3-1.amzn2023 |
| Flink | Core | hadoop-mapreduce | 추가 항목 | 3.4.0.amzn.3-1.amzn2023 |
| Flink | Core | hadoop-mapreduce-historyserver | 추가 항목 | 3.4.0.amzn.3-1.amzn2023 |
| Flink | Core | hadoop-yarn | 추가 항목 | 3.4.0.amzn.3-1.amzn2023 |
| Flink | Core | hadoop-yarn-nodemanager | 추가 항목 | 3.4.0.amzn.3-1.amzn2023 |
| Flink | Core | hadoop-yarn-proxyserver | 추가 항목 | 3.4.0.amzn.3-1.amzn2023 |
| Flink | Core | hadoop-yarn-resourcemanager | 추가 항목 | 3.4.0.amzn.3-1.amzn2023 |
| Flink | Core | hadoop-yarn-timelineserver | 추가 항목 | 3.4.0.amzn.3-1.amzn2023 |
| Flink | Core | hudi | 추가 항목 | 0.15.0.amzn.4-1.amzn2023 |
| Flink | Core | ranger-kms | 추가 항목 | 2.0.0-1.amzn2023 |
| Flink | Core | hadoop | 추가 항목 | 3.4.0.amzn.3-1.amzn2023 |
| HBase | Core | s3-dist-cp | 추가 항목 | 2.37.0-1.amzn2023 |
| HCatalog | Core | hadoop-yarn-proxyserver | 추가 항목 | 3.4.0.amzn.3-1.amzn2023 |
| HCatalog | Core | mariadb-connector-java | 추가 항목 | |
| Hive | Core | hadoop-httpfs | 추가 항목 | 3.4.0.amzn.3-1.amzn2023 |
| Hive | Core | hadoop-yarn-proxyserver | 추가 항목 | 3.4.0.amzn.3-1.amzn2023 |
| Hive | Core | hive-hbase | 추가 항목 | 3.1.3.amzn.16-1.amzn2023 |
| Hive | Core | mariadb-connector-java | 추가 항목 | 2.7.2-1 |
| Hive | Core | s3-dist-cp | 추가 항목 | 2.37.0-1.amzn2023 |
| 피닉스 | Core | s3-dist-cp | 추가 항목 | 2.37.0-1.amzn2023 |
| Spark | Core | spark-datanucleus | 추가 항목 | 3.5.3.amzn.1-1.amzn2023 |
| Tez의 Hive 실행 시간 비교 | Core | hadoop-mapreduce | 추가 항목 | 3.4.0.amzn.3-1.amzn2023 |
| Tez의 Hive 실행 시간 비교 | Core | hadoop-mapreduce-historyserver | 추가 항목 | 3.4.0.amzn.3-1.amzn2023 |
| Tez의 Hive 실행 시간 비교 | Core | hadoop-yarn-proxyserver | 추가 항목 | 3.4.0.amzn.3-1.amzn2023 |
| Trino | Core | bigtop-utils | 추가 항목 | 1.2.0-1.amzn2023 |
| Trino | Core | hadoop-client | 추가 항목 | 3.4.0.amzn.3-1.amzn2023 |
| Trino | Core | hadoop-hdfs | 추가 항목 | 3.4.0.amzn.3-1.amzn2023 |
| Trino | Core | hadoop-hdfs-datanode | 추가 항목 | 3.4.0.amzn.3-1.amzn2023 |
| Trino | Core | hadoop-hdfs-journalnode | 추가 항목 | 3.4.0.amzn.3-1.amzn2023 |
| Trino | Core | hadoop-hdfs-namenode | 추가 항목 | 3.4.0.amzn.3-1.amzn2023 |
| Trino | Core | hadoop-kms | 추가 항목 | 3.4.0.amzn.3-1.amzn2023 |
| Trino | Core | hadoop-mapreduce | 추가 항목 | 3.4.0.amzn.3-1.amzn2023 |
| Trino | Core | hadoop-mapreduce-historyserver | 추가 항목 | 3.4.0.amzn.3-1.amzn2023 |
| Trino | Core | hadoop-yarn | 추가 항목 | 3.4.0.amzn.3-1.amzn2023 |
| Trino | Core | hadoop-yarn-nodemanager | 추가 항목 | 3.4.0.amzn.3-1.amzn2023 |
| Trino | Core | hadoop-yarn-proxyserver | 추가 항목 | 3.4.0.amzn.3-1.amzn2023 |
| Trino | Core | hadoop-yarn-resourcemanager | 추가 항목 | 3.4.0.amzn.3-1.amzn2023 |
| Trino | Core | hadoop-yarn-timelineserver | 추가 항목 | 3.4.0.amzn.3-1.amzn2023 |
| Trino | Core | hive | 추가 항목 | 3.1.3.amzn.16-1.amzn2023 |
| Trino | Core | hive-hcatalog-server | 추가 항목 | 3.1.3.amzn.16-1.amzn2023 |
| Trino | Core | mariadb-connector-java | 추가 항목 | 2.7.2-1 |
| Trino | Core | ranger-kms | 추가 항목 | 2.0.0-1.amzn2023 |
| Trino | Core | zookeeper | 추가 항목 | 3.9.2.amzn.1-1.amzn2023 |
| Trino | Core | zookeeper-server | 추가 항목 | 3.9.2.amzn.1-1.amzn2023 |
| Trino | Core | bigtop-groovy | 추가 항목 | 2.5.4-1.amzn2023 |
| Trino | Core | bigtop-jsvc | 추가 항목 | 1.2.4-1.amzn2023 |
| Trino | Core | hadoop | 추가 항목 | 3.4.0.amzn.3-1.amzn2023 |
| Trino | Core | hadoop-lzo | 추가 항목 | 0.4.19-1.amzn2023 |
| Trino | Core | hive-hcatalog | 추가 항목 | 3.1.3.amzn.16-1.amzn2023 |
| Trino | Core | hive-jdbc | 추가 항목 | 3.1.3.amzn.16-1.amzn2023 |
| Zookeeper | Core | emrfs | 추가 항목 | 3.9.2.amzn.1-1.amzn2023 |
| Zookeeper | Core | hadoop-client | 추가 항목 | 3.9.2.amzn.1-1.amzn2023 |
| Zookeeper | Core | hadoop-hdfs | 추가 항목 | 3.9.2.amzn.1-1.amzn2023 |
| Zookeeper | Core | hadoop-hdfs-datanode | 추가 항목 | 3.9.2.amzn.1-1.amzn2023 |
| Zookeeper | Core | hadoop-hdfs-journalnode | 추가 항목 | 3.9.2.amzn.1-1.amzn2023 |
| Zookeeper | Core | hadoop-hdfs-namenode | 추가 항목 | 3.9.2.amzn.1-1.amzn2023 |
| Zookeeper | Core | hadoop-httpfs | 추가 항목 | 3.9.2.amzn.1-1.amzn2023 |
| Zookeeper | Core | hadoop-kms | 추가 항목 | 3.9.2.amzn.1-1.amzn2023 |
| Zookeeper | Core | hadoop-mapreduce | 추가 항목 | 3.4.0.amzn.3-1.amzn2023 |
| Zookeeper | Core | hadoop-mapreduce-historyserver | 추가 항목 | 3.4.0.amzn.3-1.amzn2023 |
| Zookeeper | Core | hadoop-yarn | 추가 항목 | 3.4.0.amzn.3-1.amzn2023 |
| Zookeeper | Core | hadoop-yarn-nodemanager | 추가 항목 | 3.4.0.amzn.3-1.amzn2023 |
| Zookeeper | Core | hadoop-yarn-proxyserver | 추가 항목 | 3.4.0.amzn.3-1.amzn2023 |
| Zookeeper | Core | hadoop-yarn-resourcemanager | 추가 항목 | 3.4.0.amzn.3-1.amzn2023 |
| Zookeeper | Core | hadoop-yarn-timelineserver | 추가 항목 | 3.4.0.amzn.3-1.amzn2023 |
| Zookeeper | Core | ranger-kms | 추가 항목 | 2.0.0-1.amzn2023 |
# 7.7.0 일반적인 취약성 및 노출
다음 표에는 Amazon EMR 7.7.0의 권장 구성에서 실행되는 EMR 클러스터에 영향을 주지 않는 모든 CVEs가 나열되어 있습니다. Amazon EMR은 업스트림 오픈 소스의 수정 사항 가용성에 종속되어 있으며, Amazon EMR이 수정 사항을 확인한 후 90일 이내에 코어 엔진 구성 요소의 일부로 안정적인 최신 버전을 제공합니다.
이 표는 2025년 2월 4일에 업데이트되었습니다.
| CVE ID | 심각도 | CVE 세부 정보 URL |
| --- | --- | --- |
| CVE-2015-1832 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2015-1832](https://nvd.nist.gov/vuln/detail/CVE-2015-1832) |
| CVE-2016-5018 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2016-5018](https://nvd.nist.gov/vuln/detail/CVE-2016-5018) |
| CVE-2017-15095 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2017-15095](https://nvd.nist.gov/vuln/detail/CVE-2017-15095) |
| CVE-2017-17485 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2017-17485](https://nvd.nist.gov/vuln/detail/CVE-2017-17485) |
| CVE-2017-7525 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2017-7525](https://nvd.nist.gov/vuln/detail/CVE-2017-7525) |
| CVE-2018-11307 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-11307](https://nvd.nist.gov/vuln/detail/CVE-2018-11307) |
| CVE-2018-11307 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-11307](https://nvd.nist.gov/vuln/detail/CVE-2018-11307) |
| CVE-2018-14718 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-14718](https://nvd.nist.gov/vuln/detail/CVE-2018-14718) |
| CVE-2018-14718 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-14718](https://nvd.nist.gov/vuln/detail/CVE-2018-14718) |
| CVE-2018-14719 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-14719](https://nvd.nist.gov/vuln/detail/CVE-2018-14719) |
| CVE-2018-14719 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-14719](https://nvd.nist.gov/vuln/detail/CVE-2018-14719) |
| CVE-2018-14720 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-14720](https://nvd.nist.gov/vuln/detail/CVE-2018-14720) |
| CVE-2018-14720 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-14720](https://nvd.nist.gov/vuln/detail/CVE-2018-14720) |
| CVE-2018-14721 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-14721](https://nvd.nist.gov/vuln/detail/CVE-2018-14721) |
| CVE-2018-14721 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-14721](https://nvd.nist.gov/vuln/detail/CVE-2018-14721) |
| CVE-2018-19360 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-19360](https://nvd.nist.gov/vuln/detail/CVE-2018-19360) |
| CVE-2018-19360 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-19360](https://nvd.nist.gov/vuln/detail/CVE-2018-19360) |
| CVE-2018-19361 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-19361](https://nvd.nist.gov/vuln/detail/CVE-2018-19361) |
| CVE-2018-19361 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-19361](https://nvd.nist.gov/vuln/detail/CVE-2018-19361) |
| CVE-2018-19362 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-19362](https://nvd.nist.gov/vuln/detail/CVE-2018-19362) |
| CVE-2018-19362 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-19362](https://nvd.nist.gov/vuln/detail/CVE-2018-19362) |
| CVE-2018-7489 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-7489](https://nvd.nist.gov/vuln/detail/CVE-2018-7489) |
| CVE-2018-7489 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-7489](https://nvd.nist.gov/vuln/detail/CVE-2018-7489) |
| CVE-2019-10202 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-10202](https://nvd.nist.gov/vuln/detail/CVE-2019-10202) |
| CVE-2019-14379 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14379](https://nvd.nist.gov/vuln/detail/CVE-2019-14379) |
| CVE-2019-14379 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14379](https://nvd.nist.gov/vuln/detail/CVE-2019-14379) |
| CVE-2019-14540 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14540](https://nvd.nist.gov/vuln/detail/CVE-2019-14540) |
| CVE-2019-14540 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14540](https://nvd.nist.gov/vuln/detail/CVE-2019-14540) |
| CVE-2019-14892 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14892](https://nvd.nist.gov/vuln/detail/CVE-2019-14892) |
| CVE-2019-14892 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14892](https://nvd.nist.gov/vuln/detail/CVE-2019-14892) |
| CVE-2019-14893 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14893](https://nvd.nist.gov/vuln/detail/CVE-2019-14893) |
| CVE-2019-14893 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14893](https://nvd.nist.gov/vuln/detail/CVE-2019-14893) |
| CVE-2019-16335 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-16335](https://nvd.nist.gov/vuln/detail/CVE-2019-16335) |
| CVE-2019-16335 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-16335](https://nvd.nist.gov/vuln/detail/CVE-2019-16335) |
| CVE-2019-16942 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-16942](https://nvd.nist.gov/vuln/detail/CVE-2019-16942) |
| CVE-2019-16942 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-16942](https://nvd.nist.gov/vuln/detail/CVE-2019-16942) |
| CVE-2019-16943 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-16943](https://nvd.nist.gov/vuln/detail/CVE-2019-16943) |
| CVE-2019-16943 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-16943](https://nvd.nist.gov/vuln/detail/CVE-2019-16943) |
| CVE-2019-17267 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-17267](https://nvd.nist.gov/vuln/detail/CVE-2019-17267) |
| CVE-2019-17267 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-17267](https://nvd.nist.gov/vuln/detail/CVE-2019-17267) |
| CVE-2019-17531 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-17531](https://nvd.nist.gov/vuln/detail/CVE-2019-17531) |
| CVE-2019-17531 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-17531](https://nvd.nist.gov/vuln/detail/CVE-2019-17531) |
| CVE-2019-20330 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-20330](https://nvd.nist.gov/vuln/detail/CVE-2019-20330) |
| CVE-2019-20330 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-20330](https://nvd.nist.gov/vuln/detail/CVE-2019-20330) |
| CVE-2020-8840 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8840](https://nvd.nist.gov/vuln/detail/CVE-2020-8840) |
| CVE-2020-8840 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8840](https://nvd.nist.gov/vuln/detail/CVE-2020-8840) |
| CVE-2020-9546 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-9546](https://nvd.nist.gov/vuln/detail/CVE-2020-9546) |
| CVE-2020-9546 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-9546](https://nvd.nist.gov/vuln/detail/CVE-2020-9546) |
| CVE-2020-9547 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-9547](https://nvd.nist.gov/vuln/detail/CVE-2020-9547) |
| CVE-2020-9547 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-9547](https://nvd.nist.gov/vuln/detail/CVE-2020-9547) |
| CVE-2020-9548 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-9548](https://nvd.nist.gov/vuln/detail/CVE-2020-9548) |
| CVE-2020-9548 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-9548](https://nvd.nist.gov/vuln/detail/CVE-2020-9548) |
| CVE-2022-1471 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-1471](https://nvd.nist.gov/vuln/detail/CVE-2022-1471) |
| CVE-2022-1471 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-1471](https://nvd.nist.gov/vuln/detail/CVE-2022-1471) |
| CVE-2022-37865 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-37865](https://nvd.nist.gov/vuln/detail/CVE-2022-37865) |
| CVE-2022-39135 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-39135](https://nvd.nist.gov/vuln/detail/CVE-2022-39135) |
| CVE-2022-42889 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42889](https://nvd.nist.gov/vuln/detail/CVE-2022-42889) |
| CVE-2022-46337 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-46337](https://nvd.nist.gov/vuln/detail/CVE-2022-46337) |
| CVE-2022-46337 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-46337](https://nvd.nist.gov/vuln/detail/CVE-2022-46337) |
| CVE-2023-44981 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2023-44981](https://nvd.nist.gov/vuln/detail/CVE-2023-44981) |
| CVE-2024-47561 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2024-47561](https://nvd.nist.gov/vuln/detail/CVE-2024-47561) |
| CVE-2024-47561 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2024-47561](https://nvd.nist.gov/vuln/detail/CVE-2024-47561) |
| CVE-2024-47561 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2024-47561](https://nvd.nist.gov/vuln/detail/CVE-2024-47561) |
| CVE-2024-47561 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2024-47561](https://nvd.nist.gov/vuln/detail/CVE-2024-47561) |
| CVE-2024-47561 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2024-47561](https://nvd.nist.gov/vuln/detail/CVE-2024-47561) |
| CVE-2024-47561 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2024-47561](https://nvd.nist.gov/vuln/detail/CVE-2024-47561) |
| CVE-2024-52046 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2024-52046](https://nvd.nist.gov/vuln/detail/CVE-2024-52046) |
| CVE-2024-52046 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2024-52046](https://nvd.nist.gov/vuln/detail/CVE-2024-52046) |
| CVE-2024-53990 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2024-53990](https://nvd.nist.gov/vuln/detail/CVE-2024-53990) |
| CVE-2024-53990 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2024-53990](https://nvd.nist.gov/vuln/detail/CVE-2024-53990) |
| CVE-2012-0881 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2012-0881](https://nvd.nist.gov/vuln/detail/CVE-2012-0881) |
| CVE-2013-4002 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2013-4002](https://nvd.nist.gov/vuln/detail/CVE-2013-4002) |
| CVE-2015-5237 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2015-5237](https://nvd.nist.gov/vuln/detail/CVE-2015-5237) |
| CVE-2015-5237 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2015-5237](https://nvd.nist.gov/vuln/detail/CVE-2015-5237) |
| CVE-2016-6796 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2016-6796](https://nvd.nist.gov/vuln/detail/CVE-2016-6796) |
| CVE-2018-1000180 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-1000180](https://nvd.nist.gov/vuln/detail/CVE-2018-1000180) |
| CVE-2018-12022 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-12022](https://nvd.nist.gov/vuln/detail/CVE-2018-12022) |
| CVE-2018-12022 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-12022](https://nvd.nist.gov/vuln/detail/CVE-2018-12022) |
| CVE-2018-12023 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-12023](https://nvd.nist.gov/vuln/detail/CVE-2018-12023) |
| CVE-2018-12023 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-12023](https://nvd.nist.gov/vuln/detail/CVE-2018-12023) |
| CVE-2018-5968 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-5968](https://nvd.nist.gov/vuln/detail/CVE-2018-5968) |
| CVE-2019-0205 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-0205](https://nvd.nist.gov/vuln/detail/CVE-2019-0205) |
| CVE-2019-0205 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-0205](https://nvd.nist.gov/vuln/detail/CVE-2019-0205) |
| CVE-2019-10172 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-10172](https://nvd.nist.gov/vuln/detail/CVE-2019-10172) |
| CVE-2019-12086 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-12086](https://nvd.nist.gov/vuln/detail/CVE-2019-12086) |
| CVE-2019-12086 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-12086](https://nvd.nist.gov/vuln/detail/CVE-2019-12086) |
| CVE-2019-14439 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14439](https://nvd.nist.gov/vuln/detail/CVE-2019-14439) |
| CVE-2019-14439 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14439](https://nvd.nist.gov/vuln/detail/CVE-2019-14439) |
| CVE-2020-10650 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10650](https://nvd.nist.gov/vuln/detail/CVE-2020-10650) |
| CVE-2020-10650 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10650](https://nvd.nist.gov/vuln/detail/CVE-2020-10650) |
| CVE-2020-10672 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10672](https://nvd.nist.gov/vuln/detail/CVE-2020-10672) |
| CVE-2020-10672 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10672](https://nvd.nist.gov/vuln/detail/CVE-2020-10672) |
| CVE-2020-10673 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10673](https://nvd.nist.gov/vuln/detail/CVE-2020-10673) |
| CVE-2020-10673 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10673](https://nvd.nist.gov/vuln/detail/CVE-2020-10673) |
| CVE-2020-10968 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10968](https://nvd.nist.gov/vuln/detail/CVE-2020-10968) |
| CVE-2020-10968 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10968](https://nvd.nist.gov/vuln/detail/CVE-2020-10968) |
| CVE-2020-10969 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10969](https://nvd.nist.gov/vuln/detail/CVE-2020-10969) |
| CVE-2020-10969 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10969](https://nvd.nist.gov/vuln/detail/CVE-2020-10969) |
| CVE-2020-11111 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11111](https://nvd.nist.gov/vuln/detail/CVE-2020-11111) |
| CVE-2020-11111 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11111](https://nvd.nist.gov/vuln/detail/CVE-2020-11111) |
| CVE-2020-11112 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11112](https://nvd.nist.gov/vuln/detail/CVE-2020-11112) |
| CVE-2020-11112 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11112](https://nvd.nist.gov/vuln/detail/CVE-2020-11112) |
| CVE-2020-11113 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11113](https://nvd.nist.gov/vuln/detail/CVE-2020-11113) |
| CVE-2020-11113 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11113](https://nvd.nist.gov/vuln/detail/CVE-2020-11113) |
| CVE-2020-11619 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11619](https://nvd.nist.gov/vuln/detail/CVE-2020-11619) |
| CVE-2020-11619 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11619](https://nvd.nist.gov/vuln/detail/CVE-2020-11619) |
| CVE-2020-11620 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11620](https://nvd.nist.gov/vuln/detail/CVE-2020-11620) |
| CVE-2020-11620 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11620](https://nvd.nist.gov/vuln/detail/CVE-2020-11620) |
| CVE-2020-13936 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-13936](https://nvd.nist.gov/vuln/detail/CVE-2020-13936) |
| CVE-2020-13949 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-13949](https://nvd.nist.gov/vuln/detail/CVE-2020-13949) |
| CVE-2020-13949 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-13949](https://nvd.nist.gov/vuln/detail/CVE-2020-13949) |
| CVE-2020-13949 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-13949](https://nvd.nist.gov/vuln/detail/CVE-2020-13949) |
| CVE-2020-14060 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14060](https://nvd.nist.gov/vuln/detail/CVE-2020-14060) |
| CVE-2020-14060 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14060](https://nvd.nist.gov/vuln/detail/CVE-2020-14060) |
| CVE-2020-14061 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14061](https://nvd.nist.gov/vuln/detail/CVE-2020-14061) |
| CVE-2020-14061 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14061](https://nvd.nist.gov/vuln/detail/CVE-2020-14061) |
| CVE-2020-14062 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14062](https://nvd.nist.gov/vuln/detail/CVE-2020-14062) |
| CVE-2020-14062 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14062](https://nvd.nist.gov/vuln/detail/CVE-2020-14062) |
| CVE-2020-14195 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14195](https://nvd.nist.gov/vuln/detail/CVE-2020-14195) |
| CVE-2020-14195 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14195](https://nvd.nist.gov/vuln/detail/CVE-2020-14195) |
| CVE-2020-24616 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-24616](https://nvd.nist.gov/vuln/detail/CVE-2020-24616) |
| CVE-2020-24616 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-24616](https://nvd.nist.gov/vuln/detail/CVE-2020-24616) |
| CVE-2020-24750 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-24750](https://nvd.nist.gov/vuln/detail/CVE-2020-24750) |
| CVE-2020-24750 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-24750](https://nvd.nist.gov/vuln/detail/CVE-2020-24750) |
| CVE-2020-25649 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-25649](https://nvd.nist.gov/vuln/detail/CVE-2020-25649) |
| CVE-2020-28052 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-28052](https://nvd.nist.gov/vuln/detail/CVE-2020-28052) |
| CVE-2020-35490 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-35490](https://nvd.nist.gov/vuln/detail/CVE-2020-35490) |
| CVE-2020-35490 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-35490](https://nvd.nist.gov/vuln/detail/CVE-2020-35490) |
| CVE-2020-35491 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-35491](https://nvd.nist.gov/vuln/detail/CVE-2020-35491) |
| CVE-2020-35491 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-35491](https://nvd.nist.gov/vuln/detail/CVE-2020-35491) |
| CVE-2020-35728 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-35728](https://nvd.nist.gov/vuln/detail/CVE-2020-35728) |
| CVE-2020-35728 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-35728](https://nvd.nist.gov/vuln/detail/CVE-2020-35728) |
| CVE-2020-36179 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36179](https://nvd.nist.gov/vuln/detail/CVE-2020-36179) |
| CVE-2020-36179 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36179](https://nvd.nist.gov/vuln/detail/CVE-2020-36179) |
| CVE-2020-36180 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36180](https://nvd.nist.gov/vuln/detail/CVE-2020-36180) |
| CVE-2020-36180 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36180](https://nvd.nist.gov/vuln/detail/CVE-2020-36180) |
| CVE-2020-36181 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36181](https://nvd.nist.gov/vuln/detail/CVE-2020-36181) |
| CVE-2020-36181 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36181](https://nvd.nist.gov/vuln/detail/CVE-2020-36181) |
| CVE-2020-36182 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36182](https://nvd.nist.gov/vuln/detail/CVE-2020-36182) |
| CVE-2020-36182 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36182](https://nvd.nist.gov/vuln/detail/CVE-2020-36182) |
| CVE-2020-36183 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36183](https://nvd.nist.gov/vuln/detail/CVE-2020-36183) |
| CVE-2020-36183 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36183](https://nvd.nist.gov/vuln/detail/CVE-2020-36183) |
| CVE-2020-36184 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36184](https://nvd.nist.gov/vuln/detail/CVE-2020-36184) |
| CVE-2020-36184 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36184](https://nvd.nist.gov/vuln/detail/CVE-2020-36184) |
| CVE-2020-36185 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36185](https://nvd.nist.gov/vuln/detail/CVE-2020-36185) |
| CVE-2020-36185 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36185](https://nvd.nist.gov/vuln/detail/CVE-2020-36185) |
| CVE-2020-36186 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36186](https://nvd.nist.gov/vuln/detail/CVE-2020-36186) |
| CVE-2020-36186 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36186](https://nvd.nist.gov/vuln/detail/CVE-2020-36186) |
| CVE-2020-36187 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36187](https://nvd.nist.gov/vuln/detail/CVE-2020-36187) |
| CVE-2020-36187 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36187](https://nvd.nist.gov/vuln/detail/CVE-2020-36187) |
| CVE-2020-36188 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36188](https://nvd.nist.gov/vuln/detail/CVE-2020-36188) |
| CVE-2020-36188 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36188](https://nvd.nist.gov/vuln/detail/CVE-2020-36188) |
| CVE-2020-36189 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36189](https://nvd.nist.gov/vuln/detail/CVE-2020-36189) |
| CVE-2020-36189 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36189](https://nvd.nist.gov/vuln/detail/CVE-2020-36189) |
| CVE-2020-36518 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36518](https://nvd.nist.gov/vuln/detail/CVE-2020-36518) |
| CVE-2020-36518 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36518](https://nvd.nist.gov/vuln/detail/CVE-2020-36518) |
| CVE-2021-20190 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-20190](https://nvd.nist.gov/vuln/detail/CVE-2021-20190) |
| CVE-2021-20190 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-20190](https://nvd.nist.gov/vuln/detail/CVE-2021-20190) |
| CVE-2021-31684 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-31684](https://nvd.nist.gov/vuln/detail/CVE-2021-31684) |
| CVE-2021-31684 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-31684](https://nvd.nist.gov/vuln/detail/CVE-2021-31684) |
| CVE-2021-34538 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-34538](https://nvd.nist.gov/vuln/detail/CVE-2021-34538) |
| CVE-2021-34538 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-34538](https://nvd.nist.gov/vuln/detail/CVE-2021-34538) |
| CVE-2021-34538 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-34538](https://nvd.nist.gov/vuln/detail/CVE-2021-34538) |
| CVE-2021-43859 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-43859](https://nvd.nist.gov/vuln/detail/CVE-2021-43859) |
| CVE-2022-1415 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-1415](https://nvd.nist.gov/vuln/detail/CVE-2022-1415) |
| CVE-2022-1415 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-1415](https://nvd.nist.gov/vuln/detail/CVE-2022-1415) |
| CVE-2022-25647 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-25647](https://nvd.nist.gov/vuln/detail/CVE-2022-25647) |
| CVE-2022-25647 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-25647](https://nvd.nist.gov/vuln/detail/CVE-2022-25647) |
| CVE-2022-25647 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-25647](https://nvd.nist.gov/vuln/detail/CVE-2022-25647) |
| CVE-2022-25857 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-25857](https://nvd.nist.gov/vuln/detail/CVE-2022-25857) |
| CVE-2022-3171 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3171](https://nvd.nist.gov/vuln/detail/CVE-2022-3171) |
| CVE-2022-3171 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3171](https://nvd.nist.gov/vuln/detail/CVE-2022-3171) |
| CVE-2022-3171 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3171](https://nvd.nist.gov/vuln/detail/CVE-2022-3171) |
| CVE-2022-3171 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3171](https://nvd.nist.gov/vuln/detail/CVE-2022-3171) |
| CVE-2022-3509 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3509](https://nvd.nist.gov/vuln/detail/CVE-2022-3509) |
| CVE-2022-3509 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3509](https://nvd.nist.gov/vuln/detail/CVE-2022-3509) |
| CVE-2022-3509 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3509](https://nvd.nist.gov/vuln/detail/CVE-2022-3509) |
| CVE-2022-3509 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3509](https://nvd.nist.gov/vuln/detail/CVE-2022-3509) |
| CVE-2022-3510 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3510](https://nvd.nist.gov/vuln/detail/CVE-2022-3510) |
| CVE-2022-3510 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3510](https://nvd.nist.gov/vuln/detail/CVE-2022-3510) |
| CVE-2022-3510 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3510](https://nvd.nist.gov/vuln/detail/CVE-2022-3510) |
| CVE-2022-3510 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3510](https://nvd.nist.gov/vuln/detail/CVE-2022-3510) |
| CVE-2022-36364 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-36364](https://nvd.nist.gov/vuln/detail/CVE-2022-36364) |
| CVE-2022-37866 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-37866](https://nvd.nist.gov/vuln/detail/CVE-2022-37866) |
| CVE-2022-40149 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-40149](https://nvd.nist.gov/vuln/detail/CVE-2022-40149) |
| CVE-2022-40149 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-40149](https://nvd.nist.gov/vuln/detail/CVE-2022-40149) |
| CVE-2022-40149 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-40149](https://nvd.nist.gov/vuln/detail/CVE-2022-40149) |
| CVE-2022-40150 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-40150](https://nvd.nist.gov/vuln/detail/CVE-2022-40150) |
| CVE-2022-40150 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-40150](https://nvd.nist.gov/vuln/detail/CVE-2022-40150) |
| CVE-2022-40150 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-40150](https://nvd.nist.gov/vuln/detail/CVE-2022-40150) |
| CVE-2022-40151 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-40151](https://nvd.nist.gov/vuln/detail/CVE-2022-40151) |
| CVE-2022-40152 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-40152](https://nvd.nist.gov/vuln/detail/CVE-2022-40152) |
| CVE-2022-41966 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-41966](https://nvd.nist.gov/vuln/detail/CVE-2022-41966) |
| CVE-2022-42003 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42003](https://nvd.nist.gov/vuln/detail/CVE-2022-42003) |
| CVE-2022-42003 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42003](https://nvd.nist.gov/vuln/detail/CVE-2022-42003) |
| CVE-2022-42003 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42003](https://nvd.nist.gov/vuln/detail/CVE-2022-42003) |
| CVE-2022-42003 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42003](https://nvd.nist.gov/vuln/detail/CVE-2022-42003) |
| CVE-2022-42003 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42003](https://nvd.nist.gov/vuln/detail/CVE-2022-42003) |
| CVE-2022-42003 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42003](https://nvd.nist.gov/vuln/detail/CVE-2022-42003) |
| CVE-2022-42004 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42004](https://nvd.nist.gov/vuln/detail/CVE-2022-42004) |
| CVE-2022-42004 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42004](https://nvd.nist.gov/vuln/detail/CVE-2022-42004) |
| CVE-2022-42004 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42004](https://nvd.nist.gov/vuln/detail/CVE-2022-42004) |
| CVE-2022-42004 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42004](https://nvd.nist.gov/vuln/detail/CVE-2022-42004) |
| CVE-2022-42004 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42004](https://nvd.nist.gov/vuln/detail/CVE-2022-42004) |
| CVE-2022-45685 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-45685](https://nvd.nist.gov/vuln/detail/CVE-2022-45685) |
| CVE-2022-45685 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-45685](https://nvd.nist.gov/vuln/detail/CVE-2022-45685) |
| CVE-2022-45685 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-45685](https://nvd.nist.gov/vuln/detail/CVE-2022-45685) |
| CVE-2022-45688 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-45688](https://nvd.nist.gov/vuln/detail/CVE-2022-45688) |
| CVE-2022-45693 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-45693](https://nvd.nist.gov/vuln/detail/CVE-2022-45693) |
| CVE-2022-45693 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-45693](https://nvd.nist.gov/vuln/detail/CVE-2022-45693) |
| CVE-2022-45693 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-45693](https://nvd.nist.gov/vuln/detail/CVE-2022-45693) |
| CVE-2022-46751 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-46751](https://nvd.nist.gov/vuln/detail/CVE-2022-46751) |
| CVE-2022-46751 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-46751](https://nvd.nist.gov/vuln/detail/CVE-2022-46751) |
| CVE-2023-1370 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-1370](https://nvd.nist.gov/vuln/detail/CVE-2023-1370) |
| CVE-2023-1370 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-1370](https://nvd.nist.gov/vuln/detail/CVE-2023-1370) |
| CVE-2023-1370 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-1370](https://nvd.nist.gov/vuln/detail/CVE-2023-1370) |
| CVE-2023-1436 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-1436](https://nvd.nist.gov/vuln/detail/CVE-2023-1436) |
| CVE-2023-1436 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-1436](https://nvd.nist.gov/vuln/detail/CVE-2023-1436) |
| CVE-2023-1436 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-1436](https://nvd.nist.gov/vuln/detail/CVE-2023-1436) |
| CVE-2023-20883 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-20883](https://nvd.nist.gov/vuln/detail/CVE-2023-20883) |
| CVE-2023-25194 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-25194](https://nvd.nist.gov/vuln/detail/CVE-2023-25194) |
| CVE-2023-25194 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-25194](https://nvd.nist.gov/vuln/detail/CVE-2023-25194) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-34453 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-34453](https://nvd.nist.gov/vuln/detail/CVE-2023-34453) |
| CVE-2023-34454 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-34454](https://nvd.nist.gov/vuln/detail/CVE-2023-34454) |
| CVE-2023-34455 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-34455](https://nvd.nist.gov/vuln/detail/CVE-2023-34455) |
| CVE-2023-3635 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-3635](https://nvd.nist.gov/vuln/detail/CVE-2023-3635) |
| CVE-2023-3635 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-3635](https://nvd.nist.gov/vuln/detail/CVE-2023-3635) |
| CVE-2023-36478 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-36478](https://nvd.nist.gov/vuln/detail/CVE-2023-36478) |
| CVE-2023-39410 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-39410](https://nvd.nist.gov/vuln/detail/CVE-2023-39410) |
| CVE-2023-39410 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-39410](https://nvd.nist.gov/vuln/detail/CVE-2023-39410) |
| CVE-2023-39410 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-39410](https://nvd.nist.gov/vuln/detail/CVE-2023-39410) |
| CVE-2023-39410 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-39410](https://nvd.nist.gov/vuln/detail/CVE-2023-39410) |
| CVE-2023-39410 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-39410](https://nvd.nist.gov/vuln/detail/CVE-2023-39410) |
| CVE-2023-43642 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-43642](https://nvd.nist.gov/vuln/detail/CVE-2023-43642) |
| CVE-2023-50387 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-50387](https://nvd.nist.gov/vuln/detail/CVE-2023-50387) |
| CVE-2023-5072 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-5072](https://nvd.nist.gov/vuln/detail/CVE-2023-5072) |
| CVE-2023-5072 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-5072](https://nvd.nist.gov/vuln/detail/CVE-2023-5072) |
| CVE-2023-52428 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-52428](https://nvd.nist.gov/vuln/detail/CVE-2023-52428) |
| CVE-2023-6378 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-6378](https://nvd.nist.gov/vuln/detail/CVE-2023-6378) |
| CVE-2023-6378 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-6378](https://nvd.nist.gov/vuln/detail/CVE-2023-6378) |
| CVE-2023-6481 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-6481](https://nvd.nist.gov/vuln/detail/CVE-2023-6481) |
| CVE-2023-6481 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-6481](https://nvd.nist.gov/vuln/detail/CVE-2023-6481) |
| CVE-2024-21634 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-21634](https://nvd.nist.gov/vuln/detail/CVE-2024-21634) |
| CVE-2024-35178 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-35178](https://nvd.nist.gov/vuln/detail/CVE-2024-35178) |
| CVE-2024-7254 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-7254](https://nvd.nist.gov/vuln/detail/CVE-2024-7254) |
| CVE-2024-7254 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-7254](https://nvd.nist.gov/vuln/detail/CVE-2024-7254) |
| CVE-2024-7254 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-7254](https://nvd.nist.gov/vuln/detail/CVE-2024-7254) |
| CVE-2024-7254 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-7254](https://nvd.nist.gov/vuln/detail/CVE-2024-7254) |
| CVE-2024-7254 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-7254](https://nvd.nist.gov/vuln/detail/CVE-2024-7254) |
| CVE-2024-7254 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-7254](https://nvd.nist.gov/vuln/detail/CVE-2024-7254) |
| CVE-2024-7254 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-7254](https://nvd.nist.gov/vuln/detail/CVE-2024-7254) |
| CVE-2024-7254 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-7254](https://nvd.nist.gov/vuln/detail/CVE-2024-7254) |
| CVE-2024-7254 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-7254](https://nvd.nist.gov/vuln/detail/CVE-2024-7254) |
| CVE-2009-2625 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2009-2625](https://nvd.nist.gov/vuln/detail/CVE-2009-2625) |
| CVE-2012-5783 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2012-5783](https://nvd.nist.gov/vuln/detail/CVE-2012-5783) |
| CVE-2012-6153 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2012-6153](https://nvd.nist.gov/vuln/detail/CVE-2012-6153) |
| CVE-2017-10355 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2017-10355](https://nvd.nist.gov/vuln/detail/CVE-2017-10355) |
| CVE-2018-10237 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2018-10237](https://nvd.nist.gov/vuln/detail/CVE-2018-10237) |
| CVE-2018-10237 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2018-10237](https://nvd.nist.gov/vuln/detail/CVE-2018-10237) |
| CVE-2018-10237 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2018-10237](https://nvd.nist.gov/vuln/detail/CVE-2018-10237) |
| CVE-2018-10237 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2018-10237](https://nvd.nist.gov/vuln/detail/CVE-2018-10237) |
| CVE-2018-10237 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2018-10237](https://nvd.nist.gov/vuln/detail/CVE-2018-10237) |
| CVE-2018-10237 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2018-10237](https://nvd.nist.gov/vuln/detail/CVE-2018-10237) |
| CVE-2018-11798 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2018-11798](https://nvd.nist.gov/vuln/detail/CVE-2018-11798) |
| CVE-2018-1313 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2018-1313](https://nvd.nist.gov/vuln/detail/CVE-2018-1313) |
| CVE-2018-2799 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2018-2799](https://nvd.nist.gov/vuln/detail/CVE-2018-2799) |
| CVE-2019-10219 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2019-10219](https://nvd.nist.gov/vuln/detail/CVE-2019-10219) |
| CVE-2019-12384 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2019-12384](https://nvd.nist.gov/vuln/detail/CVE-2019-12384) |
| CVE-2019-12384 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2019-12384](https://nvd.nist.gov/vuln/detail/CVE-2019-12384) |
| CVE-2019-12814 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2019-12814](https://nvd.nist.gov/vuln/detail/CVE-2019-12814) |
| CVE-2019-12814 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2019-12814](https://nvd.nist.gov/vuln/detail/CVE-2019-12814) |
| CVE-2020-10693 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10693](https://nvd.nist.gov/vuln/detail/CVE-2020-10693) |
| CVE-2020-13955 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-13955](https://nvd.nist.gov/vuln/detail/CVE-2020-13955) |
| CVE-2020-13956 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-13956](https://nvd.nist.gov/vuln/detail/CVE-2020-13956) |
| CVE-2020-13956 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-13956](https://nvd.nist.gov/vuln/detail/CVE-2020-13956) |
| CVE-2020-14338 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14338](https://nvd.nist.gov/vuln/detail/CVE-2020-14338) |
| CVE-2020-15250 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-15250](https://nvd.nist.gov/vuln/detail/CVE-2020-15250) |
| CVE-2020-15250 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-15250](https://nvd.nist.gov/vuln/detail/CVE-2020-15250) |
| CVE-2020-15522 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-15522](https://nvd.nist.gov/vuln/detail/CVE-2020-15522) |
| CVE-2020-15522 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-15522](https://nvd.nist.gov/vuln/detail/CVE-2020-15522) |
| CVE-2020-17521 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-17521](https://nvd.nist.gov/vuln/detail/CVE-2020-17521) |
| CVE-2020-17521 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-17521](https://nvd.nist.gov/vuln/detail/CVE-2020-17521) |
| CVE-2020-1945 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-1945](https://nvd.nist.gov/vuln/detail/CVE-2020-1945) |
| CVE-2020-26939 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-26939](https://nvd.nist.gov/vuln/detail/CVE-2020-26939) |
| CVE-2020-26939 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-26939](https://nvd.nist.gov/vuln/detail/CVE-2020-26939) |
| CVE-2020-29582 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-29582](https://nvd.nist.gov/vuln/detail/CVE-2020-29582) |
| CVE-2021-21290 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2021-21290](https://nvd.nist.gov/vuln/detail/CVE-2021-21290) |
| CVE-2021-22569 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2021-22569](https://nvd.nist.gov/vuln/detail/CVE-2021-22569) |
| CVE-2021-22569 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2021-22569](https://nvd.nist.gov/vuln/detail/CVE-2021-22569) |
| CVE-2021-22569 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2021-22569](https://nvd.nist.gov/vuln/detail/CVE-2021-22569) |
| CVE-2021-22569 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2021-22569](https://nvd.nist.gov/vuln/detail/CVE-2021-22569) |
| CVE-2021-22570 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2021-22570](https://nvd.nist.gov/vuln/detail/CVE-2021-22570) |
| CVE-2021-22570 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2021-22570](https://nvd.nist.gov/vuln/detail/CVE-2021-22570) |
| CVE-2021-22570 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2021-22570](https://nvd.nist.gov/vuln/detail/CVE-2021-22570) |
| CVE-2021-27568 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2021-27568](https://nvd.nist.gov/vuln/detail/CVE-2021-27568) |
| CVE-2021-28170 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2021-28170](https://nvd.nist.gov/vuln/detail/CVE-2021-28170) |
| CVE-2021-28170 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2021-28170](https://nvd.nist.gov/vuln/detail/CVE-2021-28170) |
| CVE-2021-28170 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2021-28170](https://nvd.nist.gov/vuln/detail/CVE-2021-28170) |
| CVE-2021-28170 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2021-28170](https://nvd.nist.gov/vuln/detail/CVE-2021-28170) |
| CVE-2021-29425 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2021-29425](https://nvd.nist.gov/vuln/detail/CVE-2021-29425) |
| CVE-2021-29425 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2021-29425](https://nvd.nist.gov/vuln/detail/CVE-2021-29425) |
| CVE-2021-36373 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2021-36373](https://nvd.nist.gov/vuln/detail/CVE-2021-36373) |
| CVE-2021-36374 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2021-36374](https://nvd.nist.gov/vuln/detail/CVE-2021-36374) |
| CVE-2021-37533 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2021-37533](https://nvd.nist.gov/vuln/detail/CVE-2021-37533) |
| CVE-2021-38153 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2021-38153](https://nvd.nist.gov/vuln/detail/CVE-2021-38153) |
| CVE-2022-23437 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2022-23437](https://nvd.nist.gov/vuln/detail/CVE-2022-23437) |
| CVE-2022-24329 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2022-24329](https://nvd.nist.gov/vuln/detail/CVE-2022-24329) |
| CVE-2022-38749 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2022-38749](https://nvd.nist.gov/vuln/detail/CVE-2022-38749) |
| CVE-2022-38750 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2022-38750](https://nvd.nist.gov/vuln/detail/CVE-2022-38750) |
| CVE-2022-38751 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2022-38751](https://nvd.nist.gov/vuln/detail/CVE-2022-38751) |
| CVE-2022-38752 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2022-38752](https://nvd.nist.gov/vuln/detail/CVE-2022-38752) |
| CVE-2022-41854 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2022-41854](https://nvd.nist.gov/vuln/detail/CVE-2022-41854) |
| CVE-2023-0833 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-0833](https://nvd.nist.gov/vuln/detail/CVE-2023-0833) |
| CVE-2023-20863 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-20863](https://nvd.nist.gov/vuln/detail/CVE-2023-20863) |
| CVE-2023-26048 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-26048](https://nvd.nist.gov/vuln/detail/CVE-2023-26048) |
| CVE-2023-26049 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-26049](https://nvd.nist.gov/vuln/detail/CVE-2023-26049) |
| CVE-2023-33201 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-33201](https://nvd.nist.gov/vuln/detail/CVE-2023-33201) |
| CVE-2023-33201 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-33201](https://nvd.nist.gov/vuln/detail/CVE-2023-33201) |
| CVE-2023-33201 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-33201](https://nvd.nist.gov/vuln/detail/CVE-2023-33201) |
| CVE-2023-33201 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-33201](https://nvd.nist.gov/vuln/detail/CVE-2023-33201) |
| CVE-2023-33201 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-33201](https://nvd.nist.gov/vuln/detail/CVE-2023-33201) |
| CVE-2023-33202 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-33202](https://nvd.nist.gov/vuln/detail/CVE-2023-33202) |
| CVE-2023-33202 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-33202](https://nvd.nist.gov/vuln/detail/CVE-2023-33202) |
| CVE-2023-33202 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-33202](https://nvd.nist.gov/vuln/detail/CVE-2023-33202) |
| CVE-2023-33202 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-33202](https://nvd.nist.gov/vuln/detail/CVE-2023-33202) |
| CVE-2023-33202 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-33202](https://nvd.nist.gov/vuln/detail/CVE-2023-33202) |
| CVE-2023-39968 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-39968](https://nvd.nist.gov/vuln/detail/CVE-2023-39968) |
| CVE-2023-40167 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-40167](https://nvd.nist.gov/vuln/detail/CVE-2023-40167) |
| CVE-2023-40170 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-40170](https://nvd.nist.gov/vuln/detail/CVE-2023-40170) |
| CVE-2023-42503 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-42503](https://nvd.nist.gov/vuln/detail/CVE-2023-42503) |
| CVE-2023-49080 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-49080](https://nvd.nist.gov/vuln/detail/CVE-2023-49080) |
| CVE-2023-51074 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-51074](https://nvd.nist.gov/vuln/detail/CVE-2023-51074) |
| CVE-2023-51074 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-51074](https://nvd.nist.gov/vuln/detail/CVE-2023-51074) |
| CVE-2024-12798 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-12798](https://nvd.nist.gov/vuln/detail/CVE-2024-12798) |
| CVE-2024-12798 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-12798](https://nvd.nist.gov/vuln/detail/CVE-2024-12798) |
| CVE-2024-12798 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-12798](https://nvd.nist.gov/vuln/detail/CVE-2024-12798) |
| CVE-2024-12798 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-12798](https://nvd.nist.gov/vuln/detail/CVE-2024-12798) |
| CVE-2024-12798 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-12798](https://nvd.nist.gov/vuln/detail/CVE-2024-12798) |
| CVE-2024-12798 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-12798](https://nvd.nist.gov/vuln/detail/CVE-2024-12798) |
| CVE-2024-12798 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-12798](https://nvd.nist.gov/vuln/detail/CVE-2024-12798) |
| CVE-2024-25710 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-25710](https://nvd.nist.gov/vuln/detail/CVE-2024-25710) |
| CVE-2024-25710 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-25710](https://nvd.nist.gov/vuln/detail/CVE-2024-25710) |
| CVE-2024-25710 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-25710](https://nvd.nist.gov/vuln/detail/CVE-2024-25710) |
| CVE-2024-25710 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-25710](https://nvd.nist.gov/vuln/detail/CVE-2024-25710) |
| CVE-2024-26308 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-26308](https://nvd.nist.gov/vuln/detail/CVE-2024-26308) |
| CVE-2024-26308 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-26308](https://nvd.nist.gov/vuln/detail/CVE-2024-26308) |
| CVE-2024-26308 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-26308](https://nvd.nist.gov/vuln/detail/CVE-2024-26308) |
| CVE-2024-26308 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-26308](https://nvd.nist.gov/vuln/detail/CVE-2024-26308) |
| CVE-2024-38820 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-38820](https://nvd.nist.gov/vuln/detail/CVE-2024-38820) |
| CVE-2024-38820 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-38820](https://nvd.nist.gov/vuln/detail/CVE-2024-38820) |
| CVE-2024-43805 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-43805](https://nvd.nist.gov/vuln/detail/CVE-2024-43805) |
| CVE-2024-6763 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-6763](https://nvd.nist.gov/vuln/detail/CVE-2024-6763) |
| CVE-2024-6763 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-6763](https://nvd.nist.gov/vuln/detail/CVE-2024-6763) |
| CVE-2024-6763 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-6763](https://nvd.nist.gov/vuln/detail/CVE-2024-6763) |
| CVE-2024-6763 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-6763](https://nvd.nist.gov/vuln/detail/CVE-2024-6763) |
| CVE-2024-6763 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-6763](https://nvd.nist.gov/vuln/detail/CVE-2024-6763) |
| CVE-2024-6763 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-6763](https://nvd.nist.gov/vuln/detail/CVE-2024-6763) |
| CVE-2024-8184 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-8184](https://nvd.nist.gov/vuln/detail/CVE-2024-8184) |
| CVE-2024-8184 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-8184](https://nvd.nist.gov/vuln/detail/CVE-2024-8184) |
| CVE-2020-8908 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8908](https://nvd.nist.gov/vuln/detail/CVE-2020-8908) |
| CVE-2020-8908 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8908](https://nvd.nist.gov/vuln/detail/CVE-2020-8908) |
| CVE-2020-8908 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8908](https://nvd.nist.gov/vuln/detail/CVE-2020-8908) |
| CVE-2020-8908 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8908](https://nvd.nist.gov/vuln/detail/CVE-2020-8908) |
| CVE-2020-8908 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8908](https://nvd.nist.gov/vuln/detail/CVE-2020-8908) |
| CVE-2020-8908 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8908](https://nvd.nist.gov/vuln/detail/CVE-2020-8908) |
| CVE-2020-8908 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8908](https://nvd.nist.gov/vuln/detail/CVE-2020-8908) |
| CVE-2020-8908 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8908](https://nvd.nist.gov/vuln/detail/CVE-2020-8908) |
| CVE-2020-8908 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8908](https://nvd.nist.gov/vuln/detail/CVE-2020-8908) |
| CVE-2020-8908 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8908](https://nvd.nist.gov/vuln/detail/CVE-2020-8908) |
| CVE-2020-8908 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8908](https://nvd.nist.gov/vuln/detail/CVE-2020-8908) |
| CVE-2020-8908 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8908](https://nvd.nist.gov/vuln/detail/CVE-2020-8908) |
| CVE-2022-2047 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-2047](https://nvd.nist.gov/vuln/detail/CVE-2022-2047) |
| CVE-2024-12801 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-12801](https://nvd.nist.gov/vuln/detail/CVE-2024-12801) |
| CVE-2024-12801 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-12801](https://nvd.nist.gov/vuln/detail/CVE-2024-12801) |
| CVE-2024-12801 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-12801](https://nvd.nist.gov/vuln/detail/CVE-2024-12801) |
| CVE-2024-12801 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-12801](https://nvd.nist.gov/vuln/detail/CVE-2024-12801) |
| GHSA-58qw-p7qm-5rvh | 낮음 | [https://nvd.nist.gov/vuln/detail/GHSA-58qw-p7qm-5rvh](https://nvd.nist.gov/vuln/detail/GHSA-58qw-p7qm-5rvh) |
| GHSA-chfm-68vv-pvw5 | 낮음 | [https://nvd.nist.gov/vuln/detail/GHSA-chfm-68vv-pvw5](https://nvd.nist.gov/vuln/detail/GHSA-chfm-68vv-pvw5) |
| CVE-2023-50868 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-50868](https://nvd.nist.gov/vuln/detail/CVE-2023-50868) |
| CVE-2024-23454 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-23454](https://nvd.nist.gov/vuln/detail/CVE-2024-23454) |
| CVE-2024-23454 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-23454](https://nvd.nist.gov/vuln/detail/CVE-2024-23454) |
| CVE-2024-23944 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-23944](https://nvd.nist.gov/vuln/detail/CVE-2024-23944) |
| CVE-2024-23944 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-23944](https://nvd.nist.gov/vuln/detail/CVE-2024-23944) |
| CVE-2024-23944 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-23944](https://nvd.nist.gov/vuln/detail/CVE-2024-23944) |
| CVE-2024-23945 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-23945](https://nvd.nist.gov/vuln/detail/CVE-2024-23945) |
| CVE-2024-23953 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-23953](https://nvd.nist.gov/vuln/detail/CVE-2024-23953) |
| CVE-2024-25638 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-25638](https://nvd.nist.gov/vuln/detail/CVE-2024-25638) |
| CVE-2024-27137 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-27137](https://nvd.nist.gov/vuln/detail/CVE-2024-27137) |
| CVE-2024-29025 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-29025](https://nvd.nist.gov/vuln/detail/CVE-2024-29025) |
| CVE-2024-29131 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-29131](https://nvd.nist.gov/vuln/detail/CVE-2024-29131) |
| CVE-2024-29131 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-29131](https://nvd.nist.gov/vuln/detail/CVE-2024-29131) |
| CVE-2024-29133 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-29133](https://nvd.nist.gov/vuln/detail/CVE-2024-29133) |
| CVE-2024-29133 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-29133](https://nvd.nist.gov/vuln/detail/CVE-2024-29133) |
| CVE-2024-29857 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-29857](https://nvd.nist.gov/vuln/detail/CVE-2024-29857) |
| CVE-2024-29857 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-29857](https://nvd.nist.gov/vuln/detail/CVE-2024-29857) |
| CVE-2024-29857 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-29857](https://nvd.nist.gov/vuln/detail/CVE-2024-29857) |
| CVE-2024-29857 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-29857](https://nvd.nist.gov/vuln/detail/CVE-2024-29857) |
| CVE-2024-29869 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-29869](https://nvd.nist.gov/vuln/detail/CVE-2024-29869) |
| CVE-2024-30171 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-30171](https://nvd.nist.gov/vuln/detail/CVE-2024-30171) |
| CVE-2024-30171 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-30171](https://nvd.nist.gov/vuln/detail/CVE-2024-30171) |
| CVE-2024-30171 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-30171](https://nvd.nist.gov/vuln/detail/CVE-2024-30171) |
| CVE-2024-30171 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-30171](https://nvd.nist.gov/vuln/detail/CVE-2024-30171) |
| CVE-2024-30172 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-30172](https://nvd.nist.gov/vuln/detail/CVE-2024-30172) |
| CVE-2024-30172 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-30172](https://nvd.nist.gov/vuln/detail/CVE-2024-30172) |
| CVE-2024-31141 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-31141](https://nvd.nist.gov/vuln/detail/CVE-2024-31141) |
| CVE-2024-31141 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-31141](https://nvd.nist.gov/vuln/detail/CVE-2024-31141) |
| CVE-2024-34447 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-34447](https://nvd.nist.gov/vuln/detail/CVE-2024-34447) |
| CVE-2024-34447 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-34447](https://nvd.nist.gov/vuln/detail/CVE-2024-34447) |
| CVE-2024-36114 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-36114](https://nvd.nist.gov/vuln/detail/CVE-2024-36114) |
| CVE-2024-36114 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-36114](https://nvd.nist.gov/vuln/detail/CVE-2024-36114) |
| CVE-2024-36114 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-36114](https://nvd.nist.gov/vuln/detail/CVE-2024-36114) |
| CVE-2024-36114 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-36114](https://nvd.nist.gov/vuln/detail/CVE-2024-36114) |
| CVE-2024-38808 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-38808](https://nvd.nist.gov/vuln/detail/CVE-2024-38808) |
| CVE-2024-43382 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-43382](https://nvd.nist.gov/vuln/detail/CVE-2024-43382) |
| CVE-2024-47072 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-47072](https://nvd.nist.gov/vuln/detail/CVE-2024-47072) |
| CVE-2024-47535 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-47535](https://nvd.nist.gov/vuln/detail/CVE-2024-47535) |
| CVE-2024-47535 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-47535](https://nvd.nist.gov/vuln/detail/CVE-2024-47535) |
| CVE-2024-47535 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-47535](https://nvd.nist.gov/vuln/detail/CVE-2024-47535) |
| CVE-2024-47535 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-47535](https://nvd.nist.gov/vuln/detail/CVE-2024-47535) |
| CVE-2024-47554 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-47554](https://nvd.nist.gov/vuln/detail/CVE-2024-47554) |
| CVE-2024-47554 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-47554](https://nvd.nist.gov/vuln/detail/CVE-2024-47554) |
| CVE-2024-47554 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-47554](https://nvd.nist.gov/vuln/detail/CVE-2024-47554) |
| CVE-2024-47554 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-47554](https://nvd.nist.gov/vuln/detail/CVE-2024-47554) |
| CVE-2024-47554 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-47554](https://nvd.nist.gov/vuln/detail/CVE-2024-47554) |
| CVE-2024-47554 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-47554](https://nvd.nist.gov/vuln/detail/CVE-2024-47554) |
| CVE-2024-51504 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-51504](https://nvd.nist.gov/vuln/detail/CVE-2024-51504) |
| CVE-2024-51504 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-51504](https://nvd.nist.gov/vuln/detail/CVE-2024-51504) |
| CVE-2024-51504 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-51504](https://nvd.nist.gov/vuln/detail/CVE-2024-51504) |
| CVE-2024-56128 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-56128](https://nvd.nist.gov/vuln/detail/CVE-2024-56128) |
| CVE-2024-56128 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-56128](https://nvd.nist.gov/vuln/detail/CVE-2024-56128) |
| CVE-2024-9823 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-9823](https://nvd.nist.gov/vuln/detail/CVE-2024-9823) |
| CVE-2025-23015 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-23015](https://nvd.nist.gov/vuln/detail/CVE-2025-23015) |
| CVE-2025-24789 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-24789](https://nvd.nist.gov/vuln/detail/CVE-2025-24789) |
| CVE-2025-24790 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-24790](https://nvd.nist.gov/vuln/detail/CVE-2025-24790) |
| CVE-2025-24860 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2025-24860](https://nvd.nist.gov/vuln/detail/CVE-2025-24860) |
## 7.7.0 릴리스 정보
다음 릴리스 정보에는 Amazon EMR 릴리스 7.7.0에 대한 정보가 포함되어 있습니다.
**새로운 기능**
+ **애플리케이션 업그레이드** – Amazon EMR 7.7.0 application upgrades include Delta 3.2.1-amzn-2, Hudi 0.15.0-amzn-4, Iceberg 1.7.1-amzn-0, and Trino 467.
**알려진 문제**
+ **Glue 카탈로그를 사용하여 HBase 테이블을 Hive에 생성** - EMR-7.3.0에서 EMR-7.10.0으로의 Hive Iceberg 통합으로 인해 버그가 발생하여 Glue Data Catalog를 메타스토어로 사용할 때 Hive에서 HBase 테이블 생성이 실패합니다. 이 문제가 발생하면 AWS 지원 팀에 문의하십시오.
+ **Tez UI** - EMR-7.3에서 EMR-7.10까지, 전송 중 암호화가 활성화된 경우 YARN Resource Manager Web UI를 통해 Tez UI에 액세스하지 못하는 버그가 있습니다. 이 문제는 Tez UI에 HTTPS가 필요한 동안 YARN 프록시가 HTTP 프로토콜을 사용하려고 시도하기 때문에 발생합니다. 이 문제를 해결하려면 `tez-site`의 `tez.tez-ui.history-url.base` 구성을 `http`에서 `https`로 수정하세요.
**변경 사항, 향상된 기능 및 해결된 문제**
+ Spark 3.3.1(EMR 버전 6.10 이상에서 지원됨)부터 폐기 호스트의 모든 실행기는 *DECOMMISSIONING* 상태라는 새로운 `ExecutorState` 상태로 설정됩니다. Yarn은 폐기 중인 실행기를 사용하여 작업을 할당할 수 없으므로 필요한 경우 실행 중인 작업에 대해 새 실행기를 요청하세요. 따라서 EMR Managed Scaling, EMR Auto Scaling 또는 EMR-EC2 클러스터의 사용자 지정 조정 메커니즘을 사용하는 동안 Spark DRA를 비활성화하면 Yarn이 각 작업에 허용되는 최대 실행기를 요청할 수 있습니다. 이 문제를 방지하려면 위의 기능 조합을 사용할 때 `spark.dynamicAllocation.enabled` 속성을 `TRUE`(기본값)로 설정한 상태로 둡니다. 또한 Spark 작업의 `spark.dynamicAllocation.maxExecutors` 및 `spark.dynamicAllocation.minExecutors` 속성 값을 설정하여 작업 실행 중에 할당된 실행기 수를 제한하여 최소 및 최대 실행기 제약 조건을 설정할 수도 있습니다.
+ EMR 7.7.0부터 사용 중인 Iceberg 버전이 더 이상 Java 8을 지원하지 않습니다. 또한 Iceberg는 Java 8 이미지 `emr-7.7.0-java8-latest` 및 `emr-7.7.0-spark-rapids-java8-latest`에서 제외됩니다.
+ Amazon EMR on EKS를 사용한 FGAC용 Lake Formation - Amazon EMR 릴리스 7.7 이상에서는 AWS Lake Formation을 활용하여 Amazon S3에서 지원하는 데이터 카탈로그 테이블에 세분화된 액세스 제어를 적용할 수 있습니다. 이 기능을 통해 Amazon EKS Spark 작업 내 Amazon EMR에서 읽기 쿼리에 대한 테이블, 행, 열 및 셀 수준의 액세스 제어를 구성할 수 있습니다. 자세한 내용은 [세분화된 액세스 제어를 위해 AWS Lake Formation에서 Amazon EMR on EKS 사용을](https://docs.aws.amazon.com/emr/latest/EMR-on-EKS-DevelopmentGuide/security_iam_fgac-lf.html) 참조하세요.
+
[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/ko_kr/emr/latest/ReleaseGuide/emr-770-release.html)
## 7.7.0 기본 Java 버전
Amazon EMR 릴리스 7.7 이상은 Apache Livy를 제외하고 Corretto 17(OpenJDK)을 지원하는 애플리케이션에 기본적으로 Amazon Corretto 17(OpenJDK 기반)과 함께 제공됩니다.
다음 표에는 Amazon EMR 7.7.0의 애플리케이션에 대한 기본 Java 버전이 나와 있습니다. 클러스터의 기본 JVM을 변경하려면 클러스터에서 실행되는 각 애플리케이션에 대해 [특정 Java 가상 머신을 사용하도록 애플리케이션 구성](configuring-java8.md)의 지침을 따릅니다. 클러스터에서는 Java 런타임 버전 1개만 사용할 수 있습니다. Amazon EMR은 동일한 클러스터에서 다양한 런타임 버전을 사용해 서로 다른 노드 또는 애플리케이션을 실행하는 것을 지원하지 않습니다.
| 애플리케이션 | Java 및 Amazon Corretto 버전(기본값은 굵은체로 표시) |
| --- | --- |
| 델타 | 17, 11, 8 |
| Flink | 17, 11, 8 |
| HBase | 17, 11, 8 |
| HCatalog | 17, 11, 8 |
| Hadoop | 17, 11, 8 |
| Hive | 17, 11, 8 |
| Hudi | 17, 11, 8 |
| Iceberg | 17, 11 |
| Livy | 17, 11, 8 |
| Oozie | 17, 11, 8 |
| 피닉스 | 17, 11, 8 |
| PrestoDB | 8 |
| Spark | 17, 11, 8 |
| Spark RAPIDS | 17, 11, 8 |
| Tez의 Hive 실행 시간 비교 | 17, 11, 8 |
| Trino | 21, 17 |
| Zeppelin | 17, 11, 8 |
| Pig | 17, 11, 8 |
| Zookeeper | 17, 11, 8 |
## 7.7.0 구성 요소 버전
이 릴리스를 통해 Amazon EMR이 설치하는 구성 요소는 다음과 같습니다. 일부는 빅 데이터 애플리케이션 패키지의 일부로 설치됩니다. 나머지는 Amazon EMR에 고유하며 시스템 프로세스 및 기능을 위해 설치됩니다. 이는 일반적으로 `emr` 또는 `aws`로 시작됩니다. 최근 Amazon EMR 릴리스의 빅 데이터 애플리케이션 패키지는 일반적으로 커뮤니티에서 발견된 최신 버전입니다. 가능한 한 빨리 Amazon EMR에서 커뮤니티 릴리스를 제공합니다.
Amazon EMR의 일부 구성 요소는 커뮤니티 버전과 다릅니다. 이러한 구성 요소에는 `CommunityVersion-amzn-EmrVersion` 양식의 버전 레이블이 있습니다. `EmrVersion`은 0에서 시작합니다. 예를 들어, 버전 2.2의 `myapp-component`라는 오픈 소스 커뮤니티 구성 요소가 다른 Amazon EMR 릴리스에 포함되도록 세 번 수정된 경우 해당 릴리스 버전은 `2.2-amzn-2`로 나열됩니다.
| 구성 요소 | 버전 | 설명 |
| --- | --- | --- |
| adot-java-agent | 1.31.0 | 애플리케이션 대몬(daemon)에서 지표를 수집하는 Java 에이전트입니다. |
| delta | 3.2.1-amzn-2 | Delta Lake는 방대한 분석 데이터 세트를 위한 오픈 테이블 형식입니다. |
| emr-amazon-cloudwatch-agent | 1.300032.2-amzn-0 | Amazon EC2 인스턴스에서 내부 시스템 수준 지표와 사용자 지정 애플리케이션 지표를 수집하는 애플리케이션입니다. |
| emr-ddb | 5.6.0 | 하둡 에코시스템 애플리케이션용 Amazon DynamoDB 커넥터 |
| emr-goodies | 3.16.0 | 편리한 하둡 에코시스템용 추가 라이브러리 |
| emr-kinesis | 3.20.0 | 하둡 에코시스템 애플리케이션용 Amazon Kinesis 커넥터. |
| emr-notebook-env | 1.18.0 | Jupyter Enterprise Gateway가 포함된 EMR 노트북용 Conda 환경 |
| emr-s3-dist-cp | 2.37.0 | Amazon S3용으로 최적화된 분사 복사 애플리케이션. |
| emr-s3-select | 2.16.0 | EMR S3Select 커넥터 |
| emr-wal-cli | 1.3.2 | emrwal 목록/삭제에 사용되는 CLI입니다. |
| emrfs | 2.68.0 | 하둡 에코시스템 애플리케이션용 Amazon S3 커넥터. |
| flink-client | 1.20.0-amzn-1 | Apache Flink 명령줄 클라이언트 스크립트 및 애플리케이션 |
| flink-jobmanager-config | 1.20.0-amzn-1 | Apache Flink JobManager에 대한 EMR 노드에서 리소스를 관리합니다. |
| hadoop-client | 3.4.0-amzn-3 | 'hdfs', 'hadoop', 'yarn' 등과 같은 하둡 명령줄 클라이언트 |
| hadoop-hdfs-datanode | 3.4.0-amzn-3 | 블록을 저장하는 HDFS 노드 수준 서비스 |
| hadoop-hdfs-library | 3.4.0-amzn-3 | HDFS 명령줄 클라이언트 및 라이브러리 |
| hadoop-hdfs-namenode | 3.4.0-amzn-3 | 파일 이름 및 블록 위치를 추적하는 HDFS 서비스 |
| hadoop-hdfs-journalnode | 3.4.0-amzn-3 | HA 클러스터에서 하둡 파일 시스템 저널을 관리하기 위한 HDFS 서비스 |
| hadoop-httpfs-server | 3.4.0-amzn-3 | HDFS 작업에 대한 HTTP 엔드포인트 |
| hadoop-kms-server | 3.4.0-amzn-3 | 하둡의 KeyProvider API를 기반으로 하는 암호화 키 관리 서버 |
| hadoop-mapred | 3.4.0-amzn-3 | MapReduce 애플리케이션을 실행하는 MapReduce 실행 엔진 라이브러리 |
| hadoop-yarn-nodemanager | 3.4.0-amzn-3 | 개별 노드의 컨테이너를 관리하는 YARN 서비스 |
| hadoop-yarn-resourcemanager | 3.4.0-amzn-3 | 클러스터 리소스 및 분산 애플리케이션을 할당 및 관리하는 YARN 서비스 |
| hadoop-yarn-timeline-server | 3.4.0-amzn-3 | YARN 애플리케이션의 현재 및 기록 정보를 가져오는 서비스 |
| hbase-hmaster | 2.6.1-amzn-1 | 리전 조정 및 관리 명령의 실행을 담당하는 HBase 클러스터용 서비스 |
| hbase-region-server | 2.6.1-amzn-1 | 한 개 이상의 HBase 리전에 서비스를 제공하는 서비스 |
| hbase-client | 2.6.1-amzn-1 | HBase 명령줄 클라이언트 |
| hbase-rest-server | 2.6.1-amzn-1 | HBase용 RESTful HTTP 엔드포인트를 제공하는 서비스 |
| hbase-thrift-server | 2.6.1-amzn-1 | HBase에 Thrift 엔드포인트를 제공하는 서비스 |
| hbase-operator-tools | 2.6.1-amzn-1 | Apache HBase 클러스터용 복구 도구. |
| hcatalog-client | 3.1.3-amzn-16 | hcatalog-server를 조정하기 위한 'hcat' 명령줄 클라이언트 |
| hcatalog-server | 3.1.3-amzn-16 | 분산 애플리케이션용 스토리지 관리 계층, 테이블 및 HCatalog를 제공하는 서비스 |
| hcatalog-webhcat-server | 3.1.3-amzn-16 | HCatalog에 REST 인터페이스를 제공하는 HTTP 엔드포인트 |
| hive-client | 3.1.3-amzn-16 | Hive 명령줄 클라이언트 |
| hive-hbase | 3.1.3-amzn-16 | Hive-hbase 클라이언트 |
| hive-metastore-server | 3.1.3-amzn-16 | 하둡 작업에 대한 SQL용 메타데이터가 저장되는 시맨틱 리포지토리인 Hive 메타스토어에 액세스하기 위한 서비스 |
| hive-server2 | 3.1.3-amzn-16 | Hive 쿼리를 웹 요청으로 수락하기 위한 서비스 |
| hudi | 0.15.0-amzn-4 | 짧은 지연 시간 및 높은 효율성으로 데이터 파이프라인을 구동하는 증분 처리 프레임워크. |
| hudi-presto | 0.15.0-amzn-4 | Hudi로 Presto를 실행하기 위한 번들 라이브러리. |
| hudi-trino | 0.15.0-amzn-4 | Hudi와 함께 Trnio를 실행하기 위한 번들 라이브러리. |
| hudi-spark | 0.15.0-amzn-4 | Hudi와 함께 Spark를 실행하기 위한 번들 라이브러리. |
| hue-server | 4.11.0 | 하둡 에코시스템 애플리케이션을 사용하여 데이터를 분석하는 웹 애플리케이션. |
| iceberg | 1.7.1-amzn-0 | Apache Iceberg는 방대한 분석 데이터 세트를 위한 오픈 테이블 형식입니다. |
| jupyterhub | 1.5.0 | Jupyter Notebook용 다중 사용자 서버 |
| livy-server | 0.8.0-incubating | Apache Spark와 상호작용하기 위한 REST 인터페이스 |
| nginx | 1.12.1 | HTTP인 nginx [engine x] 및 역방향 프록시 서버 |
| mariadb-server | 5.5.68 이상 | MariaDB 데이터베이스 서버. |
| nvidia-cuda | 12.3.0 | Nvidia 드라이버와 Cuda 도구 키트 |
| oozie-client | 5.2.1 | Oozie 명령줄 클라이언트 |
| oozie-server | 5.2.1 | Oozie 워크플로 요청을 수락하는 서비스 |
| opencv | 4.7.0 | 오픈 소스 컴퓨터 비전 라이브러리. |
| phoenix-library | 5.2.1 | 서버 및 클라이언트의 phoenix 라이브러리 |
| phoenix-connectors | 6.0.0 | Spark-3용 Apache Phoenix 커넥터 |
| phoenix-query-server | 6.0.0 | Avatica API에 대한 JSON 형식 액세스 및 프로토콜 버퍼 액세스를 비롯하여 JDBC 액세스를 제공하는 경량 서버 |
| presto-coordinator | 0.287-amzn-1 | presto-worker의 쿼리를 수락하고 쿼리 실행을 관리하는 서비스. |
| presto-worker | 0.287-amzn-1 | 여러 쿼리를 실행하는 서비스. |
| presto-client | 0.287-amzn-1 | Presto 서버가 시작되지 않은 HA 클러스터의 대기 마스터에 설치된 Presto 명령줄 클라이언트. |
| trino-coordinator | 467-amzn-0 | trino-workers의 쿼리를 수락하고 쿼리 실행을 관리하는 서비스. |
| trino-worker | 467-amzn-0 | 여러 쿼리를 실행하는 서비스. |
| trino-client | 467-amzn-0 | Trino 서버가 시작되지 않은 HA 클러스터의 대기 마스터에 설치된 Trino 명령줄 클라이언트. |
| pig-client | 0.17.0 | Pig 명령줄 클라이언트. |
| r | 4.3.2 | 통계 컴퓨팅용 R 프로젝트 |
| ranger-kms-server | 2.0.0 | Apache Ranger 키 관리 시스템 |
| spark-client | 3.5.3-amzn-1 | Spark 명령줄 클라이언트. |
| spark-history-server | 3.5.3-amzn-1 | 완료된 Spark 애플리케이션의 수명에 대해 기록된 이벤트를 조회하는 웹 UI. |
| spark-on-yarn | 3.5.3-amzn-1 | YARN용 인 메모리 실행 엔진. |
| spark-yarn-slave | 3.5.3-amzn-1 | YARN 슬레이브에서 필요한 Apache Spark 라이브러리. |
| spark-rapids | 24.10.1-amzn-1 | GPU로 Apache Spark를 가속화하는 Nvidia Spark RAPIDS 플러그인. |
| tensorflow | 2.16.1 | TensorFlow는 고성능 수치 계산용 오픈 소스 소프트웨어 라이브러리입니다. |
| tez-on-yarn | 0.10.2-amzn-14 | tez YARN 애플리케이션 및 라이브러리. |
| tez-on-worker | 0.10.2-amzn-14 | 워커 노드에 대한 tez YARN 애플리케이션 및 라이브러리. |
| zeppelin-server | 0.11.1 | 대화형 데이터 분석이 가능한 웹 기반 노트북 |
| zookeeper-server | 3.9.2-amzn-1 | 구성 정보 유지 관리, 이름 지정, 분산 동기화 제공 및 그룹 서비스 제공을 위한 중앙 집중식 서비스. |
| zookeeper-client | 3.9.2-amzn-1 | ZooKeeper 명령줄 클라이언트. |
## 7.7.0 구성 분류
구성 분류를 사용하면 애플리케이션을 사용자 지정할 수 있습니다. 이는 종종 `hive-site.xml`과 같이 애플리케이션의 구성 XML 파일에 해당합니다. 자세한 내용은 [애플리케이션 구성](emr-configure-apps.md) 단원을 참조하십시오.
재구성 작업은 실행 중인 클러스터의 인스턴스 그룹에 대한 구성을 지정할 때 수행됩니다. Amazon EMR은 사용자가 수정한 분류에 대한 재구성 작업만 시작합니다. 자세한 내용은 [실행 중인 클러스터에서 인스턴스 그룹 재구성](emr-configure-apps-running-cluster.md) 단원을 참조하십시오.
**emr-7.7.0 분류**
| 분류 | 설명 | 재구성 작업 |
| --- | --- | --- |
| capacity-scheduler | Hadoop capacity-scheduler.xml 파일에서 값을 변경합니다. | Restarts the ResourceManager service. |
| container-executor | Hadoop YARN container-executor.cfg 파일에서 값을 변경합니다. | Not available. |
| container-log4j | Hadoop YARN container-log4j.properties 파일에서 값을 변경합니다. | Not available. |
| core-site | Hadoop core-site.xml 파일에서 값을 변경합니다. | Restarts the Hadoop HDFS services Namenode, SecondaryNamenode, Datanode, ZKFC, and Journalnode. Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts Hadoop KMS, Ranger KMS, HiveServer2, Hive MetaStore, Hadoop Httpfs, and MapReduce-HistoryServer. |
| docker-conf | Docker 관련 설정을 변경합니다. | Not available. |
| emrfs-site | EMRFS 설정을 변경합니다. | Restarts the Hadoop HDFS services Namenode, SecondaryNamenode, Datanode, ZKFC, and Journalnode. Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts HBaseRegionserver, HBaseMaster, HBaseThrift, HBaseRest, HiveServer2, Hive MetaStore, Hadoop Httpfs, and MapReduce-HistoryServer. |
| flink-conf | flink-conf.yaml 설정을 변경합니다. | Restarts Flink history server. |
| flink-log4j | Flink log4j.properties 설정을 변경합니다. | Restarts Flink history server. |
| flink-log4j-session | Kubernetes 및 Yarn 세션에 대한 Flink log4j-session.properties 설정을 변경합니다. | Restarts Flink history server. |
| flink-log4j-cli | Flink log4j-cli.properties 설정을 변경합니다. | Restarts Flink history server. |
| hadoop-env | 모든 Hadoop 구성 요소에 대한 Hadoop 환경에서 값을 변경합니다. | Restarts the Hadoop HDFS services Namenode, SecondaryNamenode, Datanode, ZKFC, and Journalnode. Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts PhoenixQueryserver, HiveServer2, Hive MetaStore, and MapReduce-HistoryServer. |
| hadoop-log4j | Hadoop log4j.properties 파일에서 값을 변경합니다. | Restarts the Hadoop HDFS services SecondaryNamenode, Datanode, and Journalnode. Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts Hadoop KMS, Hadoop Httpfs, and MapReduce-HistoryServer. |
| hadoop-ssl-server | hadoop ssl 서버 구성을 변경합니다. | Not available. |
| hadoop-ssl-client | hadoop ssl 클라이언트 구성을 변경합니다. | Not available. |
| hbase | Apache HBase에 대한 Amazon EMR 큐레이트 설정입니다. | Custom EMR specific property. Sets emrfs-site and hbase-site configs. See those for their associated restarts. |
| hbase-env | HBase 환경에서 값을 변경합니다. | Restarts the HBase services RegionServer, HBaseMaster, ThriftServer, RestServer. |
| hbase-log4j | HBase hbase-log4j.properties 파일에서 값을 변경합니다. | Restarts the HBase services RegionServer, HBaseMaster, ThriftServer, RestServer. |
| hbase-metrics | HBase hadoop-metrics2-hbase.properties 파일에서 값을 변경합니다. | Restarts the HBase services RegionServer, HBaseMaster, ThriftServer, RestServer. |
| hbase-policy | HBase hbase-policy.xml 파일에서 값을 변경합니다. | Not available. |
| hbase-site | HBase hbase-site.xml 파일에서 값을 변경합니다. | Restarts the HBase services RegionServer, HBaseMaster, ThriftServer, RestServer. Additionally restarts Phoenix QueryServer. |
| hdfs-encryption-zones | HDFS 암호화 영역을 구성합니다. | This classification should not be reconfigured. |
| hdfs-env | HDFS 환경에서 값을 변경합니다. | Restarts Hadoop HDFS services Namenode, Datanode, and ZKFC. |
| hdfs-site | HDFS hdfs-site.xml에서 값을 변경합니다. | Restarts the Hadoop HDFS services Namenode, SecondaryNamenode, Datanode, ZKFC, and Journalnode. Additionally restarts Hadoop Httpfs. |
| hcatalog-env | HCatalog 환경에서 값을 변경합니다. | Restarts Hive HCatalog Server. |
| hcatalog-server-jndi | HCatalog jndi.properties 환경에서 값을 변경합니다. | Restarts Hive HCatalog Server. |
| hcatalog-server-proto-hive-site | HCatalog proto-hive-site.xml에서 값을 변경합니다. | Restarts Hive HCatalog Server. |
| hcatalog-webhcat-env | HCatalog WebHCat 환경에서 값을 변경합니다. | Restarts Hive WebHCat server. |
| hcatalog-webhcat-log4j2 | HCatalog WebHCat log4j2.properties에서 값을 변경합니다. | Restarts Hive WebHCat server. |
| hcatalog-webhcat-site | HCatalog WebHCat webhcat-site.xml 파일에서 값을 변경합니다. | Restarts Hive WebHCat server. |
| hive | Apache Hive에 대한 Amazon EMR 큐레이트 설정입니다. | Sets configurations to launch Hive LLAP service. |
| hive-beeline-log4j2 | Hive beeline-log4j2.properties 파일에서 값을 변경합니다. | Not available. |
| hive-parquet-logging | Hive parquet-logging.properties 파일에서 값을 변경합니다. | Not available. |
| hive-env | Hive 환경에서 값을 변경합니다. | Restarts HiveServer2, HiveMetastore, and Hive HCatalog-Server. Runs Hive schemaTool CLI commands to verify hive-metastore. |
| hive-exec-log4j2 | Hive hive-exec-log4j2.properties 파일에서 값을 변경합니다. | Not available. |
| hive-llap-daemon-log4j2 | Hive llap-daemon-log4j2.properties 파일에서 값을 변경합니다. | Not available. |
| hive-log4j2 | Hive hive-log4j2.properties 파일에서 값을 변경합니다. | Not available. |
| hive-site | Hive hive-site.xml 파일에서 값을 변경합니다. | Restarts HiveServer2, HiveMetastore, and Hive HCatalog-Server. Runs Hive schemaTool CLI commands to verify hive-metastore. Also restarts Oozie and Zeppelin. |
| hiveserver2-site | Hive Server2 hiveserver2-site.xml 파일에서 값을 변경합니다. | Not available. |
| hue-ini | Hue ini 파일에서 값을 변경합니다. | Restarts Hue. Also activates Hue config override CLI commands to pick up new configurations. |
| httpfs-env | HTTPFS 환경에서 값을 변경합니다. | Restarts Hadoop Httpfs service. |
| httpfs-site | Hadoop httpfs-site.xml 파일에서 값을 변경합니다. | Restarts Hadoop Httpfs service. |
| hadoop-kms-acls | Hadoop kms-acls.xml 파일에서 값을 변경합니다. | Not available. |
| hadoop-kms-env | Hadoop KMS 환경에서 값을 변경합니다. | Restarts Hadoop-KMS service. |
| hadoop-kms-java-home | Hadoop의 KMS java 홈 변경 | Not available. |
| hadoop-kms-log4j | Hadoop kms-log4j.properties 파일에서 값을 변경합니다. | Not available. |
| hadoop-kms-site | Hadoop kms-site.xml 파일에서 값을 변경합니다. | Restarts Hadoop-KMS and Ranger-KMS service. |
| hudi-env | Hudi 환경에서 값을 변경합니다. | Not available. |
| hudi-defaults | Hudi hudi-defaults.conf 파일에서 값을 변경합니다. | Not available. |
| iceberg-defaults | Iceberg iceberg-defaults.conf 파일에서 값을 변경합니다. | Not available. |
| delta-defaults | Delta delta-defaults.conf 파일에서 값을 변경합니다. | Not available. |
| jupyter-notebook-conf | Jupyter Notebook jupyter\$1notebook\$1config.py 파일에서 값을 변경합니다. | Not available. |
| jupyter-hub-conf | JupyterHubs jupyterhub\$1config.py 파일에서 값을 변경합니다. | Not available. |
| jupyter-s3-conf | Jupyter Notebook S3 지속성 구성 | Not available. |
| jupyter-sparkmagic-conf | Sparkmagic config.json 파일에서 값을 변경합니다. | Not available. |
| livy-conf | Livy livy.conf 파일에서 값을 변경합니다. | Restarts Livy Server. |
| livy-env | Livy 환경에서 값을 변경합니다. | Restarts Livy Server. |
| livy-log4j2 | Livy log4j2.properties 설정을 변경합니다. | Restarts Livy Server. |
| mapred-env | MapReduce 애플리케이션 환경에서 값을 변경합니다. | Restarts Hadoop MapReduce-HistoryServer. |
| mapred-site | MapReduce 애플리케이션 mapred-site.xml 파일에서 값을 변경합니다. | Restarts Hadoop MapReduce-HistoryServer. |
| oozie-env | Oozie 환경에서 값을 변경합니다. | Restarts Oozie. |
| oozie-log4j | Oozie oozie-log4j.properties 파일에서 값을 변경합니다. | Restarts Oozie. |
| oozie-site | Oozie oozie-site.xml 파일에서 값을 변경합니다. | Restarts Oozie. |
| phoenix-hbase-metrics | Phoenix hadoop-metrics2-hbase.properties 파일에서 값을 변경합니다. | Not available. |
| phoenix-hbase-site | Phoenix hbase-site.xml 파일에서 값을 변경합니다. | Not available. |
| phoenix-log4j2 | Phoenix log4j2.properties 파일에서 값을 변경합니다. | Restarts Phoenix-QueryServer. |
| phoenix-metrics | Phoenix hadoop-metrics2-phoenix.properties 파일에서 값을 변경합니다. | Not available. |
| pig-env | Pig 환경에서 값을 변경합니다. | Not available. |
| pig-properties | Pig pig.properties 파일에서 값을 변경합니다. | Restarts Oozie. |
| pig-log4j | Pig log4j.properties 파일에서 값을 변경합니다. | Not available. |
| presto-log | Presto log.properties 파일에서 값을 변경합니다. | Restarts Presto-Server (for PrestoDB) |
| presto-config | Presto config.properties 파일에서 값을 변경합니다. | Restarts Presto-Server (for PrestoDB) |
| presto-password-authenticator | Presto password-authenticator.properties 파일에서 값을 변경합니다. | Not available. |
| presto-env | Presto presto-env.sh 파일에서 값을 변경합니다. | Restarts Presto-Server (for PrestoDB) |
| presto-node | Presto node.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-blackhole | Presto blackhole.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-cassandra | Presto cassandra.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-hive | Presto hive.properties 파일에서 값을 변경합니다. | Restarts Presto-Server (for PrestoDB) |
| presto-connector-jmx | Presto jmx.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-kafka | Presto kafka.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-lakeformation | Presto lakeformation.properties 파일에서 값을 변경합니다. | Restarts Presto-Server (for PrestoDB) |
| presto-connector-localfile | Presto localfile.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-memory | Presto memory.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-mongodb | Presto mongodb.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-mysql | Presto mysql.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-postgresql | Presto postgresql.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-raptor | Presto raptor.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-redis | Presto redis.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-redshift | Presto redshift.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-tpch | Presto tpch.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-tpcds | Presto tpcds.properties 파일에서 값을 변경합니다. | Not available. |
| trino-log | Trino log.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-config | Trino config.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-password-authenticator | Trino password-authenticator.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-env | Trino trino-env.sh 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-node | Trino node.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-blackhole | Trino blackhole.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-cassandra | Trino cassandra.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-delta | Trino delta.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-connector-hive | Trino hive.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-exchange-manager | Trino exchange-manager.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-connector-iceberg | Trino iceberg.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-connector-hudi | Trino hudi.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-connector-jmx | Trino jmx.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-kafka | Trino kafka.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-localfile | Trino localfile.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-memory | Trino memory.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-mongodb | Trino mongodb.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-mysql | Trino mysql.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-postgresql | Trino postgresql.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-raptor | Trino raptor.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-redis | Trino redis.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-redshift | Trino redshift.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-tpch | Trino tpch.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-tpcds | Trino tpcds.properties 파일에서 값을 변경합니다. | Not available. |
| ranger-kms-dbks-site | Ranger KMS dbks-site.xml 파일에서 값을 변경합니다. | Restarts Ranger KMS Server. |
| ranger-kms-site | Ranger KMS ranger-kms-site.xml 파일에서 값을 변경합니다. | Restarts Ranger KMS Server. |
| ranger-kms-env | Ranger KMS 환경에서 값을 변경합니다. | Restarts Ranger KMS Server. |
| ranger-kms-logback | Ranger KMS kms-logback.xml 파일에서 값을 변경합니다. | Not available. |
| ranger-kms-db-ca | Ranger KMS와의 MySQL SSL 연결에서 CA 파일의 값을 변경합니다. | Not available. |
| spark | Apache Spark에 대한 Amazon EMR 큐레이트 설정입니다. | This property modifies spark-defaults. See actions there. |
| spark-defaults | Spark spark-defaults.conf 파일에서 값을 변경합니다. | Restarts Spark history server and Spark thrift server. |
| spark-env | Spark 환경에서 값을 변경합니다. | Restarts Spark history server and Spark thrift server. |
| spark-hive-site | Spark hive-site.xml 파일에서 값을 변경합니다. | Not available. |
| spark-log4j2 | Spark log4j2.properties 파일에서 값을 변경합니다. | Restarts Spark history server and Spark thrift server. |
| spark-metrics | Spark metrics.properties 파일에서 값을 변경합니다. | Restarts Spark history server and Spark thrift server. |
| tez-site | Tez tez-site.xml 파일에서 값을 변경합니다. | Restart Oozie and HiveServer2. |
| yarn-env | YARN 환경에서 값을 변경합니다. | Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts MapReduce-HistoryServer. |
| yarn-site | YARN yarn-site.xml 파일에서 값을 변경합니다. | Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts Livy Server and MapReduce-HistoryServer. |
| zeppelin-env | Zeppelin 환경에서 값을 변경합니다. | Restarts Zeppelin. |
| zeppelin-site | zeppelin-site.xml에서 구성 설정을 변경합니다. | Restarts Zeppelin. |
| zookeeper-config | ZooKeeper zoo.cfg 파일에서 값을 변경합니다. | Restarts Zookeeper server. |
| zookeeper-logback | ZooKeeper logback.xml 파일에서 값을 변경합니다. | Restarts Zookeeper server. |
| emr-metrics | 이 노드에 대한 emr 지표 설정을 변경합니다. | Restarts the CloudWatchAgent service. |
## 7.7.0 변경 로그
**7.7.0 릴리스 및 릴리스 정보에 대한 변경 로그**
| Date | 이벤트 | 설명 |
| --- | --- | --- |
| 2025-02-07 | 문서 게시 | Amazon EMR 7.7.0 릴리스 정보 최초 게시 |
| 2025-02-06 | 배포 완료 | [지원되는 모든 리전](https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/)에 Amazon EMR 7.7.0 완전 배포 |
| 2025-01-30 | 초기 제한 릴리스 | Amazon EMR 7.7.0이 초기 상용 리전에 처음 배포됨 |
# Amazon EMR 릴리스 7.6.0
## 7.6.0 지원 수명 주기
다음 표에서는 Amazon EMR 릴리스 7.6.0에 지원되는 수명 주기 날짜를 설명합니다.
| 지원 단계 | Date |
| --- | --- |
| 초기 릴리스 날짜 | 2025년 1월 10일 |
| 표준 지원 종료 시점 | 2027년 1월 9일 |
| 지원 종료 | 2027년 1월 10일 |
| 수명 종료 | 2028년 1월 10일 |
## 7.6.0 애플리케이션 버전
이 릴리스에 포함된 애플리케이션은 [https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Install-CloudWatch-Agent.html](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Install-CloudWatch-Agent.html), [https://delta.io/](https://delta.io/), [https://flink.apache.org/](https://flink.apache.org/), [http://hbase.apache.org/](http://hbase.apache.org/), [https://cwiki.apache.org/confluence/display/Hive/HCatalog](https://cwiki.apache.org/confluence/display/Hive/HCatalog), [http://hadoop.apache.org/docs/current/](http://hadoop.apache.org/docs/current/), [http://hive.apache.org/](http://hive.apache.org/), [https://hudi.apache.org](https://hudi.apache.org), [http://gethue.com/](http://gethue.com/), [https://iceberg.apache.org/](https://iceberg.apache.org/), [https://jupyter-enterprise-gateway.readthedocs.io/en/latest/](https://jupyter-enterprise-gateway.readthedocs.io/en/latest/), [https://jupyterhub.readthedocs.io/en/latest/#](https://jupyterhub.readthedocs.io/en/latest/#), [https://livy.incubator.apache.org/](https://livy.incubator.apache.org/), [http://oozie.apache.org/](http://oozie.apache.org/), [https://phoenix.apache.org/](https://phoenix.apache.org/), [http://pig.apache.org/](http://pig.apache.org/), [https://prestodb.io/](https://prestodb.io/), [https://spark.apache.org/docs/latest/](https://spark.apache.org/docs/latest/), [https://www.tensorflow.org/](https://www.tensorflow.org/), [https://tez.apache.org/](https://tez.apache.org/), [https://trino.io/](https://trino.io/), [https://zeppelin.incubator.apache.org/](https://zeppelin.incubator.apache.org/), [https://zookeeper.apache.org](https://zookeeper.apache.org)입니다.
아래 테이블에는 이번 Amazon EMR 릴리스에서 사용할 수 있는 애플리케이션 버전과 이전 세 가지 Amazon EMR 릴리스(해당하는 경우)의 애플리케이션 버전이 나와 있습니다.
각 Amazon EMR 릴리스에서 애플리케이션 버전의 전체 기록은 다음 주제를 참조하세요.
+ [Amazon EMR 7.x 릴리스의 애플리케이션 버전](emr-release-app-versions-7.x.md)
+ [Amazon EMR 6.x 릴리스의 애플리케이션 버전](emr-release-app-versions-6.x.md)
+ [Amazon EMR 5.x 릴리스의 애플리케이션 버전](emr-release-app-versions-5.x.md)
+ [Amazon EMR 4.x 릴리스의 애플리케이션 버전](emr-release-app-versions-4.x.md)
**애플리케이션 버전 정보**
| | emr-7.6.0 | emr-7.5.0 | emr-7.4.0 | emr-7.3.0 |
| --- | --- | --- | --- | --- |
| AWS Java용 SDK | 2.29.25, 1.12.779 | 2.28.8, 1.12.772 | 2.28.8, 1.12.772 | 2.25.70, 1.12.747 |
| Python | 3.9, 3.11 | 3.9, 3.11 | 3.9, 3.11 | 3.9, 3.11 |
| Scala | 2.12.18 | 2.12.18 | 2.12.18 | 2.12.18 |
| AmazonCloudWatchAgent | 1.300032.2-amzn-0 | 1.300032.2-amzn-0 | 1.300032.2-amzn-0 | 1.300032.2-amzn-0 |
| Delta | 3.2.1-amzn-1 | 3.2.1-amzn-0 | 3.2.0-amzn-1 | 3.2.0-amzn-0 |
| Flink | 1.20.0-amzn-0 | 1.19.1-amzn-1 | 1.19.1-amzn-0 | 1.18.1-amzn-2 |
| Ganglia | - | - | - | - |
| HBase | 2.6.1-amzn-0 | 2.5.10-amzn-0 | 2.5.5-amzn-0 | 2.4.17-amzn-7 |
| HCatalog | 3.1.3-amzn-15 | 3.1.3-amzn-14 | 3.1.3-amzn-13 | 3.1.3-amzn-12 |
| Hadoop | 3.4.0-amzn-2 | 3.4.0-amzn-1 | 3.4.0-amzn-0 | 3.3.6-amzn-5 |
| Hive | 3.1.3-amzn-15 | 3.1.3-amzn-14 | 3.1.3-amzn-13 | 3.1.3-amzn-12 |
| Hudi | 0.15.0-amzn-3 | 0.15.0-amzn-2 | 0.15.0-amzn-1 | 0.15.0-amzn-0 |
| Hue | 4.11.0 | 4.11.0 | 4.11.0 | 4.11.0 |
| Iceberg | 1.6.1-amzn-2 | 1.6.1-amzn-1 | 1.6.1-amzn-0 | 1.5.2-amzn-0 |
| JupyterEnterpriseGateway | 2.6.0 | 2.6.0 | 2.6.0 | 2.6.0 |
| JupyterHub | 1.5.0 | 1.5.0 | 1.5.0 | 1.5.0 |
| Livy | 0.8.0-incubating | 0.8.0-incubating | 0.8.0-incubating | 0.8.0-incubating |
| MXNet | - | - | - | - |
| Mahout | - | - | - | - |
| Oozie | 5.2.1 | 5.2.1 | 5.2.1 | 5.2.1 |
| Phoenix | 5.2.0 | 5.2.0 | 5.2.0 | 5.1.3 |
| Pig | 0.17.0 | 0.17.0 | 0.17.0 | 0.17.0 |
| Presto | 0.287-amzn-1 | 0.287-amzn-0 | 0.287-amzn-0 | 0.285-amzn-1 |
| Spark | 3.5.3-amzn-0 | 3.5.2-amzn-1 | 3.5.2-amzn-0 | 3.5.1-amzn-1 |
| Sqoop | - | - | 1.4.7 | 1.4.7 |
| TensorFlow | 2.16.1 | 2.16.1 | 2.16.1 | 2.16.1 |
| Tez | 0.10.2-amzn-13 | 0.10.2-amzn-12 | 0.10.2-amzn-11 | 0.10.2-amzn-10 |
| Trino (PrestoSQL) | 457-amzn-0 | 446-amzn-0 | 446-amzn-0 | 442-amzn-0 |
| Zeppelin | 0.11.1 | 0.11.1 | 0.11.1 | 0.11.1 |
| ZooKeeper | 3.9.2-amzn-0 | 3.9.2-amzn-0 | 3.9.2-amzn-0 | 3.9.1-amzn-1 |
# 7.6.0 릴리스 구성 요소 세부 정보
Amazon EMR 7.6.0의 *추가* 패키지에 대한 자세한 내용은 다음 표를 참조하세요.
| 애플리케이션 | 애플리케이션 유형 | 패키지 | 패키지 유형 | 패키지 버전 |
| --- | --- | --- | --- | --- |
| AmazonCloudWatchAgent | Core | hadoop-hdfs-journalnode | 추가 항목 | 3.4.0.amzn.2-1.amzn2023 |
| AmazonCloudWatchAgent | Core | ranger-kms | 추가 항목 | 2.0.0-1.amzn2023 |
| AmazonCloudWatchAgent | Core | s3-dist-cp | 추가 항목 | 2.36.0-1.amzn2023 |
| AmazonCloudWatchAgent | Core | zookeeper | 추가 항목 | 3.9.2.amzn.0-1.amzn2023 |
| AmazonCloudWatchAgent | Core | zookeeper-server | 추가 항목 | 3.9.2.amzn.0-1.amzn2023 |
| Flink | Core | hadoop-client | 추가 항목 | 3.4.0.amzn.2-1.amzn2023 |
| Flink | Core | hadoop-hdfs | 추가 항목 | 3.4.0.amzn.2-1.amzn2023 |
| Flink | Core | hadoop-hdfs-datanode | 추가 항목 | 3.4.0.amzn.2-1.amzn2023 |
| Flink | Core | hadoop-hdfs-journalnode | 추가 항목 | 3.4.0.amzn.2-1.amzn2023 |
| Flink | Core | hadoop-hdfs-namenode | 추가 항목 | 3.4.0.amzn.2-1.amzn2023 |
| Flink | Core | hadoop-httpfs | 추가 항목 | 3.4.0.amzn.2-1.amzn2023 |
| Flink | Core | hadoop-kms | 추가 항목 | 3.4.0.amzn.2-1.amzn2023 |
| Flink | Core | hadoop-mapreduce | 추가 항목 | 3.4.0.amzn.2-1.amzn2023 |
| Flink | Core | hadoop-mapreduce-historyserver | 추가 항목 | 3.4.0.amzn.2-1.amzn2023 |
| Flink | Core | hadoop-yarn | 추가 항목 | 3.4.0.amzn.2-1.amzn2023 |
| Flink | Core | hadoop-yarn-nodemanager | 추가 항목 | 3.4.0.amzn.2-1.amzn2023 |
| Flink | Core | hadoop-yarn-proxyserver | 추가 항목 | 3.4.0.amzn.2-1.amzn2023 |
| Flink | Core | hadoop-yarn-resourcemanager | 추가 항목 | 3.4.0.amzn.2-1.amzn2023 |
| Flink | Core | hadoop-yarn-timelineserver | 추가 항목 | 3.4.0.amzn.2-1.amzn2023 |
| Flink | Core | hudi | 추가 항목 | 0.15.0.amzn.3-1.amzn2023 |
| Flink | Core | ranger-kms | 추가 항목 | 2.0.0-1.amzn2023 |
| Flink | Core | hadoop | 추가 항목 | 3.4.0.amzn.2-1.amzn2023 |
| HBase | Core | s3-dist-cp | 추가 항목 | 2.36.0-1.amzn2023 |
| HCatalog | Core | hadoop-yarn-proxyserver | 추가 항목 | 3.4.0.amzn.2-1.amzn2023 |
| HCatalog | Core | mariadb-connector-java | 추가 항목 | |
| Hive | Core | hadoop-httpfs | 추가 항목 | 3.4.0.amzn.2-1.amzn2023 |
| Hive | Core | hadoop-yarn-proxyserver | 추가 항목 | 3.4.0.amzn.2-1.amzn2023 |
| Hive | Core | hive-hbase | 추가 항목 | 3.1.3.amzn.15-1.amzn2023 |
| Hive | Core | mariadb-connector-java | 추가 항목 | 2.7.2-1 |
| Hive | Core | s3-dist-cp | 추가 항목 | 2.36.0-1.amzn2023 |
| 피닉스 | Core | s3-dist-cp | 추가 항목 | 2.36.0-1.amzn2023 |
| Spark | Core | spark-datanucleus | 추가 항목 | 3.5.1.amzn.0-1.amzn2023 |
| Tez의 Hive 실행 시간 비교 | Core | hadoop-mapreduce | 추가 항목 | 3.4.0.amzn.2-1.amzn2023 |
| Tez의 Hive 실행 시간 비교 | Core | hadoop-mapreduce-historyserver | 추가 항목 | 3.4.0.amzn.2-1.amzn2023 |
| Tez의 Hive 실행 시간 비교 | Core | hadoop-yarn-proxyserver | 추가 항목 | 3.4.0.amzn.2-1.amzn2023 |
| Trino | Core | bigtop-utils | 추가 항목 | 1.2.0-1.amzn2023 |
| Trino | Core | hadoop-client | 추가 항목 | 3.4.0.amzn.2-1.amzn2023 |
| Trino | Core | hadoop-hdfs | 추가 항목 | 3.4.0.amzn.2-1.amzn2023 |
| Trino | Core | hadoop-hdfs-datanode | 추가 항목 | 3.4.0.amzn.2-1.amzn2023 |
| Trino | Core | hadoop-hdfs-journalnode | 추가 항목 | 3.4.0.amzn.2-1.amzn2023 |
| Trino | Core | hadoop-hdfs-namenode | 추가 항목 | 3.4.0.amzn.2-1.amzn2023 |
| Trino | Core | hadoop-kms | 추가 항목 | 3.4.0.amzn.2-1.amzn2023 |
| Trino | Core | hadoop-mapreduce | 추가 항목 | 3.4.0.amzn.2-1.amzn2023 |
| Trino | Core | hadoop-mapreduce-historyserver | 추가 항목 | 3.4.0.amzn.2-1.amzn2023 |
| Trino | Core | hadoop-yarn | 추가 항목 | 3.4.0.amzn.2-1.amzn2023 |
| Trino | Core | hadoop-yarn-nodemanager | 추가 항목 | 3.4.0.amzn.2-1.amzn2023 |
| Trino | Core | hadoop-yarn-proxyserver | 추가 항목 | 3.4.0.amzn.2-1.amzn2023 |
| Trino | Core | hadoop-yarn-resourcemanager | 추가 항목 | 3.4.0.amzn.2-1.amzn2023 |
| Trino | Core | hadoop-yarn-timelineserver | 추가 항목 | 3.4.0.amzn.2-1.amzn2023 |
| Trino | Core | hive | 추가 항목 | 3.1.3.amzn.12-1.amzn2023 |
| Trino | Core | hive-hcatalog-server | 추가 항목 | 3.1.3.amzn.12-1.amzn2023 |
| Trino | Core | mariadb-connector-java | 추가 항목 | 2.7.2-1 |
| Trino | Core | ranger-kms | 추가 항목 | 2.0.0-1.amzn2023 |
| Trino | Core | zookeeper | 추가 항목 | 3.9.2.amzn.0-1.amzn2023 |
| Trino | Core | zookeeper-server | 추가 항목 | 3.9.2.amzn.0-1.amzn2023 |
| Trino | Core | bigtop-groovy | 추가 항목 | 2.5.4-1.amzn2023 |
| Trino | Core | bigtop-jsvc | 추가 항목 | 1.2.4-1.amzn2023 |
| Trino | Core | hadoop | 추가 항목 | 3.4.0.amzn.2-1.amzn2023 |
| Trino | Core | hadoop-lzo | 추가 항목 | 0.4.19-1.amzn2023 |
| Trino | Core | hive-hcatalog | 추가 항목 | 3.1.3.amzn.15-1.amzn2023 |
| Trino | Core | hive-jdbc | 추가 항목 | 3.1.3.amzn.12-1.amzn2023 |
| Zookeeper | Core | emrfs | 추가 항목 | 3.9.2.amzn.0-1.amzn2023 |
| Zookeeper | Core | hadoop-client | 추가 항목 | 3.9.2.amzn.0-1.amzn2023 |
| Zookeeper | Core | hadoop-hdfs | 추가 항목 | 3.9.2.amzn.0-1.amzn2023 |
| Zookeeper | Core | hadoop-hdfs-datanode | 추가 항목 | 3.9.2.amzn.0-1.amzn2023 |
| Zookeeper | Core | hadoop-hdfs-journalnode | 추가 항목 | 3.9.2.amzn.0-1.amzn2023 |
| Zookeeper | Core | hadoop-hdfs-namenode | 추가 항목 | 3.9.2.amzn.0-1.amzn2023 |
| Zookeeper | Core | hadoop-httpfs | 추가 항목 | 3.9.2.amzn.0-1.amzn2023 |
| Zookeeper | Core | hadoop-kms | 추가 항목 | 3.9.2.amzn.0-1.amzn2023 |
| Zookeeper | Core | hadoop-mapreduce | 추가 항목 | 3.4.0.amzn.2-1.amzn2023 |
| Zookeeper | Core | hadoop-mapreduce-historyserver | 추가 항목 | 3.4.0.amzn.2-1.amzn2023 |
| Zookeeper | Core | hadoop-yarn | 추가 항목 | 3.4.0.amzn.2-1.amzn2023 |
| Zookeeper | Core | hadoop-yarn-nodemanager | 추가 항목 | 3.4.0.amzn.2-1.amzn2023 |
| Zookeeper | Core | hadoop-yarn-proxyserver | 추가 항목 | 3.4.0.amzn.2-1.amzn2023 |
| Zookeeper | Core | hadoop-yarn-resourcemanager | 추가 항목 | 3.4.0.amzn.2-1.amzn2023 |
| Zookeeper | Core | hadoop-yarn-timelineserver | 추가 항목 | 3.4.0.amzn.2-1.amzn2023 |
| Zookeeper | Core | ranger-kms | 추가 항목 | 2.0.0-1.amzn2023 |
# 7.6.0 일반적인 취약성 및 노출
다음 표에는 Amazon EMR 7.6.0의 권장 구성에서 실행되는 EMR 클러스터에 영향을 주지 않는 모든 CVEs가 나열되어 있습니다. Amazon EMR은 업스트림 오픈 소스의 수정 사항 가용성에 종속되어 있으며, Amazon EMR이 수정 사항을 확인한 후 90일 이내에 코어 엔진 구성 요소의 일부로 안정적인 최신 버전을 제공합니다.
이 표는 2025년 1월 9일에 업데이트되었습니다.
| CVE ID | 심각도 | CVE 세부 정보 URL |
| --- | --- | --- |
| CVE-2013-7285 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2013-7285](https://nvd.nist.gov/vuln/detail/CVE-2013-7285) |
| CVE-2015-1832 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2015-1832](https://nvd.nist.gov/vuln/detail/CVE-2015-1832) |
| CVE-2016-5018 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2016-5018](https://nvd.nist.gov/vuln/detail/CVE-2016-5018) |
| CVE-2017-15095 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2017-15095](https://nvd.nist.gov/vuln/detail/CVE-2017-15095) |
| CVE-2017-17485 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2017-17485](https://nvd.nist.gov/vuln/detail/CVE-2017-17485) |
| CVE-2017-7525 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2017-7525](https://nvd.nist.gov/vuln/detail/CVE-2017-7525) |
| CVE-2018-11307 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-11307](https://nvd.nist.gov/vuln/detail/CVE-2018-11307) |
| CVE-2018-14718 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-14718](https://nvd.nist.gov/vuln/detail/CVE-2018-14718) |
| CVE-2018-14719 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-14719](https://nvd.nist.gov/vuln/detail/CVE-2018-14719) |
| CVE-2018-14720 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-14720](https://nvd.nist.gov/vuln/detail/CVE-2018-14720) |
| CVE-2018-14721 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-14721](https://nvd.nist.gov/vuln/detail/CVE-2018-14721) |
| CVE-2018-19360 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-19360](https://nvd.nist.gov/vuln/detail/CVE-2018-19360) |
| CVE-2018-19361 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-19361](https://nvd.nist.gov/vuln/detail/CVE-2018-19361) |
| CVE-2018-19362 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-19362](https://nvd.nist.gov/vuln/detail/CVE-2018-19362) |
| CVE-2018-7489 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-7489](https://nvd.nist.gov/vuln/detail/CVE-2018-7489) |
| CVE-2019-10173 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-10173](https://nvd.nist.gov/vuln/detail/CVE-2019-10173) |
| CVE-2019-10202 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-10202](https://nvd.nist.gov/vuln/detail/CVE-2019-10202) |
| CVE-2019-14379 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14379](https://nvd.nist.gov/vuln/detail/CVE-2019-14379) |
| CVE-2019-14540 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14540](https://nvd.nist.gov/vuln/detail/CVE-2019-14540) |
| CVE-2019-14892 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14892](https://nvd.nist.gov/vuln/detail/CVE-2019-14892) |
| CVE-2019-14893 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14893](https://nvd.nist.gov/vuln/detail/CVE-2019-14893) |
| CVE-2019-16335 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-16335](https://nvd.nist.gov/vuln/detail/CVE-2019-16335) |
| CVE-2019-16942 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-16942](https://nvd.nist.gov/vuln/detail/CVE-2019-16942) |
| CVE-2019-16943 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-16943](https://nvd.nist.gov/vuln/detail/CVE-2019-16943) |
| CVE-2019-17267 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-17267](https://nvd.nist.gov/vuln/detail/CVE-2019-17267) |
| CVE-2019-17531 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-17531](https://nvd.nist.gov/vuln/detail/CVE-2019-17531) |
| CVE-2019-20330 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-20330](https://nvd.nist.gov/vuln/detail/CVE-2019-20330) |
| CVE-2019-20444 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-20444](https://nvd.nist.gov/vuln/detail/CVE-2019-20444) |
| CVE-2019-20445 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-20445](https://nvd.nist.gov/vuln/detail/CVE-2019-20445) |
| CVE-2020-8840 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8840](https://nvd.nist.gov/vuln/detail/CVE-2020-8840) |
| CVE-2020-9546 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-9546](https://nvd.nist.gov/vuln/detail/CVE-2020-9546) |
| CVE-2020-9547 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-9547](https://nvd.nist.gov/vuln/detail/CVE-2020-9547) |
| CVE-2020-9548 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-9548](https://nvd.nist.gov/vuln/detail/CVE-2020-9548) |
| CVE-2021-21342 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2021-21342](https://nvd.nist.gov/vuln/detail/CVE-2021-21342) |
| CVE-2021-21344 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2021-21344](https://nvd.nist.gov/vuln/detail/CVE-2021-21344) |
| CVE-2021-21345 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2021-21345](https://nvd.nist.gov/vuln/detail/CVE-2021-21345) |
| CVE-2021-21346 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2021-21346](https://nvd.nist.gov/vuln/detail/CVE-2021-21346) |
| CVE-2021-21347 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2021-21347](https://nvd.nist.gov/vuln/detail/CVE-2021-21347) |
| CVE-2021-21350 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2021-21350](https://nvd.nist.gov/vuln/detail/CVE-2021-21350) |
| CVE-2021-21351 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2021-21351](https://nvd.nist.gov/vuln/detail/CVE-2021-21351) |
| CVE-2021-41411 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2021-41411](https://nvd.nist.gov/vuln/detail/CVE-2021-41411) |
| CVE-2022-1471 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-1471](https://nvd.nist.gov/vuln/detail/CVE-2022-1471) |
| CVE-2022-37865 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-37865](https://nvd.nist.gov/vuln/detail/CVE-2022-37865) |
| CVE-2022-39135 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-39135](https://nvd.nist.gov/vuln/detail/CVE-2022-39135) |
| CVE-2022-42889 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42889](https://nvd.nist.gov/vuln/detail/CVE-2022-42889) |
| CVE-2022-46337 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-46337](https://nvd.nist.gov/vuln/detail/CVE-2022-46337) |
| CVE-2024-47561 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2024-47561](https://nvd.nist.gov/vuln/detail/CVE-2024-47561) |
| CVE-2024-52046 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2024-52046](https://nvd.nist.gov/vuln/detail/CVE-2024-52046) |
| CVE-2024-53990 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2024-53990](https://nvd.nist.gov/vuln/detail/CVE-2024-53990) |
| CVE-2012-0881 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2012-0881](https://nvd.nist.gov/vuln/detail/CVE-2012-0881) |
| CVE-2013-4002 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2013-4002](https://nvd.nist.gov/vuln/detail/CVE-2013-4002) |
| CVE-2014-8125 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2014-8125](https://nvd.nist.gov/vuln/detail/CVE-2014-8125) |
| CVE-2015-5237 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2015-5237](https://nvd.nist.gov/vuln/detail/CVE-2015-5237) |
| CVE-2016-3674 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2016-3674](https://nvd.nist.gov/vuln/detail/CVE-2016-3674) |
| CVE-2016-6796 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2016-6796](https://nvd.nist.gov/vuln/detail/CVE-2016-6796) |
| CVE-2017-7957 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2017-7957](https://nvd.nist.gov/vuln/detail/CVE-2017-7957) |
| CVE-2018-1000180 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-1000180](https://nvd.nist.gov/vuln/detail/CVE-2018-1000180) |
| CVE-2018-12022 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-12022](https://nvd.nist.gov/vuln/detail/CVE-2018-12022) |
| CVE-2018-12023 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-12023](https://nvd.nist.gov/vuln/detail/CVE-2018-12023) |
| CVE-2018-5968 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-5968](https://nvd.nist.gov/vuln/detail/CVE-2018-5968) |
| CVE-2019-0205 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-0205](https://nvd.nist.gov/vuln/detail/CVE-2019-0205) |
| CVE-2019-10172 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-10172](https://nvd.nist.gov/vuln/detail/CVE-2019-10172) |
| CVE-2019-12086 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-12086](https://nvd.nist.gov/vuln/detail/CVE-2019-12086) |
| CVE-2019-14439 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14439](https://nvd.nist.gov/vuln/detail/CVE-2019-14439) |
| CVE-2020-10650 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10650](https://nvd.nist.gov/vuln/detail/CVE-2020-10650) |
| CVE-2020-10672 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10672](https://nvd.nist.gov/vuln/detail/CVE-2020-10672) |
| CVE-2020-10673 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10673](https://nvd.nist.gov/vuln/detail/CVE-2020-10673) |
| CVE-2020-10968 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10968](https://nvd.nist.gov/vuln/detail/CVE-2020-10968) |
| CVE-2020-10969 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10969](https://nvd.nist.gov/vuln/detail/CVE-2020-10969) |
| CVE-2020-11111 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11111](https://nvd.nist.gov/vuln/detail/CVE-2020-11111) |
| CVE-2020-11112 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11112](https://nvd.nist.gov/vuln/detail/CVE-2020-11112) |
| CVE-2020-11113 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11113](https://nvd.nist.gov/vuln/detail/CVE-2020-11113) |
| CVE-2020-11619 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11619](https://nvd.nist.gov/vuln/detail/CVE-2020-11619) |
| CVE-2020-11620 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11620](https://nvd.nist.gov/vuln/detail/CVE-2020-11620) |
| CVE-2020-13936 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-13936](https://nvd.nist.gov/vuln/detail/CVE-2020-13936) |
| CVE-2020-13949 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-13949](https://nvd.nist.gov/vuln/detail/CVE-2020-13949) |
| CVE-2020-14060 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14060](https://nvd.nist.gov/vuln/detail/CVE-2020-14060) |
| CVE-2020-14061 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14061](https://nvd.nist.gov/vuln/detail/CVE-2020-14061) |
| CVE-2020-14062 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14062](https://nvd.nist.gov/vuln/detail/CVE-2020-14062) |
| CVE-2020-14195 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14195](https://nvd.nist.gov/vuln/detail/CVE-2020-14195) |
| CVE-2020-24616 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-24616](https://nvd.nist.gov/vuln/detail/CVE-2020-24616) |
| CVE-2020-24750 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-24750](https://nvd.nist.gov/vuln/detail/CVE-2020-24750) |
| CVE-2020-25649 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-25649](https://nvd.nist.gov/vuln/detail/CVE-2020-25649) |
| CVE-2020-26217 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-26217](https://nvd.nist.gov/vuln/detail/CVE-2020-26217) |
| CVE-2020-26258 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-26258](https://nvd.nist.gov/vuln/detail/CVE-2020-26258) |
| CVE-2020-28052 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-28052](https://nvd.nist.gov/vuln/detail/CVE-2020-28052) |
| CVE-2020-35490 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-35490](https://nvd.nist.gov/vuln/detail/CVE-2020-35490) |
| CVE-2020-35491 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-35491](https://nvd.nist.gov/vuln/detail/CVE-2020-35491) |
| CVE-2020-35728 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-35728](https://nvd.nist.gov/vuln/detail/CVE-2020-35728) |
| CVE-2020-36179 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36179](https://nvd.nist.gov/vuln/detail/CVE-2020-36179) |
| CVE-2020-36180 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36180](https://nvd.nist.gov/vuln/detail/CVE-2020-36180) |
| CVE-2020-36181 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36181](https://nvd.nist.gov/vuln/detail/CVE-2020-36181) |
| CVE-2020-36182 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36182](https://nvd.nist.gov/vuln/detail/CVE-2020-36182) |
| CVE-2020-36183 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36183](https://nvd.nist.gov/vuln/detail/CVE-2020-36183) |
| CVE-2020-36184 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36184](https://nvd.nist.gov/vuln/detail/CVE-2020-36184) |
| CVE-2020-36185 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36185](https://nvd.nist.gov/vuln/detail/CVE-2020-36185) |
| CVE-2020-36186 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36186](https://nvd.nist.gov/vuln/detail/CVE-2020-36186) |
| CVE-2020-36187 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36187](https://nvd.nist.gov/vuln/detail/CVE-2020-36187) |
| CVE-2020-36188 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36188](https://nvd.nist.gov/vuln/detail/CVE-2020-36188) |
| CVE-2020-36189 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36189](https://nvd.nist.gov/vuln/detail/CVE-2020-36189) |
| CVE-2020-36518 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36518](https://nvd.nist.gov/vuln/detail/CVE-2020-36518) |
| CVE-2021-20190 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-20190](https://nvd.nist.gov/vuln/detail/CVE-2021-20190) |
| CVE-2021-21341 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-21341](https://nvd.nist.gov/vuln/detail/CVE-2021-21341) |
| CVE-2021-21343 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-21343](https://nvd.nist.gov/vuln/detail/CVE-2021-21343) |
| CVE-2021-21348 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-21348](https://nvd.nist.gov/vuln/detail/CVE-2021-21348) |
| CVE-2021-21349 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-21349](https://nvd.nist.gov/vuln/detail/CVE-2021-21349) |
| CVE-2021-29505 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-29505](https://nvd.nist.gov/vuln/detail/CVE-2021-29505) |
| CVE-2021-31684 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-31684](https://nvd.nist.gov/vuln/detail/CVE-2021-31684) |
| CVE-2021-34538 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-34538](https://nvd.nist.gov/vuln/detail/CVE-2021-34538) |
| CVE-2021-37136 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-37136](https://nvd.nist.gov/vuln/detail/CVE-2021-37136) |
| CVE-2021-39139 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-39139](https://nvd.nist.gov/vuln/detail/CVE-2021-39139) |
| CVE-2021-39141 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-39141](https://nvd.nist.gov/vuln/detail/CVE-2021-39141) |
| CVE-2021-39144 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-39144](https://nvd.nist.gov/vuln/detail/CVE-2021-39144) |
| CVE-2021-39145 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-39145](https://nvd.nist.gov/vuln/detail/CVE-2021-39145) |
| CVE-2021-39146 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-39146](https://nvd.nist.gov/vuln/detail/CVE-2021-39146) |
| CVE-2021-39147 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-39147](https://nvd.nist.gov/vuln/detail/CVE-2021-39147) |
| CVE-2021-39148 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-39148](https://nvd.nist.gov/vuln/detail/CVE-2021-39148) |
| CVE-2021-39149 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-39149](https://nvd.nist.gov/vuln/detail/CVE-2021-39149) |
| CVE-2021-39150 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-39150](https://nvd.nist.gov/vuln/detail/CVE-2021-39150) |
| CVE-2021-39151 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-39151](https://nvd.nist.gov/vuln/detail/CVE-2021-39151) |
| CVE-2021-39152 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-39152](https://nvd.nist.gov/vuln/detail/CVE-2021-39152) |
| CVE-2021-39153 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-39153](https://nvd.nist.gov/vuln/detail/CVE-2021-39153) |
| CVE-2021-39154 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-39154](https://nvd.nist.gov/vuln/detail/CVE-2021-39154) |
| CVE-2021-43859 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-43859](https://nvd.nist.gov/vuln/detail/CVE-2021-43859) |
| CVE-2022-1415 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-1415](https://nvd.nist.gov/vuln/detail/CVE-2022-1415) |
| CVE-2022-25647 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-25647](https://nvd.nist.gov/vuln/detail/CVE-2022-25647) |
| CVE-2022-25857 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-25857](https://nvd.nist.gov/vuln/detail/CVE-2022-25857) |
| CVE-2022-3171 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3171](https://nvd.nist.gov/vuln/detail/CVE-2022-3171) |
| CVE-2022-3509 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3509](https://nvd.nist.gov/vuln/detail/CVE-2022-3509) |
| CVE-2022-3510 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3510](https://nvd.nist.gov/vuln/detail/CVE-2022-3510) |
| CVE-2022-36364 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-36364](https://nvd.nist.gov/vuln/detail/CVE-2022-36364) |
| CVE-2022-37866 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-37866](https://nvd.nist.gov/vuln/detail/CVE-2022-37866) |
| CVE-2022-40149 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-40149](https://nvd.nist.gov/vuln/detail/CVE-2022-40149) |
| CVE-2022-40150 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-40150](https://nvd.nist.gov/vuln/detail/CVE-2022-40150) |
| CVE-2022-40151 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-40151](https://nvd.nist.gov/vuln/detail/CVE-2022-40151) |
| CVE-2022-40152 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-40152](https://nvd.nist.gov/vuln/detail/CVE-2022-40152) |
| CVE-2022-41966 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-41966](https://nvd.nist.gov/vuln/detail/CVE-2022-41966) |
| CVE-2022-42003 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42003](https://nvd.nist.gov/vuln/detail/CVE-2022-42003) |
| CVE-2022-42004 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42004](https://nvd.nist.gov/vuln/detail/CVE-2022-42004) |
| CVE-2022-45685 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-45685](https://nvd.nist.gov/vuln/detail/CVE-2022-45685) |
| CVE-2022-45688 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-45688](https://nvd.nist.gov/vuln/detail/CVE-2022-45688) |
| CVE-2022-45693 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-45693](https://nvd.nist.gov/vuln/detail/CVE-2022-45693) |
| CVE-2022-46751 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-46751](https://nvd.nist.gov/vuln/detail/CVE-2022-46751) |
| CVE-2023-1370 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-1370](https://nvd.nist.gov/vuln/detail/CVE-2023-1370) |
| CVE-2023-1436 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-1436](https://nvd.nist.gov/vuln/detail/CVE-2023-1436) |
| CVE-2023-20883 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-20883](https://nvd.nist.gov/vuln/detail/CVE-2023-20883) |
| CVE-2023-25194 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-25194](https://nvd.nist.gov/vuln/detail/CVE-2023-25194) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-34453 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-34453](https://nvd.nist.gov/vuln/detail/CVE-2023-34453) |
| CVE-2023-34454 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-34454](https://nvd.nist.gov/vuln/detail/CVE-2023-34454) |
| CVE-2023-34455 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-34455](https://nvd.nist.gov/vuln/detail/CVE-2023-34455) |
| CVE-2023-3635 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-3635](https://nvd.nist.gov/vuln/detail/CVE-2023-3635) |
| CVE-2023-39410 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-39410](https://nvd.nist.gov/vuln/detail/CVE-2023-39410) |
| CVE-2023-43642 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-43642](https://nvd.nist.gov/vuln/detail/CVE-2023-43642) |
| CVE-2023-44487 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-44487](https://nvd.nist.gov/vuln/detail/CVE-2023-44487) |
| CVE-2023-50387 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-50387](https://nvd.nist.gov/vuln/detail/CVE-2023-50387) |
| CVE-2023-5072 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-5072](https://nvd.nist.gov/vuln/detail/CVE-2023-5072) |
| CVE-2023-52428 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-52428](https://nvd.nist.gov/vuln/detail/CVE-2023-52428) |
| CVE-2023-6378 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-6378](https://nvd.nist.gov/vuln/detail/CVE-2023-6378) |
| CVE-2023-6481 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-6481](https://nvd.nist.gov/vuln/detail/CVE-2023-6481) |
| CVE-2024-21634 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-21634](https://nvd.nist.gov/vuln/detail/CVE-2024-21634) |
| CVE-2024-7254 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-7254](https://nvd.nist.gov/vuln/detail/CVE-2024-7254) |
| CVE-2009-2625 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2009-2625](https://nvd.nist.gov/vuln/detail/CVE-2009-2625) |
| CVE-2012-5783 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2012-5783](https://nvd.nist.gov/vuln/detail/CVE-2012-5783) |
| CVE-2012-6153 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2012-6153](https://nvd.nist.gov/vuln/detail/CVE-2012-6153) |
| CVE-2017-10355 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2017-10355](https://nvd.nist.gov/vuln/detail/CVE-2017-10355) |
| CVE-2018-10237 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2018-10237](https://nvd.nist.gov/vuln/detail/CVE-2018-10237) |
| CVE-2018-11798 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2018-11798](https://nvd.nist.gov/vuln/detail/CVE-2018-11798) |
| CVE-2018-1313 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2018-1313](https://nvd.nist.gov/vuln/detail/CVE-2018-1313) |
| CVE-2018-2799 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2018-2799](https://nvd.nist.gov/vuln/detail/CVE-2018-2799) |
| CVE-2019-10219 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2019-10219](https://nvd.nist.gov/vuln/detail/CVE-2019-10219) |
| CVE-2019-12384 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2019-12384](https://nvd.nist.gov/vuln/detail/CVE-2019-12384) |
| CVE-2019-12814 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2019-12814](https://nvd.nist.gov/vuln/detail/CVE-2019-12814) |
| CVE-2020-10693 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10693](https://nvd.nist.gov/vuln/detail/CVE-2020-10693) |
| CVE-2020-13955 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-13955](https://nvd.nist.gov/vuln/detail/CVE-2020-13955) |
| CVE-2020-13956 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-13956](https://nvd.nist.gov/vuln/detail/CVE-2020-13956) |
| CVE-2020-14338 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14338](https://nvd.nist.gov/vuln/detail/CVE-2020-14338) |
| CVE-2020-15250 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-15250](https://nvd.nist.gov/vuln/detail/CVE-2020-15250) |
| CVE-2020-15522 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-15522](https://nvd.nist.gov/vuln/detail/CVE-2020-15522) |
| CVE-2020-17521 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-17521](https://nvd.nist.gov/vuln/detail/CVE-2020-17521) |
| CVE-2020-1945 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-1945](https://nvd.nist.gov/vuln/detail/CVE-2020-1945) |
| CVE-2020-26939 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-26939](https://nvd.nist.gov/vuln/detail/CVE-2020-26939) |
| CVE-2020-29582 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-29582](https://nvd.nist.gov/vuln/detail/CVE-2020-29582) |
| CVE-2021-21290 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2021-21290](https://nvd.nist.gov/vuln/detail/CVE-2021-21290) |
| CVE-2021-21295 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2021-21295](https://nvd.nist.gov/vuln/detail/CVE-2021-21295) |
| CVE-2021-22569 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2021-22569](https://nvd.nist.gov/vuln/detail/CVE-2021-22569) |
| CVE-2021-22570 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2021-22570](https://nvd.nist.gov/vuln/detail/CVE-2021-22570) |
| CVE-2021-27568 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2021-27568](https://nvd.nist.gov/vuln/detail/CVE-2021-27568) |
| CVE-2021-28170 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2021-28170](https://nvd.nist.gov/vuln/detail/CVE-2021-28170) |
| CVE-2021-29425 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2021-29425](https://nvd.nist.gov/vuln/detail/CVE-2021-29425) |
| CVE-2021-36373 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2021-36373](https://nvd.nist.gov/vuln/detail/CVE-2021-36373) |
| CVE-2021-36374 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2021-36374](https://nvd.nist.gov/vuln/detail/CVE-2021-36374) |
| CVE-2021-37533 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2021-37533](https://nvd.nist.gov/vuln/detail/CVE-2021-37533) |
| CVE-2021-38153 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2021-38153](https://nvd.nist.gov/vuln/detail/CVE-2021-38153) |
| CVE-2022-23437 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2022-23437](https://nvd.nist.gov/vuln/detail/CVE-2022-23437) |
| CVE-2022-24329 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2022-24329](https://nvd.nist.gov/vuln/detail/CVE-2022-24329) |
| CVE-2022-38749 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2022-38749](https://nvd.nist.gov/vuln/detail/CVE-2022-38749) |
| CVE-2022-38750 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2022-38750](https://nvd.nist.gov/vuln/detail/CVE-2022-38750) |
| CVE-2022-38751 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2022-38751](https://nvd.nist.gov/vuln/detail/CVE-2022-38751) |
| CVE-2022-38752 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2022-38752](https://nvd.nist.gov/vuln/detail/CVE-2022-38752) |
| CVE-2022-41854 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2022-41854](https://nvd.nist.gov/vuln/detail/CVE-2022-41854) |
| CVE-2023-0833 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-0833](https://nvd.nist.gov/vuln/detail/CVE-2023-0833) |
| CVE-2023-20863 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-20863](https://nvd.nist.gov/vuln/detail/CVE-2023-20863) |
| CVE-2023-26049 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-26049](https://nvd.nist.gov/vuln/detail/CVE-2023-26049) |
| CVE-2023-33201 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-33201](https://nvd.nist.gov/vuln/detail/CVE-2023-33201) |
| CVE-2023-33202 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-33202](https://nvd.nist.gov/vuln/detail/CVE-2023-33202) |
| CVE-2023-34462 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-34462](https://nvd.nist.gov/vuln/detail/CVE-2023-34462) |
| CVE-2023-42503 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-42503](https://nvd.nist.gov/vuln/detail/CVE-2023-42503) |
| CVE-2023-51074 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-51074](https://nvd.nist.gov/vuln/detail/CVE-2023-51074) |
| CVE-2024-12798 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-12798](https://nvd.nist.gov/vuln/detail/CVE-2024-12798) |
| CVE-2024-25710 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-25710](https://nvd.nist.gov/vuln/detail/CVE-2024-25710) |
| CVE-2024-26308 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-26308](https://nvd.nist.gov/vuln/detail/CVE-2024-26308) |
| CVE-2024-38820 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-38820](https://nvd.nist.gov/vuln/detail/CVE-2024-38820) |
| CVE-2024-6763 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-6763](https://nvd.nist.gov/vuln/detail/CVE-2024-6763) |
| CVE-2024-8184 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-8184](https://nvd.nist.gov/vuln/detail/CVE-2024-8184) |
| CVE-2020-8908 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8908](https://nvd.nist.gov/vuln/detail/CVE-2020-8908) |
| CVE-2024-12801 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-12801](https://nvd.nist.gov/vuln/detail/CVE-2024-12801) |
| CVE-2023-50868 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-50868](https://nvd.nist.gov/vuln/detail/CVE-2023-50868) |
| CVE-2024-23454 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-23454](https://nvd.nist.gov/vuln/detail/CVE-2024-23454) |
| CVE-2024-23944 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-23944](https://nvd.nist.gov/vuln/detail/CVE-2024-23944) |
| CVE-2024-23945 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-23945](https://nvd.nist.gov/vuln/detail/CVE-2024-23945) |
| CVE-2024-25638 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-25638](https://nvd.nist.gov/vuln/detail/CVE-2024-25638) |
| CVE-2024-29025 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-29025](https://nvd.nist.gov/vuln/detail/CVE-2024-29025) |
| CVE-2024-29131 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-29131](https://nvd.nist.gov/vuln/detail/CVE-2024-29131) |
| CVE-2024-29133 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-29133](https://nvd.nist.gov/vuln/detail/CVE-2024-29133) |
| CVE-2024-29857 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-29857](https://nvd.nist.gov/vuln/detail/CVE-2024-29857) |
| CVE-2024-30171 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-30171](https://nvd.nist.gov/vuln/detail/CVE-2024-30171) |
| CVE-2024-31141 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-31141](https://nvd.nist.gov/vuln/detail/CVE-2024-31141) |
| CVE-2024-36114 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-36114](https://nvd.nist.gov/vuln/detail/CVE-2024-36114) |
| CVE-2024-38808 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-38808](https://nvd.nist.gov/vuln/detail/CVE-2024-38808) |
| CVE-2024-43382 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-43382](https://nvd.nist.gov/vuln/detail/CVE-2024-43382) |
| CVE-2024-47072 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-47072](https://nvd.nist.gov/vuln/detail/CVE-2024-47072) |
| CVE-2024-47535 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-47535](https://nvd.nist.gov/vuln/detail/CVE-2024-47535) |
| CVE-2024-47554 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-47554](https://nvd.nist.gov/vuln/detail/CVE-2024-47554) |
| CVE-2024-51504 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-51504](https://nvd.nist.gov/vuln/detail/CVE-2024-51504) |
| CVE-2024-56128 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-56128](https://nvd.nist.gov/vuln/detail/CVE-2024-56128) |
| CVE-2024-9823 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-9823](https://nvd.nist.gov/vuln/detail/CVE-2024-9823) |
## 7.6.0 릴리스 정보
다음 릴리스 정보에는 Amazon EMR 릴리스 7.6.0에 대한 정보가 포함되어 있습니다.
**새로운 기능**
+ **애플리케이션 업그레이드** – Amazon EMR 7.6.0 application upgrades include HBase 2.6.1, Flink 1.20.0, Spark 3.5.3, and Trino 457.
**알려진 문제**
+ 관리형 조정이 활성화되면 YARN ResourceManager(RM)에 심각한 교착 문제가 발생하여 동시 작업을 통해 **DECOMMISSIONING**에서 **DECOMMISSIONED** 상태로 전환할 때 응답하지 않습니다. 이 문제는 특히 대규모 클러스터 환경에서 발생합니다. 이 경우 노드 상태 전환과 애플리케이션 상태 전환 모두가 처리되지 않아 ResourceManager의 핵심 기능이 마비됩니다. 해결 방법은 프라이머리 노드에서 다음 명령을 사용하여 RM JVM을 다시 시작하는 것입니다.
```
sudo systemctl restart hadoop-yarn-resourcemanager
```
+ `CapacityScheduler` 또는 `FairScheduler` 이외의 YARN 스케줄러(예: FIFO 스케줄러)로 EMR 클러스터를 시작하면 `YARNMemoryAvailablePercentage` 지표가 CloudWatch로 푸시되지 않습니다. 이 문제는 관리형 확장 사용 클러스터의 다운스케일링에 영향을 줍니다. 그리고 `YARNMemoryAvailablePercentage` 지표에 따라 달라지는 경우 사용자 지정 관리 규모 조정에도 영향을 미칠 수 있습니다. 해결 방법으로 `CapacityScheduler` 또는 `FairScheduler`를 사용합니다.
+ **Glue 카탈로그를 사용하여 HBase 테이블을 Hive에 생성** - EMR-7.3.0에서 EMR-7.10.0으로의 Hive Iceberg 통합으로 인해 버그가 발생하여 Glue Data Catalog를 메타스토어로 사용할 때 Hive에서 HBase 테이블 생성이 실패합니다. 이 문제가 발생하면 AWS 지원 팀에 문의하십시오.
+ **Tez UI** - EMR-7.3에서 EMR-7.10까지, 전송 중 암호화가 활성화된 경우 YARN Resource Manager Web UI를 통해 Tez UI에 액세스하지 못하는 버그가 있습니다. 이 문제는 Tez UI에 HTTPS가 필요한 동안 YARN 프록시가 HTTP 프로토콜을 사용하려고 시도하기 때문에 발생합니다. 이 문제를 해결하려면 `tez-site`의 `tez.tez-ui.history-url.base` 구성을 `http`에서 `https`로 수정하세요.
**변경 사항, 향상된 기능 및 해결된 문제**
+ EMR 7.6.0부터, 단계 취소 프로세스는 이제 해당 단계가 취소될 때 해당 단계에서 생성된 모든 Hadoop YARN 애플리케이션이 종료되도록 합니다. 이 작업을 수행하면 클러스터 모드에서 실행되는 Spark 작업과 같은 애플리케이션을 보다 안정적으로 정리할 수 있습니다.
+ Spark 3.3.1(EMR 버전 6.10 이상에서 지원됨)부터 폐기 호스트의 모든 실행기는 *DECOMMISSIONING* 상태라는 새로운 `ExecutorState` 상태로 설정됩니다. Yarn은 폐기 중인 실행기를 사용하여 작업을 할당할 수 없으므로 필요한 경우 실행 중인 작업에 대해 새 실행기를 요청하세요. 따라서 EMR Managed Scaling, EMR Auto Scaling 또는 EMR-EC2 클러스터의 사용자 지정 조정 메커니즘을 사용하는 동안 Spark DRA를 비활성화하면 Yarn이 각 작업에 허용되는 최대 실행기를 요청할 수 있습니다. 이 문제를 방지하려면 위의 기능 조합을 사용할 때 `spark.dynamicAllocation.enabled` 속성을 `TRUE`(기본값)로 설정한 상태로 둡니다. 또한 Spark 작업의 `spark.dynamicAllocation.maxExecutors` 및 `spark.dynamicAllocation.minExecutors` 속성 값을 설정하여 작업 실행 중에 할당된 실행기 수를 제한하여 최소 및 최대 실행기 제약 조건을 설정할 수도 있습니다.
+ CloudWatch 에이전트는 EMR 7.6 이상의 런타임 역할 클러스터에서 지원됩니다. 자세한 내용은 [Amazon CloudWatch 에이전트](https://docs.aws.amazon.com/emr/latest/ReleaseGuide/emr-AmazonCloudWatchAgent.html)를 참조하세요.
+ Amazon Elastic Map Reduce(EMR) 릴리스 버전 7.6.0부터 Amazon S3A 파일 시스템 커넥터는 이제 Amazon S3 클라이언트 측 암호화를 지원합니다.
+ EMR 7.6.0부터, TLS는 HMaster 및 RegionServer 엔드포인트에서 지원됩니다. 자세한 내용은 HBase: [HBase](https://docs.aws.amazon.com/emr/latest/ManagementGuide/emr-encryption-support-matrix.html#emr-encryption-support-matrix-hbase)를 사용한 TLS 지원에 대한 다음 표를 참조하세요.
+
[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/ko_kr/emr/latest/ReleaseGuide/emr-760-release.html)
## 7.6.0 기본 Java 버전
Amazon EMR 릴리스 7.6 이상은 Apache Livy를 제외하고 Corretto 17(OpenJDK)을 지원하는 애플리케이션에 기본적으로 Amazon Corretto 17(OpenJDK 기반)과 함께 제공됩니다.
다음 표에는 Amazon EMR 7.6.0의 애플리케이션에 대한 기본 Java 버전이 나와 있습니다. 클러스터의 기본 JVM을 변경하려면 클러스터에서 실행되는 각 애플리케이션에 대해 [특정 Java 가상 머신을 사용하도록 애플리케이션 구성](configuring-java8.md)의 지침을 따릅니다. 클러스터에서는 Java 런타임 버전 1개만 사용할 수 있습니다. Amazon EMR은 동일한 클러스터에서 다양한 런타임 버전을 사용해 서로 다른 노드 또는 애플리케이션을 실행하는 것을 지원하지 않습니다.
| 애플리케이션 | Java 및 Amazon Corretto 버전(기본값은 굵은체로 표시) |
| --- | --- |
| 델타 | 17, 11, 8 |
| Flink | 17, 11, 8 |
| HBase | 17, 11, 8 |
| HCatalog | 17, 11, 8 |
| Hadoop | 17, 11, 8 |
| Hive | 17, 11, 8 |
| Hudi | 17, 11, 8 |
| Iceberg | 17, 11, 8 |
| Livy | 17, 11, 8 |
| Oozie | 17, 11, 8 |
| 피닉스 | 17, 11, 8 |
| PrestoDB | 8 |
| Spark | 17, 11, 8 |
| Spark RAPIDS | 17, 11, 8 |
| Tez의 Hive 실행 시간 비교 | 17, 11, 8 |
| Trino | 21, 17 |
| Zeppelin | 17, 11, 8 |
| Pig | 17, 11, 8 |
| Zookeeper | 17, 11, 8 |
## 7.6.0 구성 요소 버전
이 릴리스를 통해 Amazon EMR이 설치하는 구성 요소는 다음과 같습니다. 일부는 빅 데이터 애플리케이션 패키지의 일부로 설치됩니다. 나머지는 Amazon EMR에 고유하며 시스템 프로세스 및 기능을 위해 설치됩니다. 이는 일반적으로 `emr` 또는 `aws`로 시작됩니다. 최근 Amazon EMR 릴리스의 빅 데이터 애플리케이션 패키지는 일반적으로 커뮤니티에서 발견된 최신 버전입니다. 가능한 한 빨리 Amazon EMR에서 커뮤니티 릴리스를 제공합니다.
Amazon EMR의 일부 구성 요소는 커뮤니티 버전과 다릅니다. 이러한 구성 요소에는 `CommunityVersion-amzn-EmrVersion` 양식의 버전 레이블이 있습니다. `EmrVersion`은 0에서 시작합니다. 예를 들어, 버전 2.2의 `myapp-component`라는 오픈 소스 커뮤니티 구성 요소가 다른 Amazon EMR 릴리스에 포함되도록 세 번 수정된 경우 해당 릴리스 버전은 `2.2-amzn-2`로 나열됩니다.
| 구성 요소 | 버전 | 설명 |
| --- | --- | --- |
| adot-java-agent | 1.31.0 | 애플리케이션 대몬(daemon)에서 지표를 수집하는 Java 에이전트입니다. |
| delta | 3.2.1-amzn-1 | Delta Lake는 방대한 분석 데이터 세트를 위한 오픈 테이블 형식입니다. |
| emr-amazon-cloudwatch-agent | 1.300032.2-amzn-0 | Amazon EC2 인스턴스에서 내부 시스템 수준 지표와 사용자 지정 애플리케이션 지표를 수집하는 애플리케이션입니다. |
| emr-ddb | 5.6.0 | 하둡 에코시스템 애플리케이션용 Amazon DynamoDB 커넥터 |
| emr-goodies | 3.15.0 | 편리한 하둡 에코시스템용 추가 라이브러리 |
| emr-kinesis | 3.19.0 | 하둡 에코시스템 애플리케이션용 Amazon Kinesis 커넥터. |
| emr-notebook-env | 1.18.0 | Jupyter Enterprise Gateway가 포함된 EMR 노트북용 Conda 환경 |
| emr-s3-dist-cp | 2.36.0 | Amazon S3용으로 최적화된 분사 복사 애플리케이션. |
| emr-s3-select | 2.15.0 | EMR S3Select 커넥터 |
| emr-wal-cli | 1.3.1 | emrwal 목록/삭제에 사용되는 CLI입니다. |
| emrfs | 2.67.0 | 하둡 에코시스템 애플리케이션용 Amazon S3 커넥터. |
| flink-client | 1.20.0-amzn-0 | Apache Flink 명령줄 클라이언트 스크립트 및 애플리케이션 |
| flink-jobmanager-config | 1.20.0-amzn-0 | Apache Flink JobManager에 대한 EMR 노드에서 리소스를 관리합니다. |
| hadoop-client | 3.4.0-amzn-2 | 'hdfs', 'hadoop', 'yarn' 등과 같은 하둡 명령줄 클라이언트 |
| hadoop-hdfs-datanode | 3.4.0-amzn-2 | 블록을 저장하는 HDFS 노드 수준 서비스 |
| hadoop-hdfs-library | 3.4.0-amzn-2 | HDFS 명령줄 클라이언트 및 라이브러리 |
| hadoop-hdfs-namenode | 3.4.0-amzn-2 | 파일 이름 및 블록 위치를 추적하는 HDFS 서비스 |
| hadoop-hdfs-journalnode | 3.4.0-amzn-2 | HA 클러스터에서 하둡 파일 시스템 저널을 관리하기 위한 HDFS 서비스 |
| hadoop-httpfs-server | 3.4.0-amzn-2 | HDFS 작업에 대한 HTTP 엔드포인트 |
| hadoop-kms-server | 3.4.0-amzn-2 | 하둡의 KeyProvider API를 기반으로 하는 암호화 키 관리 서버 |
| hadoop-mapred | 3.4.0-amzn-2 | MapReduce 애플리케이션을 실행하는 MapReduce 실행 엔진 라이브러리 |
| hadoop-yarn-nodemanager | 3.4.0-amzn-2 | 개별 노드의 컨테이너를 관리하는 YARN 서비스 |
| hadoop-yarn-resourcemanager | 3.4.0-amzn-2 | 클러스터 리소스 및 분산 애플리케이션을 할당 및 관리하는 YARN 서비스 |
| hadoop-yarn-timeline-server | 3.4.0-amzn-2 | YARN 애플리케이션의 현재 및 기록 정보를 가져오는 서비스 |
| hbase-hmaster | 2.6.1-amzn-0 | 리전 조정 및 관리 명령의 실행을 담당하는 HBase 클러스터용 서비스 |
| hbase-region-server | 2.6.1-amzn-0 | 한 개 이상의 HBase 리전에 서비스를 제공하는 서비스 |
| hbase-client | 2.6.1-amzn-0 | HBase 명령줄 클라이언트 |
| hbase-rest-server | 2.6.1-amzn-0 | HBase용 RESTful HTTP 엔드포인트를 제공하는 서비스 |
| hbase-thrift-server | 2.6.1-amzn-0 | HBase에 Thrift 엔드포인트를 제공하는 서비스 |
| hbase-operator-tools | 2.6.1-amzn-0 | Apache HBase 클러스터용 복구 도구. |
| hcatalog-client | 3.1.3-amzn-15 | hcatalog-server를 조정하기 위한 'hcat' 명령줄 클라이언트 |
| hcatalog-server | 3.1.3-amzn-15 | 분산 애플리케이션용 스토리지 관리 계층, 테이블 및 HCatalog를 제공하는 서비스 |
| hcatalog-webhcat-server | 3.1.3-amzn-15 | HCatalog에 REST 인터페이스를 제공하는 HTTP 엔드포인트 |
| hive-client | 3.1.3-amzn-15 | Hive 명령줄 클라이언트 |
| hive-hbase | 3.1.3-amzn-15 | Hive-hbase 클라이언트 |
| hive-metastore-server | 3.1.3-amzn-15 | 하둡 작업에 대한 SQL용 메타데이터가 저장되는 시맨틱 리포지토리인 Hive 메타스토어에 액세스하기 위한 서비스 |
| hive-server2 | 3.1.3-amzn-15 | Hive 쿼리를 웹 요청으로 수락하기 위한 서비스 |
| hudi | 0.15.0-amzn-3 | 짧은 지연 시간 및 높은 효율성으로 데이터 파이프라인을 구동하는 증분 처리 프레임워크. |
| hudi-presto | 0.15.0-amzn-3 | Hudi로 Presto를 실행하기 위한 번들 라이브러리. |
| hudi-trino | 0.15.0-amzn-3 | Hudi와 함께 Trnio를 실행하기 위한 번들 라이브러리. |
| hudi-spark | 0.15.0-amzn-3 | Hudi와 함께 Spark를 실행하기 위한 번들 라이브러리. |
| hue-server | 4.11.0 | 하둡 에코시스템 애플리케이션을 사용하여 데이터를 분석하는 웹 애플리케이션. |
| iceberg | 1.6.1-amzn-2 | Apache Iceberg는 방대한 분석 데이터 세트를 위한 오픈 테이블 형식입니다. |
| jupyterhub | 1.5.0 | Jupyter Notebook용 다중 사용자 서버 |
| livy-server | 0.8.0-incubating | Apache Spark와 상호작용하기 위한 REST 인터페이스 |
| nginx | 1.12.1 | HTTP인 nginx [engine x] 및 역방향 프록시 서버 |
| mariadb-server | 5.5.68 이상 | MariaDB 데이터베이스 서버. |
| nvidia-cuda | 12.3.0 | Nvidia 드라이버와 Cuda 도구 키트 |
| oozie-client | 5.2.1 | Oozie 명령줄 클라이언트 |
| oozie-server | 5.2.1 | Oozie 워크플로 요청을 수락하는 서비스 |
| opencv | 4.7.0 | 오픈 소스 컴퓨터 비전 라이브러리. |
| phoenix-library | 5.2.0 | 서버 및 클라이언트의 phoenix 라이브러리 |
| phoenix-connectors | 6.0.0 | Spark-3용 Apache Phoenix 커넥터 |
| phoenix-query-server | 6.0.0 | Avatica API에 대한 JSON 형식 액세스 및 프로토콜 버퍼 액세스를 비롯하여 JDBC 액세스를 제공하는 경량 서버 |
| presto-coordinator | 0.287-amzn-1 | presto-worker의 쿼리를 수락하고 쿼리 실행을 관리하는 서비스. |
| presto-worker | 0.287-amzn-1 | 여러 쿼리를 실행하는 서비스. |
| presto-client | 0.287-amzn-1 | Presto 서버가 시작되지 않은 HA 클러스터의 대기 마스터에 설치된 Presto 명령줄 클라이언트. |
| trino-coordinator | 457-amzn-0 | trino-workers의 쿼리를 수락하고 쿼리 실행을 관리하는 서비스. |
| trino-worker | 457-amzn-0 | 여러 쿼리를 실행하는 서비스. |
| trino-client | 457-amzn-0 | Trino 서버가 시작되지 않은 HA 클러스터의 대기 마스터에 설치된 Trino 명령줄 클라이언트. |
| pig-client | 0.17.0 | Pig 명령줄 클라이언트. |
| r | 4.3.2 | 통계 컴퓨팅용 R 프로젝트 |
| ranger-kms-server | 2.0.0 | Apache Ranger 키 관리 시스템 |
| spark-client | 3.5.3-amzn-0 | Spark 명령줄 클라이언트. |
| spark-history-server | 3.5.3-amzn-0 | 완료된 Spark 애플리케이션의 수명에 대해 기록된 이벤트를 조회하는 웹 UI. |
| spark-on-yarn | 3.5.3-amzn-0 | YARN용 인 메모리 실행 엔진. |
| spark-yarn-slave | 3.5.3-amzn-0 | YARN 슬레이브에서 필요한 Apache Spark 라이브러리. |
| spark-rapids | 24.10.1-amzn-0 | GPU로 Apache Spark를 가속화하는 Nvidia Spark RAPIDS 플러그인. |
| tensorflow | 2.16.1 | TensorFlow는 고성능 수치 계산용 오픈 소스 소프트웨어 라이브러리입니다. |
| tez-on-yarn | 0.10.2-amzn-13 | tez YARN 애플리케이션 및 라이브러리. |
| tez-on-worker | 0.10.2-amzn-13 | 워커 노드에 대한 tez YARN 애플리케이션 및 라이브러리. |
| zeppelin-server | 0.11.1 | 대화형 데이터 분석이 가능한 웹 기반 노트북 |
| zookeeper-server | 3.9.2-amzn-0 | 구성 정보 유지 관리, 이름 지정, 분산 동기화 제공 및 그룹 서비스 제공을 위한 중앙 집중식 서비스. |
| zookeeper-client | 3.9.2-amzn-0 | ZooKeeper 명령줄 클라이언트. |
## 7.6.0 구성 분류
구성 분류를 사용하면 애플리케이션을 사용자 지정할 수 있습니다. 이는 종종 `hive-site.xml`과 같이 애플리케이션의 구성 XML 파일에 해당합니다. 자세한 내용은 [애플리케이션 구성](emr-configure-apps.md) 단원을 참조하십시오.
재구성 작업은 실행 중인 클러스터의 인스턴스 그룹에 대한 구성을 지정할 때 수행됩니다. Amazon EMR은 사용자가 수정한 분류에 대한 재구성 작업만 시작합니다. 자세한 내용은 [실행 중인 클러스터에서 인스턴스 그룹 재구성](emr-configure-apps-running-cluster.md) 단원을 참조하십시오.
**emr-7.6.0 분류**
| 분류 | 설명 | 재구성 작업 |
| --- | --- | --- |
| capacity-scheduler | Hadoop capacity-scheduler.xml 파일에서 값을 변경합니다. | Restarts the ResourceManager service. |
| container-executor | Hadoop YARN container-executor.cfg 파일에서 값을 변경합니다. | Not available. |
| container-log4j | Hadoop YARN container-log4j.properties 파일에서 값을 변경합니다. | Not available. |
| core-site | Hadoop core-site.xml 파일에서 값을 변경합니다. | Restarts the Hadoop HDFS services Namenode, SecondaryNamenode, Datanode, ZKFC, and Journalnode. Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts Hadoop KMS, Ranger KMS, HiveServer2, Hive MetaStore, Hadoop Httpfs, and MapReduce-HistoryServer. |
| docker-conf | Docker 관련 설정을 변경합니다. | Not available. |
| emrfs-site | EMRFS 설정을 변경합니다. | Restarts the Hadoop HDFS services Namenode, SecondaryNamenode, Datanode, ZKFC, and Journalnode. Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts HBaseRegionserver, HBaseMaster, HBaseThrift, HBaseRest, HiveServer2, Hive MetaStore, Hadoop Httpfs, and MapReduce-HistoryServer. |
| flink-conf | flink-conf.yaml 설정을 변경합니다. | Restarts Flink history server. |
| flink-log4j | Flink log4j.properties 설정을 변경합니다. | Restarts Flink history server. |
| flink-log4j-session | Kubernetes 및 Yarn 세션에 대한 Flink log4j-session.properties 설정을 변경합니다. | Restarts Flink history server. |
| flink-log4j-cli | Flink log4j-cli.properties 설정을 변경합니다. | Restarts Flink history server. |
| hadoop-env | 모든 Hadoop 구성 요소에 대한 Hadoop 환경에서 값을 변경합니다. | Restarts the Hadoop HDFS services Namenode, SecondaryNamenode, Datanode, ZKFC, and Journalnode. Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts PhoenixQueryserver, HiveServer2, Hive MetaStore, and MapReduce-HistoryServer. |
| hadoop-log4j | Hadoop log4j.properties 파일에서 값을 변경합니다. | Restarts the Hadoop HDFS services SecondaryNamenode, Datanode, and Journalnode. Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts Hadoop KMS, Hadoop Httpfs, and MapReduce-HistoryServer. |
| hadoop-ssl-server | hadoop ssl 서버 구성을 변경합니다. | Not available. |
| hadoop-ssl-client | hadoop ssl 클라이언트 구성을 변경합니다. | Not available. |
| hbase | Apache HBase에 대한 Amazon EMR 큐레이트 설정입니다. | Custom EMR specific property. Sets emrfs-site and hbase-site configs. See those for their associated restarts. |
| hbase-env | HBase 환경에서 값을 변경합니다. | Restarts the HBase services RegionServer, HBaseMaster, ThriftServer, RestServer. |
| hbase-log4j | HBase hbase-log4j.properties 파일에서 값을 변경합니다. | Restarts the HBase services RegionServer, HBaseMaster, ThriftServer, RestServer. |
| hbase-metrics | HBase hadoop-metrics2-hbase.properties 파일에서 값을 변경합니다. | Restarts the HBase services RegionServer, HBaseMaster, ThriftServer, RestServer. |
| hbase-policy | HBase hbase-policy.xml 파일에서 값을 변경합니다. | Not available. |
| hbase-site | HBase hbase-site.xml 파일에서 값을 변경합니다. | Restarts the HBase services RegionServer, HBaseMaster, ThriftServer, RestServer. Additionally restarts Phoenix QueryServer. |
| hdfs-encryption-zones | HDFS 암호화 영역을 구성합니다. | This classification should not be reconfigured. |
| hdfs-env | HDFS 환경에서 값을 변경합니다. | Restarts Hadoop HDFS services Namenode, Datanode, and ZKFC. |
| hdfs-site | HDFS hdfs-site.xml에서 값을 변경합니다. | Restarts the Hadoop HDFS services Namenode, SecondaryNamenode, Datanode, ZKFC, and Journalnode. Additionally restarts Hadoop Httpfs. |
| hcatalog-env | HCatalog 환경에서 값을 변경합니다. | Restarts Hive HCatalog Server. |
| hcatalog-server-jndi | HCatalog jndi.properties 환경에서 값을 변경합니다. | Restarts Hive HCatalog Server. |
| hcatalog-server-proto-hive-site | HCatalog proto-hive-site.xml에서 값을 변경합니다. | Restarts Hive HCatalog Server. |
| hcatalog-webhcat-env | HCatalog WebHCat 환경에서 값을 변경합니다. | Restarts Hive WebHCat server. |
| hcatalog-webhcat-log4j2 | HCatalog WebHCat log4j2.properties에서 값을 변경합니다. | Restarts Hive WebHCat server. |
| hcatalog-webhcat-site | HCatalog WebHCat webhcat-site.xml 파일에서 값을 변경합니다. | Restarts Hive WebHCat server. |
| hive | Apache Hive에 대한 Amazon EMR 큐레이트 설정입니다. | Sets configurations to launch Hive LLAP service. |
| hive-beeline-log4j2 | Hive beeline-log4j2.properties 파일에서 값을 변경합니다. | Not available. |
| hive-parquet-logging | Hive parquet-logging.properties 파일에서 값을 변경합니다. | Not available. |
| hive-env | Hive 환경에서 값을 변경합니다. | Restarts HiveServer2, HiveMetastore, and Hive HCatalog-Server. Runs Hive schemaTool CLI commands to verify hive-metastore. |
| hive-exec-log4j2 | Hive hive-exec-log4j2.properties 파일에서 값을 변경합니다. | Not available. |
| hive-llap-daemon-log4j2 | Hive llap-daemon-log4j2.properties 파일에서 값을 변경합니다. | Not available. |
| hive-log4j2 | Hive hive-log4j2.properties 파일에서 값을 변경합니다. | Not available. |
| hive-site | Hive hive-site.xml 파일에서 값을 변경합니다. | Restarts HiveServer2, HiveMetastore, and Hive HCatalog-Server. Runs Hive schemaTool CLI commands to verify hive-metastore. Also restarts Oozie and Zeppelin. |
| hiveserver2-site | Hive Server2 hiveserver2-site.xml 파일에서 값을 변경합니다. | Not available. |
| hue-ini | Hue ini 파일에서 값을 변경합니다. | Restarts Hue. Also activates Hue config override CLI commands to pick up new configurations. |
| httpfs-env | HTTPFS 환경에서 값을 변경합니다. | Restarts Hadoop Httpfs service. |
| httpfs-site | Hadoop httpfs-site.xml 파일에서 값을 변경합니다. | Restarts Hadoop Httpfs service. |
| hadoop-kms-acls | Hadoop kms-acls.xml 파일에서 값을 변경합니다. | Not available. |
| hadoop-kms-env | Hadoop KMS 환경에서 값을 변경합니다. | Restarts Hadoop-KMS service. |
| hadoop-kms-java-home | Hadoop의 KMS java 홈 변경 | Not available. |
| hadoop-kms-log4j | Hadoop kms-log4j.properties 파일에서 값을 변경합니다. | Not available. |
| hadoop-kms-site | Hadoop kms-site.xml 파일에서 값을 변경합니다. | Restarts Hadoop-KMS and Ranger-KMS service. |
| hudi-env | Hudi 환경에서 값을 변경합니다. | Not available. |
| hudi-defaults | Hudi hudi-defaults.conf 파일에서 값을 변경합니다. | Not available. |
| iceberg-defaults | Iceberg iceberg-defaults.conf 파일에서 값을 변경합니다. | Not available. |
| delta-defaults | Delta delta-defaults.conf 파일에서 값을 변경합니다. | Not available. |
| jupyter-notebook-conf | Jupyter Notebook jupyter\$1notebook\$1config.py 파일에서 값을 변경합니다. | Not available. |
| jupyter-hub-conf | JupyterHubs jupyterhub\$1config.py 파일에서 값을 변경합니다. | Not available. |
| jupyter-s3-conf | Jupyter Notebook S3 지속성 구성 | Not available. |
| jupyter-sparkmagic-conf | Sparkmagic config.json 파일에서 값을 변경합니다. | Not available. |
| livy-conf | Livy livy.conf 파일에서 값을 변경합니다. | Restarts Livy Server. |
| livy-env | Livy 환경에서 값을 변경합니다. | Restarts Livy Server. |
| livy-log4j2 | Livy log4j2.properties 설정을 변경합니다. | Restarts Livy Server. |
| mapred-env | MapReduce 애플리케이션 환경에서 값을 변경합니다. | Restarts Hadoop MapReduce-HistoryServer. |
| mapred-site | MapReduce 애플리케이션 mapred-site.xml 파일에서 값을 변경합니다. | Restarts Hadoop MapReduce-HistoryServer. |
| oozie-env | Oozie 환경에서 값을 변경합니다. | Restarts Oozie. |
| oozie-log4j | Oozie oozie-log4j.properties 파일에서 값을 변경합니다. | Restarts Oozie. |
| oozie-site | Oozie oozie-site.xml 파일에서 값을 변경합니다. | Restarts Oozie. |
| phoenix-hbase-metrics | Phoenix hadoop-metrics2-hbase.properties 파일에서 값을 변경합니다. | Not available. |
| phoenix-hbase-site | Phoenix hbase-site.xml 파일에서 값을 변경합니다. | Not available. |
| phoenix-log4j2 | Phoenix log4j2.properties 파일에서 값을 변경합니다. | Restarts Phoenix-QueryServer. |
| phoenix-metrics | Phoenix hadoop-metrics2-phoenix.properties 파일에서 값을 변경합니다. | Not available. |
| pig-env | Pig 환경에서 값을 변경합니다. | Not available. |
| pig-properties | Pig pig.properties 파일에서 값을 변경합니다. | Restarts Oozie. |
| pig-log4j | Pig log4j.properties 파일에서 값을 변경합니다. | Not available. |
| presto-log | Presto log.properties 파일에서 값을 변경합니다. | Restarts Presto-Server (for PrestoDB) |
| presto-config | Presto config.properties 파일에서 값을 변경합니다. | Restarts Presto-Server (for PrestoDB) |
| presto-password-authenticator | Presto password-authenticator.properties 파일에서 값을 변경합니다. | Not available. |
| presto-env | Presto presto-env.sh 파일에서 값을 변경합니다. | Restarts Presto-Server (for PrestoDB) |
| presto-node | Presto node.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-blackhole | Presto blackhole.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-cassandra | Presto cassandra.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-hive | Presto hive.properties 파일에서 값을 변경합니다. | Restarts Presto-Server (for PrestoDB) |
| presto-connector-jmx | Presto jmx.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-kafka | Presto kafka.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-lakeformation | Presto lakeformation.properties 파일에서 값을 변경합니다. | Restarts Presto-Server (for PrestoDB) |
| presto-connector-localfile | Presto localfile.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-memory | Presto memory.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-mongodb | Presto mongodb.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-mysql | Presto mysql.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-postgresql | Presto postgresql.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-raptor | Presto raptor.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-redis | Presto redis.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-redshift | Presto redshift.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-tpch | Presto tpch.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-tpcds | Presto tpcds.properties 파일에서 값을 변경합니다. | Not available. |
| trino-log | Trino log.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-config | Trino config.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-password-authenticator | Trino password-authenticator.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-env | Trino trino-env.sh 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-node | Trino node.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-blackhole | Trino blackhole.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-cassandra | Trino cassandra.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-delta | Trino delta.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-connector-hive | Trino hive.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-exchange-manager | Trino exchange-manager.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-connector-iceberg | Trino iceberg.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-connector-hudi | Trino hudi.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-connector-jmx | Trino jmx.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-kafka | Trino kafka.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-localfile | Trino localfile.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-memory | Trino memory.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-mongodb | Trino mongodb.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-mysql | Trino mysql.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-postgresql | Trino postgresql.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-raptor | Trino raptor.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-redis | Trino redis.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-redshift | Trino redshift.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-tpch | Trino tpch.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-tpcds | Trino tpcds.properties 파일에서 값을 변경합니다. | Not available. |
| ranger-kms-dbks-site | Ranger KMS dbks-site.xml 파일에서 값을 변경합니다. | Restarts Ranger KMS Server. |
| ranger-kms-site | Ranger KMS ranger-kms-site.xml 파일에서 값을 변경합니다. | Restarts Ranger KMS Server. |
| ranger-kms-env | Ranger KMS 환경에서 값을 변경합니다. | Restarts Ranger KMS Server. |
| ranger-kms-logback | Ranger KMS kms-logback.xml 파일에서 값을 변경합니다. | Not available. |
| ranger-kms-db-ca | Ranger KMS와의 MySQL SSL 연결에서 CA 파일의 값을 변경합니다. | Not available. |
| spark | Apache Spark에 대한 Amazon EMR 큐레이트 설정입니다. | This property modifies spark-defaults. See actions there. |
| spark-defaults | Spark spark-defaults.conf 파일에서 값을 변경합니다. | Restarts Spark history server and Spark thrift server. |
| spark-env | Spark 환경에서 값을 변경합니다. | Restarts Spark history server and Spark thrift server. |
| spark-hive-site | Spark hive-site.xml 파일에서 값을 변경합니다. | Not available. |
| spark-log4j2 | Spark log4j2.properties 파일에서 값을 변경합니다. | Restarts Spark history server and Spark thrift server. |
| spark-metrics | Spark metrics.properties 파일에서 값을 변경합니다. | Restarts Spark history server and Spark thrift server. |
| tez-site | Tez tez-site.xml 파일에서 값을 변경합니다. | Restart Oozie and HiveServer2. |
| yarn-env | YARN 환경에서 값을 변경합니다. | Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts MapReduce-HistoryServer. |
| yarn-site | YARN yarn-site.xml 파일에서 값을 변경합니다. | Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts Livy Server and MapReduce-HistoryServer. |
| zeppelin-env | Zeppelin 환경에서 값을 변경합니다. | Restarts Zeppelin. |
| zeppelin-site | zeppelin-site.xml에서 구성 설정을 변경합니다. | Restarts Zeppelin. |
| zookeeper-config | ZooKeeper zoo.cfg 파일에서 값을 변경합니다. | Restarts Zookeeper server. |
| zookeeper-logback | ZooKeeper logback.xml 파일에서 값을 변경합니다. | Restarts Zookeeper server. |
| emr-metrics | 이 노드에 대한 emr 지표 설정을 변경합니다. | Restarts the CloudWatchAgent service. |
## 7.6.0 변경 로그
**7.6.0 릴리스 및 릴리스 정보에 대한 변경 로그**
| Date | 이벤트 | 설명 |
| --- | --- | --- |
| 2025-01-13 | 문서 게시 | Amazon EMR 7.6.0 릴리스 정보 최초 게시 |
| 2025-01-10 | 배포 완료 | [지원되는 모든 리전](https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/)에 Amazon EMR 7.6.0 완전 배포 |
| 2025-12-26 | 초기 릴리스 | Amazon EMR 7.6.0이 초기 상용 리전에 처음 배포됨 |
# Amazon EMR 릴리스 7.5.0
## 7.5.0 지원 수명 주기
다음 표에서는 Amazon EMR 릴리스 7.5.0에 지원되는 수명 주기 날짜를 설명합니다.
| 지원 단계 | Date |
| --- | --- |
| 초기 릴리스 날짜 | 2024년 11월 21일 |
| 표준 지원 종료 시점 | 2026년 11월 20일 |
| 지원 종료 | 2026년 11월 21일 |
| 수명 종료 | 2027년 11월 21일 |
## 7.5.0 애플리케이션 버전
이 릴리스에 포함된 애플리케이션은 [https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Install-CloudWatch-Agent.html](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Install-CloudWatch-Agent.html), [https://delta.io/](https://delta.io/), [https://flink.apache.org/](https://flink.apache.org/), [http://hbase.apache.org/](http://hbase.apache.org/), [https://cwiki.apache.org/confluence/display/Hive/HCatalog](https://cwiki.apache.org/confluence/display/Hive/HCatalog), [http://hadoop.apache.org/docs/current/](http://hadoop.apache.org/docs/current/), [http://hive.apache.org/](http://hive.apache.org/), [https://hudi.apache.org](https://hudi.apache.org), [http://gethue.com/](http://gethue.com/), [https://iceberg.apache.org/](https://iceberg.apache.org/), [https://jupyter-enterprise-gateway.readthedocs.io/en/latest/](https://jupyter-enterprise-gateway.readthedocs.io/en/latest/), [https://jupyterhub.readthedocs.io/en/latest/#](https://jupyterhub.readthedocs.io/en/latest/#), [https://livy.incubator.apache.org/](https://livy.incubator.apache.org/), [http://oozie.apache.org/](http://oozie.apache.org/), [https://phoenix.apache.org/](https://phoenix.apache.org/), [http://pig.apache.org/](http://pig.apache.org/), [https://prestodb.io/](https://prestodb.io/), [https://spark.apache.org/docs/latest/](https://spark.apache.org/docs/latest/), [https://www.tensorflow.org/](https://www.tensorflow.org/), [https://tez.apache.org/](https://tez.apache.org/), [https://trino.io/](https://trino.io/), [https://zeppelin.incubator.apache.org/](https://zeppelin.incubator.apache.org/), [https://zookeeper.apache.org](https://zookeeper.apache.org)입니다.
아래 테이블에는 이번 Amazon EMR 릴리스에서 사용할 수 있는 애플리케이션 버전과 이전 세 가지 Amazon EMR 릴리스(해당하는 경우)의 애플리케이션 버전이 나와 있습니다.
각 Amazon EMR 릴리스에서 애플리케이션 버전의 전체 기록은 다음 주제를 참조하세요.
+ [Amazon EMR 7.x 릴리스의 애플리케이션 버전](emr-release-app-versions-7.x.md)
+ [Amazon EMR 6.x 릴리스의 애플리케이션 버전](emr-release-app-versions-6.x.md)
+ [Amazon EMR 5.x 릴리스의 애플리케이션 버전](emr-release-app-versions-5.x.md)
+ [Amazon EMR 4.x 릴리스의 애플리케이션 버전](emr-release-app-versions-4.x.md)
**애플리케이션 버전 정보**
| | emr-7.5.0 | emr-7.4.0 | emr-7.3.0 | emr-7.2.0 |
| --- | --- | --- | --- | --- |
| AWS Java용 SDK | 2.28.8, 1.12.772 | 2.28.8, 1.12.772 | 2.25.70, 1.12.747 | 2.23.18, 1.12.705 |
| Python | 3.9, 3.11 | 3.9, 3.11 | 3.9, 3.11 | 3.9, 3.11 |
| Scala | 2.12.18 | 2.12.18 | 2.12.18 | 2.12.17 |
| AmazonCloudWatchAgent | 1.300032.2-amzn-0 | 1.300032.2-amzn-0 | 1.300032.2-amzn-0 | 1.300032.2-amzn-0 |
| Delta | 3.2.1-amzn-0 | 3.2.0-amzn-1 | 3.2.0-amzn-0 | 3.1.0 |
| Flink | 1.19.1-amzn-1 | 1.19.1-amzn-0 | 1.18.1-amzn-2 | 1.18.1-amzn-1 |
| Ganglia | - | - | - | - |
| HBase | 2.5.10-amzn-0 | 2.5.5-amzn-0 | 2.4.17-amzn-7 | 2.4.17-amzn-6 |
| HCatalog | 3.1.3-amzn-14 | 3.1.3-amzn-13 | 3.1.3-amzn-12 | 3.1.3-amzn-11 |
| Hadoop | 3.4.0-amzn-1 | 3.4.0-amzn-0 | 3.3.6-amzn-5 | 3.3.6-amzn-4 |
| Hive | 3.1.3-amzn-14 | 3.1.3-amzn-13 | 3.1.3-amzn-12 | 3.1.3-amzn-11 |
| Hudi | 0.15.0-amzn-2 | 0.15.0-amzn-1 | 0.15.0-amzn-0 | 0.14.1-amzn-1 |
| Hue | 4.11.0 | 4.11.0 | 4.11.0 | 4.11.0 |
| Iceberg | 1.6.1-amzn-1 | 1.6.1-amzn-0 | 1.5.2-amzn-0 | 1.5.0-amzn-0 |
| JupyterEnterpriseGateway | 2.6.0 | 2.6.0 | 2.6.0 | 2.6.0 |
| JupyterHub | 1.5.0 | 1.5.0 | 1.5.0 | 1.5.0 |
| Livy | 0.8.0-incubating | 0.8.0-incubating | 0.8.0-incubating | 0.8.0-incubating |
| MXNet | - | - | - | 1.9.1 |
| Mahout | - | - | - | - |
| Oozie | 5.2.1 | 5.2.1 | 5.2.1 | 5.2.1 |
| Phoenix | 5.2.0 | 5.2.0 | 5.1.3 | 5.1.3 |
| Pig | 0.17.0 | 0.17.0 | 0.17.0 | 0.17.0 |
| Presto | 0.287-amzn-0 | 0.287-amzn-0 | 0.285-amzn-1 | 0.285-amzn-0 |
| Spark | 3.5.2-amzn-1 | 3.5.2-amzn-0 | 3.5.1-amzn-1 | 3.5.1-amzn-0 |
| Sqoop | - | 1.4.7 | 1.4.7 | 1.4.7 |
| TensorFlow | 2.16.1 | 2.16.1 | 2.16.1 | 2.11.0 |
| Tez | 0.10.2-amzn-12 | 0.10.2-amzn-11 | 0.10.2-amzn-10 | 0.10.2-amzn-9 |
| Trino (PrestoSQL) | 446-amzn-0 | 446-amzn-0 | 442-amzn-0 | 436-amzn-0 |
| Zeppelin | 0.11.1 | 0.11.1 | 0.11.1 | 0.10.1 |
| ZooKeeper | 3.9.2-amzn-0 | 3.9.2-amzn-0 | 3.9.1-amzn-1 | 3.9.1-amzn-1 |
# 7.5.0 릴리스 구성 요소 세부 정보
Amazon EMR 7.5.0의 *추가* 패키지에 대한 자세한 내용은 다음 표를 참조하세요.
| 애플리케이션 | 애플리케이션 유형 | 패키지 | 패키지 유형 | 패키지 버전 |
| --- | --- | --- | --- | --- |
| AmazonCloudWatchAgent | Core | hadoop-hdfs-journalnode | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| AmazonCloudWatchAgent | Core | ranger-kms | 추가 항목 | 2.0.0-1.amzn2023 |
| AmazonCloudWatchAgent | Core | s3-dist-cp | 추가 항목 | 2.33.0-1.amzn2023 |
| AmazonCloudWatchAgent | Core | zookeeper | 추가 항목 | 3.9.1.amzn.1-1.amzn2023 |
| AmazonCloudWatchAgent | Core | zookeeper-server | 추가 항목 | 3.9.1.amzn.1-1.amzn2023 |
| Flink | Core | hadoop-client | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Flink | Core | hadoop-hdfs | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Flink | Core | hadoop-hdfs-datanode | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Flink | Core | hadoop-hdfs-journalnode | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Flink | Core | hadoop-hdfs-namenode | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Flink | Core | hadoop-httpfs | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Flink | Core | hadoop-kms | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Flink | Core | hadoop-mapreduce | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Flink | Core | hadoop-mapreduce-historyserver | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Flink | Core | hadoop-yarn | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Flink | Core | hadoop-yarn-nodemanager | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Flink | Core | hadoop-yarn-proxyserver | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Flink | Core | hadoop-yarn-resourcemanager | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Flink | Core | hadoop-yarn-timelineserver | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Flink | Core | hudi | 추가 항목 | 0.15.0.amzn.0-1.amzn2023 |
| Flink | Core | ranger-kms | 추가 항목 | 2.0.0-1.amzn2023 |
| Flink | Core | hadoop | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| HBase | Core | s3-dist-cp | 추가 항목 | 2.33.0-1.amzn2023 |
| HCatalog | Core | hadoop-yarn-proxyserver | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| HCatalog | Core | mariadb-connector-java | 추가 항목 | |
| Hive | Core | hadoop-httpfs | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Hive | Core | hadoop-yarn-proxyserver | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Hive | Core | hive-hbase | 추가 항목 | 3.1.3.amzn.12-1.amzn2023 |
| Hive | Core | mariadb-connector-java | 추가 항목 | 2.7.2-1 |
| Hive | Core | s3-dist-cp | 추가 항목 | 2.33.0-1.amzn2023 |
| 피닉스 | Core | s3-dist-cp | 추가 항목 | 2.33.0-1.amzn2023 |
| Spark | Core | spark-datanucleus | 추가 항목 | 3.5.1.amzn.0-1.amzn2023 |
| Tez의 Hive 실행 시간 비교 | Core | hadoop-mapreduce | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Tez의 Hive 실행 시간 비교 | Core | hadoop-mapreduce-historyserver | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Tez의 Hive 실행 시간 비교 | Core | hadoop-yarn-proxyserver | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Trino | Core | bigtop-utils | 추가 항목 | 1.2.0-1.amzn2023 |
| Trino | Core | hadoop-client | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Trino | Core | hadoop-hdfs | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Trino | Core | hadoop-hdfs-datanode | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Trino | Core | hadoop-hdfs-journalnode | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Trino | Core | hadoop-hdfs-namenode | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Trino | Core | hadoop-kms | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Trino | Core | hadoop-mapreduce | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Trino | Core | hadoop-mapreduce-historyserver | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Trino | Core | hadoop-yarn | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Trino | Core | hadoop-yarn-nodemanager | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Trino | Core | hadoop-yarn-proxyserver | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Trino | Core | hadoop-yarn-resourcemanager | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Trino | Core | hadoop-yarn-timelineserver | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Trino | Core | hive | 추가 항목 | 3.1.3.amzn.12-1.amzn2023 |
| Trino | Core | hive-hcatalog-server | 추가 항목 | 3.1.3.amzn.12-1.amzn2023 |
| Trino | Core | mariadb-connector-java | 추가 항목 | 2.7.2-1 |
| Trino | Core | ranger-kms | 추가 항목 | 2.0.0-1.amzn2023 |
| Trino | Core | zookeeper | 추가 항목 | 3.9.1.amzn.1-1.amzn2023 |
| Trino | Core | zookeeper-server | 추가 항목 | 3.9.1.amzn.1-1.amzn2023 |
| Trino | Core | bigtop-groovy | 추가 항목 | 2.5.4-1.amzn2023 |
| Trino | Core | bigtop-jsvc | 추가 항목 | 1.2.4-1.amzn2023 |
| Trino | Core | hadoop | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Trino | Core | hadoop-lzo | 추가 항목 | 0.4.19-1.amzn2023 |
| Trino | Core | hive-hcatalog | 추가 항목 | 3.1.3.amzn.12-1.amzn2023 |
| Trino | Core | hive-jdbc | 추가 항목 | 3.1.3.amzn.12-1.amzn2023 |
| Zookeeper | Core | emrfs | 추가 항목 | 2.64.0-1.amzn2023 |
| Zookeeper | Core | hadoop-client | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Zookeeper | Core | hadoop-hdfs | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Zookeeper | Core | hadoop-hdfs-datanode | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Zookeeper | Core | hadoop-hdfs-journalnode | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Zookeeper | Core | hadoop-hdfs-namenode | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Zookeeper | Core | hadoop-httpfs | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Zookeeper | Core | hadoop-kms | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Zookeeper | Core | hadoop-mapreduce | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Zookeeper | Core | hadoop-mapreduce-historyserver | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Zookeeper | Core | hadoop-yarn | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Zookeeper | Core | hadoop-yarn-nodemanager | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Zookeeper | Core | hadoop-yarn-proxyserver | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Zookeeper | Core | hadoop-yarn-resourcemanager | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Zookeeper | Core | hadoop-yarn-timelineserver | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Zookeeper | Core | ranger-kms | 추가 항목 | 2.0.0-1.amzn2023 |
# 7.5.0 일반적인 취약성 및 노출
다음 표에는 Amazon EMR 7.5.0의 권장 구성에서 실행되는 EMR 클러스터에 영향을 주지 않는 모든 CVEs가 나열되어 있습니다. Amazon EMR은 업스트림 오픈 소스의 수정 사항 가용성에 종속되어 있으며, Amazon EMR이 수정 사항을 확인한 후 90일 이내에 코어 엔진 구성 요소의 일부로 안정적인 최신 버전을 제공합니다.
이 표는 2021년 11월 23일에 업데이트되었습니다.
| CVE ID | 심각도 | CVE 세부 정보 URL |
| --- | --- | --- |
| CVE-2013-4002 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2013-4002](https://nvd.nist.gov/vuln/detail/CVE-2013-4002) |
| CVE-2015-1832 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2015-1832](https://nvd.nist.gov/vuln/detail/CVE-2015-1832) |
| CVE-2018-12022 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-12022](https://nvd.nist.gov/vuln/detail/CVE-2018-12022) |
| CVE-2018-14718 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-14718](https://nvd.nist.gov/vuln/detail/CVE-2018-14718) |
| CVE-2019-12384 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-12384](https://nvd.nist.gov/vuln/detail/CVE-2019-12384) |
| CVE-2019-14379 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14379](https://nvd.nist.gov/vuln/detail/CVE-2019-14379) |
| CVE-2019-14439 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14439](https://nvd.nist.gov/vuln/detail/CVE-2019-14439) |
| CVE-2020-10672 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10672](https://nvd.nist.gov/vuln/detail/CVE-2020-10672) |
| CVE-2020-10673 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10673](https://nvd.nist.gov/vuln/detail/CVE-2020-10673) |
| CVE-2020-11112 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11112](https://nvd.nist.gov/vuln/detail/CVE-2020-11112) |
| CVE-2020-13949 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-13949](https://nvd.nist.gov/vuln/detail/CVE-2020-13949) |
| CVE-2020-14195 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14195](https://nvd.nist.gov/vuln/detail/CVE-2020-14195) |
| CVE-2020-17521 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-17521](https://nvd.nist.gov/vuln/detail/CVE-2020-17521) |
| CVE-2020-24616 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-24616](https://nvd.nist.gov/vuln/detail/CVE-2020-24616) |
| CVE-2020-24750 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-24750](https://nvd.nist.gov/vuln/detail/CVE-2020-24750) |
| CVE-2020-25649 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-25649](https://nvd.nist.gov/vuln/detail/CVE-2020-25649) |
| CVE-2020-36183 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36183](https://nvd.nist.gov/vuln/detail/CVE-2020-36183) |
| CVE-2020-36186 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36186](https://nvd.nist.gov/vuln/detail/CVE-2020-36186) |
| CVE-2020-36188 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36188](https://nvd.nist.gov/vuln/detail/CVE-2020-36188) |
| CVE-2020-36189 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36189](https://nvd.nist.gov/vuln/detail/CVE-2020-36189) |
| CVE-2020-8908 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8908](https://nvd.nist.gov/vuln/detail/CVE-2020-8908) |
| CVE-2021-37137 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2021-37137](https://nvd.nist.gov/vuln/detail/CVE-2021-37137) |
| CVE-2021-38153 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2021-38153](https://nvd.nist.gov/vuln/detail/CVE-2021-38153) |
| CVE-2022-25857 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-25857](https://nvd.nist.gov/vuln/detail/CVE-2022-25857) |
| CVE-2022-3509 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3509](https://nvd.nist.gov/vuln/detail/CVE-2022-3509) |
| CVE-2022-37866 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-37866](https://nvd.nist.gov/vuln/detail/CVE-2022-37866) |
| CVE-2022-41966 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-41966](https://nvd.nist.gov/vuln/detail/CVE-2022-41966) |
| CVE-2022-45688 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-45688](https://nvd.nist.gov/vuln/detail/CVE-2022-45688) |
| CVE-2023-34455 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2023-34455](https://nvd.nist.gov/vuln/detail/CVE-2023-34455) |
| CVE-2023-3635 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2023-3635](https://nvd.nist.gov/vuln/detail/CVE-2023-3635) |
| CVE-2023-38647 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2023-38647](https://nvd.nist.gov/vuln/detail/CVE-2023-38647) |
| CVE-2023-40167 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2023-40167](https://nvd.nist.gov/vuln/detail/CVE-2023-40167) |
| CVE-2023-43642 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2023-43642](https://nvd.nist.gov/vuln/detail/CVE-2023-43642) |
| CVE-2023-44981 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2023-44981](https://nvd.nist.gov/vuln/detail/CVE-2023-44981) |
| CVE-2023-50387 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2023-50387](https://nvd.nist.gov/vuln/detail/CVE-2023-50387) |
| CVE-2024-23454 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2024-23454](https://nvd.nist.gov/vuln/detail/CVE-2024-23454) |
| CVE-2024-29025 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2024-29025](https://nvd.nist.gov/vuln/detail/CVE-2024-29025) |
| CVE-2024-36124 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2024-36124](https://nvd.nist.gov/vuln/detail/CVE-2024-36124) |
| CVE-2024-8184 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2024-8184](https://nvd.nist.gov/vuln/detail/CVE-2024-8184) |
| CVE-2012-0881 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2012-0881](https://nvd.nist.gov/vuln/detail/CVE-2012-0881) |
| CVE-2012-5783 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2012-5783](https://nvd.nist.gov/vuln/detail/CVE-2012-5783) |
| CVE-2015-5237 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2015-5237](https://nvd.nist.gov/vuln/detail/CVE-2015-5237) |
| CVE-2016-5018 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2016-5018](https://nvd.nist.gov/vuln/detail/CVE-2016-5018) |
| CVE-2016-6796 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2016-6796](https://nvd.nist.gov/vuln/detail/CVE-2016-6796) |
| CVE-2017-15095 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2017-15095](https://nvd.nist.gov/vuln/detail/CVE-2017-15095) |
| CVE-2018-1000180 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-1000180](https://nvd.nist.gov/vuln/detail/CVE-2018-1000180) |
| CVE-2018-10054 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-10054](https://nvd.nist.gov/vuln/detail/CVE-2018-10054) |
| CVE-2018-10237 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-10237](https://nvd.nist.gov/vuln/detail/CVE-2018-10237) |
| CVE-2018-11798 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-11798](https://nvd.nist.gov/vuln/detail/CVE-2018-11798) |
| CVE-2018-12023 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-12023](https://nvd.nist.gov/vuln/detail/CVE-2018-12023) |
| CVE-2018-14721 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-14721](https://nvd.nist.gov/vuln/detail/CVE-2018-14721) |
| CVE-2018-19361 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-19361](https://nvd.nist.gov/vuln/detail/CVE-2018-19361) |
| CVE-2018-5968 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-5968](https://nvd.nist.gov/vuln/detail/CVE-2018-5968) |
| CVE-2018-7489 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-7489](https://nvd.nist.gov/vuln/detail/CVE-2018-7489) |
| CVE-2019-0205 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-0205](https://nvd.nist.gov/vuln/detail/CVE-2019-0205) |
| CVE-2019-12086 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-12086](https://nvd.nist.gov/vuln/detail/CVE-2019-12086) |
| CVE-2019-12814 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-12814](https://nvd.nist.gov/vuln/detail/CVE-2019-12814) |
| CVE-2019-14540 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14540](https://nvd.nist.gov/vuln/detail/CVE-2019-14540) |
| CVE-2019-14892 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14892](https://nvd.nist.gov/vuln/detail/CVE-2019-14892) |
| CVE-2019-14893 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14893](https://nvd.nist.gov/vuln/detail/CVE-2019-14893) |
| CVE-2019-16869 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-16869](https://nvd.nist.gov/vuln/detail/CVE-2019-16869) |
| CVE-2019-16942 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-16942](https://nvd.nist.gov/vuln/detail/CVE-2019-16942) |
| CVE-2019-17267 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-17267](https://nvd.nist.gov/vuln/detail/CVE-2019-17267) |
| CVE-2019-17531 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-17531](https://nvd.nist.gov/vuln/detail/CVE-2019-17531) |
| CVE-2019-20330 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-20330](https://nvd.nist.gov/vuln/detail/CVE-2019-20330) |
| CVE-2019-20444 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-20444](https://nvd.nist.gov/vuln/detail/CVE-2019-20444) |
| CVE-2019-20445 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-20445](https://nvd.nist.gov/vuln/detail/CVE-2019-20445) |
| CVE-2020-10969 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10969](https://nvd.nist.gov/vuln/detail/CVE-2020-10969) |
| CVE-2020-11111 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11111](https://nvd.nist.gov/vuln/detail/CVE-2020-11111) |
| CVE-2020-11619 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11619](https://nvd.nist.gov/vuln/detail/CVE-2020-11619) |
| CVE-2020-11620 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11620](https://nvd.nist.gov/vuln/detail/CVE-2020-11620) |
| CVE-2020-13955 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-13955](https://nvd.nist.gov/vuln/detail/CVE-2020-13955) |
| CVE-2020-13956 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-13956](https://nvd.nist.gov/vuln/detail/CVE-2020-13956) |
| CVE-2020-14060 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14060](https://nvd.nist.gov/vuln/detail/CVE-2020-14060) |
| CVE-2020-14061 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14061](https://nvd.nist.gov/vuln/detail/CVE-2020-14061) |
| CVE-2020-15250 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-15250](https://nvd.nist.gov/vuln/detail/CVE-2020-15250) |
| CVE-2020-26939 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-26939](https://nvd.nist.gov/vuln/detail/CVE-2020-26939) |
| CVE-2020-35491 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-35491](https://nvd.nist.gov/vuln/detail/CVE-2020-35491) |
| CVE-2020-35728 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-35728](https://nvd.nist.gov/vuln/detail/CVE-2020-35728) |
| CVE-2020-36179 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36179](https://nvd.nist.gov/vuln/detail/CVE-2020-36179) |
| CVE-2020-36181 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36181](https://nvd.nist.gov/vuln/detail/CVE-2020-36181) |
| CVE-2020-36182 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36182](https://nvd.nist.gov/vuln/detail/CVE-2020-36182) |
| CVE-2020-36184 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36184](https://nvd.nist.gov/vuln/detail/CVE-2020-36184) |
| CVE-2020-36185 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36185](https://nvd.nist.gov/vuln/detail/CVE-2020-36185) |
| CVE-2020-36187 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36187](https://nvd.nist.gov/vuln/detail/CVE-2020-36187) |
| CVE-2020-36518 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36518](https://nvd.nist.gov/vuln/detail/CVE-2020-36518) |
| CVE-2020-8840 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8840](https://nvd.nist.gov/vuln/detail/CVE-2020-8840) |
| CVE-2020-9546 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-9546](https://nvd.nist.gov/vuln/detail/CVE-2020-9546) |
| CVE-2020-9547 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-9547](https://nvd.nist.gov/vuln/detail/CVE-2020-9547) |
| CVE-2020-9548 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-9548](https://nvd.nist.gov/vuln/detail/CVE-2020-9548) |
| CVE-2021-20190 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-20190](https://nvd.nist.gov/vuln/detail/CVE-2021-20190) |
| CVE-2021-21290 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-21290](https://nvd.nist.gov/vuln/detail/CVE-2021-21290) |
| CVE-2021-22569 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-22569](https://nvd.nist.gov/vuln/detail/CVE-2021-22569) |
| CVE-2021-28170 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-28170](https://nvd.nist.gov/vuln/detail/CVE-2021-28170) |
| CVE-2021-29425 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-29425](https://nvd.nist.gov/vuln/detail/CVE-2021-29425) |
| CVE-2021-31684 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-31684](https://nvd.nist.gov/vuln/detail/CVE-2021-31684) |
| CVE-2021-34538 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-34538](https://nvd.nist.gov/vuln/detail/CVE-2021-34538) |
| CVE-2021-36374 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-36374](https://nvd.nist.gov/vuln/detail/CVE-2021-36374) |
| CVE-2021-37533 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-37533](https://nvd.nist.gov/vuln/detail/CVE-2021-37533) |
| CVE-2021-43859 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-43859](https://nvd.nist.gov/vuln/detail/CVE-2021-43859) |
| CVE-2022-1415 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-1415](https://nvd.nist.gov/vuln/detail/CVE-2022-1415) |
| CVE-2022-1471 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-1471](https://nvd.nist.gov/vuln/detail/CVE-2022-1471) |
| CVE-2022-3171 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3171](https://nvd.nist.gov/vuln/detail/CVE-2022-3171) |
| CVE-2022-3510 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3510](https://nvd.nist.gov/vuln/detail/CVE-2022-3510) |
| CVE-2022-36364 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-36364](https://nvd.nist.gov/vuln/detail/CVE-2022-36364) |
| CVE-2022-37865 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-37865](https://nvd.nist.gov/vuln/detail/CVE-2022-37865) |
| CVE-2022-38749 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-38749](https://nvd.nist.gov/vuln/detail/CVE-2022-38749) |
| CVE-2022-38751 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-38751](https://nvd.nist.gov/vuln/detail/CVE-2022-38751) |
| CVE-2022-40150 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-40150](https://nvd.nist.gov/vuln/detail/CVE-2022-40150) |
| CVE-2022-40151 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-40151](https://nvd.nist.gov/vuln/detail/CVE-2022-40151) |
| CVE-2022-40152 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-40152](https://nvd.nist.gov/vuln/detail/CVE-2022-40152) |
| CVE-2022-41854 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-41854](https://nvd.nist.gov/vuln/detail/CVE-2022-41854) |
| CVE-2022-42003 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42003](https://nvd.nist.gov/vuln/detail/CVE-2022-42003) |
| CVE-2022-42889 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42889](https://nvd.nist.gov/vuln/detail/CVE-2022-42889) |
| CVE-2022-45685 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-45685](https://nvd.nist.gov/vuln/detail/CVE-2022-45685) |
| CVE-2022-45693 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-45693](https://nvd.nist.gov/vuln/detail/CVE-2022-45693) |
| CVE-2022-46337 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-46337](https://nvd.nist.gov/vuln/detail/CVE-2022-46337) |
| CVE-2023-0833 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-0833](https://nvd.nist.gov/vuln/detail/CVE-2023-0833) |
| CVE-2023-1370 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-1370](https://nvd.nist.gov/vuln/detail/CVE-2023-1370) |
| CVE-2023-1436 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-1436](https://nvd.nist.gov/vuln/detail/CVE-2023-1436) |
| CVE-2023-20863 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-20863](https://nvd.nist.gov/vuln/detail/CVE-2023-20863) |
| CVE-2023-25194 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-25194](https://nvd.nist.gov/vuln/detail/CVE-2023-25194) |
| CVE-2023-33201 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-33201](https://nvd.nist.gov/vuln/detail/CVE-2023-33201) |
| CVE-2023-33202 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-33202](https://nvd.nist.gov/vuln/detail/CVE-2023-33202) |
| CVE-2023-34453 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-34453](https://nvd.nist.gov/vuln/detail/CVE-2023-34453) |
| CVE-2023-34454 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-34454](https://nvd.nist.gov/vuln/detail/CVE-2023-34454) |
| CVE-2023-39410 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-39410](https://nvd.nist.gov/vuln/detail/CVE-2023-39410) |
| CVE-2023-42503 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-42503](https://nvd.nist.gov/vuln/detail/CVE-2023-42503) |
| CVE-2023-5072 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-5072](https://nvd.nist.gov/vuln/detail/CVE-2023-5072) |
| CVE-2023-50868 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-50868](https://nvd.nist.gov/vuln/detail/CVE-2023-50868) |
| CVE-2023-52428 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-52428](https://nvd.nist.gov/vuln/detail/CVE-2023-52428) |
| CVE-2023-6378 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-6378](https://nvd.nist.gov/vuln/detail/CVE-2023-6378) |
| CVE-2023-6481 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-6481](https://nvd.nist.gov/vuln/detail/CVE-2023-6481) |
| CVE-2024-21634 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-21634](https://nvd.nist.gov/vuln/detail/CVE-2024-21634) |
| CVE-2024-23944 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-23944](https://nvd.nist.gov/vuln/detail/CVE-2024-23944) |
| CVE-2024-29131 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-29131](https://nvd.nist.gov/vuln/detail/CVE-2024-29131) |
| CVE-2024-30171 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-30171](https://nvd.nist.gov/vuln/detail/CVE-2024-30171) |
| CVE-2024-30172 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-30172](https://nvd.nist.gov/vuln/detail/CVE-2024-30172) |
| CVE-2024-34447 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-34447](https://nvd.nist.gov/vuln/detail/CVE-2024-34447) |
| CVE-2024-35255 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-35255](https://nvd.nist.gov/vuln/detail/CVE-2024-35255) |
| CVE-2024-36114 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-36114](https://nvd.nist.gov/vuln/detail/CVE-2024-36114) |
| CVE-2024-38808 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-38808](https://nvd.nist.gov/vuln/detail/CVE-2024-38808) |
| CVE-2024-39676 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-39676](https://nvd.nist.gov/vuln/detail/CVE-2024-39676) |
| CVE-2024-51504 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-51504](https://nvd.nist.gov/vuln/detail/CVE-2024-51504) |
| CVE-2024-7254 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-7254](https://nvd.nist.gov/vuln/detail/CVE-2024-7254) |
| CVE-2017-17485 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2017-17485](https://nvd.nist.gov/vuln/detail/CVE-2017-17485) |
| CVE-2018-14719 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2018-14719](https://nvd.nist.gov/vuln/detail/CVE-2018-14719) |
| CVE-2018-14720 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2018-14720](https://nvd.nist.gov/vuln/detail/CVE-2018-14720) |
| CVE-2018-19362 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2018-19362](https://nvd.nist.gov/vuln/detail/CVE-2018-19362) |
| CVE-2020-10650 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10650](https://nvd.nist.gov/vuln/detail/CVE-2020-10650) |
| CVE-2020-10968 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10968](https://nvd.nist.gov/vuln/detail/CVE-2020-10968) |
| CVE-2020-13936 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-13936](https://nvd.nist.gov/vuln/detail/CVE-2020-13936) |
| CVE-2020-14062 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14062](https://nvd.nist.gov/vuln/detail/CVE-2020-14062) |
| CVE-2020-15522 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-15522](https://nvd.nist.gov/vuln/detail/CVE-2020-15522) |
| CVE-2020-1945 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-1945](https://nvd.nist.gov/vuln/detail/CVE-2020-1945) |
| CVE-2020-28052 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-28052](https://nvd.nist.gov/vuln/detail/CVE-2020-28052) |
| CVE-2020-35490 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-35490](https://nvd.nist.gov/vuln/detail/CVE-2020-35490) |
| CVE-2021-36373 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2021-36373](https://nvd.nist.gov/vuln/detail/CVE-2021-36373) |
| CVE-2022-25647 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2022-25647](https://nvd.nist.gov/vuln/detail/CVE-2022-25647) |
| CVE-2022-38750 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2022-38750](https://nvd.nist.gov/vuln/detail/CVE-2022-38750) |
| CVE-2022-38752 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2022-38752](https://nvd.nist.gov/vuln/detail/CVE-2022-38752) |
| CVE-2022-42004 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42004](https://nvd.nist.gov/vuln/detail/CVE-2022-42004) |
| CVE-2022-46751 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2022-46751](https://nvd.nist.gov/vuln/detail/CVE-2022-46751) |
| CVE-2023-20883 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-20883](https://nvd.nist.gov/vuln/detail/CVE-2023-20883) |
| CVE-2023-26048 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-26048](https://nvd.nist.gov/vuln/detail/CVE-2023-26048) |
| CVE-2023-2976 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-36478 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-36478](https://nvd.nist.gov/vuln/detail/CVE-2023-36478) |
| CVE-2023-51074 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-51074](https://nvd.nist.gov/vuln/detail/CVE-2023-51074) |
| CVE-2024-25638 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-25638](https://nvd.nist.gov/vuln/detail/CVE-2024-25638) |
| CVE-2024-25710 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-25710](https://nvd.nist.gov/vuln/detail/CVE-2024-25710) |
| CVE-2024-26308 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-26308](https://nvd.nist.gov/vuln/detail/CVE-2024-26308) |
| CVE-2024-29133 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-29133](https://nvd.nist.gov/vuln/detail/CVE-2024-29133) |
| CVE-2024-47554 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-47554](https://nvd.nist.gov/vuln/detail/CVE-2024-47554) |
| CVE-2024-47561 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-47561](https://nvd.nist.gov/vuln/detail/CVE-2024-47561) |
| CVE-2024-6763 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-6763](https://nvd.nist.gov/vuln/detail/CVE-2024-6763) |
| CVE-2012-6153 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2012-6153](https://nvd.nist.gov/vuln/detail/CVE-2012-6153) |
| CVE-2020-11113 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11113](https://nvd.nist.gov/vuln/detail/CVE-2020-11113) |
| CVE-2021-22570 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-22570](https://nvd.nist.gov/vuln/detail/CVE-2021-22570) |
| CVE-2021-27568 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-27568](https://nvd.nist.gov/vuln/detail/CVE-2021-27568) |
| CVE-2024-29857 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-29857](https://nvd.nist.gov/vuln/detail/CVE-2024-29857) |
| CVE-2017-7525 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2017-7525](https://nvd.nist.gov/vuln/detail/CVE-2017-7525) |
| CVE-2018-11307 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-11307](https://nvd.nist.gov/vuln/detail/CVE-2018-11307) |
| CVE-2018-1313 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-1313](https://nvd.nist.gov/vuln/detail/CVE-2018-1313) |
| CVE-2018-19360 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-19360](https://nvd.nist.gov/vuln/detail/CVE-2018-19360) |
| CVE-2019-16335 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-16335](https://nvd.nist.gov/vuln/detail/CVE-2019-16335) |
| CVE-2019-16943 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-16943](https://nvd.nist.gov/vuln/detail/CVE-2019-16943) |
| CVE-2020-36180 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36180](https://nvd.nist.gov/vuln/detail/CVE-2020-36180) |
| CVE-2021-37136 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-37136](https://nvd.nist.gov/vuln/detail/CVE-2021-37136) |
| CVE-2022-24329 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-24329](https://nvd.nist.gov/vuln/detail/CVE-2022-24329) |
| CVE-2022-39135 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-39135](https://nvd.nist.gov/vuln/detail/CVE-2022-39135) |
| CVE-2022-40149 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-40149](https://nvd.nist.gov/vuln/detail/CVE-2022-40149) |
| CVE-2023-26049 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-26049](https://nvd.nist.gov/vuln/detail/CVE-2023-26049) |
## 7.5.0 릴리스 정보
다음 릴리스 정보에는 Amazon EMR 릴리스 7.5.0에 대한 정보가 포함되어 있습니다.
**새로운 기능**
+ **애플리케이션 업그레이드** – Amazon EMR 7.5.0 application upgrades include Delta 3.2.1-amzn-0, HBase 2.5.10, Hudi 0.15.0-amzn-2, and Iceberg 1.6.1-amzn-1.
+ EMR 미리 쓰기 로그(WAL)는 클러스터 간 복제를 지원합니다. 자세한 내용은 [EMR WAL 클러스터 간 복제](https://docs.aws.amazon.com/emr/latest/ReleaseGuide/emr-hbase-wal-cross-cluster.html)를 참조하세요.
**알려진 문제**
+ Amazon EMR 릴리스 7.5 이상에서 Apache Sqoop이 제거되었습니다.
+ 관리형 조정이 활성화되면 YARN ResourceManager(RM)에 심각한 교착 문제가 발생하여 동시 작업을 통해 **DECOMMISSIONING**에서 **DECOMMISSIONED** 상태로 전환할 때 응답하지 않습니다. 이 문제는 특히 대규모 클러스터 환경에서 발생합니다. 이 경우 노드 상태 전환과 애플리케이션 상태 전환 모두가 처리되지 않아 ResourceManager의 핵심 기능이 마비됩니다. 해결 방법은 프라이머리 노드에서 다음 명령을 사용하여 RM JVM을 다시 시작하는 것입니다.
```
sudo systemctl restart hadoop-yarn-resourcemanager
```
+ `CapacityScheduler` 또는 `FairScheduler` 이외의 YARN 스케줄러(예: FIFO 스케줄러)로 EMR 클러스터를 시작하면 `YARNMemoryAvailablePercentage` 지표가 CloudWatch로 푸시되지 않습니다. 이 문제는 관리형 확장 사용 클러스터의 다운스케일링에 영향을 줍니다. 그리고 `YARNMemoryAvailablePercentage` 지표에 따라 달라지는 경우 사용자 지정 관리 규모 조정에도 영향을 미칠 수 있습니다. 해결 방법으로 `CapacityScheduler` 또는 `FairScheduler`를 사용합니다.
+ **Glue 카탈로그를 사용하여 HBase 테이블을 Hive에 생성** - EMR-7.3.0에서 EMR-7.10.0으로의 Hive Iceberg 통합으로 인해 버그가 발생하여 Glue Data Catalog를 메타스토어로 사용할 때 Hive에서 HBase 테이블 생성이 실패합니다. 이 문제가 발생하면 AWS 지원 팀에 문의하십시오.
+ **Tez UI** - EMR-7.3에서 EMR-7.10까지, 전송 중 암호화가 활성화된 경우 YARN Resource Manager Web UI를 통해 Tez UI에 액세스하지 못하는 버그가 있습니다. 이 문제는 Tez UI에 HTTPS가 필요한 동안 YARN 프록시가 HTTP 프로토콜을 사용하려고 시도하기 때문에 발생합니다. 이 문제를 해결하려면 `tez-site`의 `tez.tez-ui.history-url.base` 구성을 `http`에서 `https`로 수정하세요.
**변경 사항, 향상된 기능 및 해결된 문제**
+ Spark 3.3.1(EMR 버전 6.10 이상에서 지원됨)부터 폐기 호스트의 모든 실행기는 *DECOMMISSIONING* 상태라는 새로운 `ExecutorState` 상태로 설정됩니다. Yarn은 폐기 중인 실행기를 사용하여 작업을 할당할 수 없으므로 필요한 경우 실행 중인 작업에 대해 새 실행기를 요청하세요. 따라서 EMR Managed Scaling, EMR Auto Scaling 또는 EMR-EC2 클러스터의 사용자 지정 조정 메커니즘을 사용하는 동안 Spark DRA를 비활성화하면 Yarn이 각 작업에 허용되는 최대 실행기를 요청할 수 있습니다. 이 문제를 방지하려면 위의 기능 조합을 사용할 때 `spark.dynamicAllocation.enabled` 속성을 `TRUE`(기본값)로 설정한 상태로 둡니다. 또한 Spark 작업의 `spark.dynamicAllocation.maxExecutors` 및 `spark.dynamicAllocation.minExecutors` 속성 값을 설정하여 작업 실행 중에 할당된 실행기 수를 제한하여 최소 및 최대 실행기 제약 조건을 설정할 수도 있습니다.
+ Amazon EMR은 클러스터에 대해 선택한 인스턴스 유형에 따라 다른 빌드의 TensorFlow 라이브러리를 사용합니다. 또한 Amazon EMR은 EMR-7.5.0 이상에서 **aarch64** 인스턴스 유형(Graviton 인스턴스)이 있는 클러스터에 TensorFlow를 지원합니다.
다음 표에는 EMR-7.5.0의 인스턴스 유형별 빌드가 나와 있습니다.
[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/ko_kr/emr/latest/ReleaseGuide/emr-750-release.html)
+ FGAC(Fine-Grained Access Control)가 활성화된 AWS Lake Formation Amazon EMR 클러스터는 이제 다음 hdfs-site.xml 구성으로 최대 256개의 동시 단계를 지원할 수 있습니다.
```
[
{
"Classification": "hdfs-site",
"Properties": {
"dfs.datanode.handler.count": "40",
"dfs.datanode.max.transfer.threads": "16384",
"dfs.namenode.handler.count": "64",
"dfs.replication": "1"
}
},
{
"Classification": "hdfs-env",
"Configurations": [
{
"Classification": "export",
"Properties": {
"HADOOP_DATANODE_HEAPSIZE": "5120"
}
}
],
"Properties": {}
}
]
```
+
[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/ko_kr/emr/latest/ReleaseGuide/emr-750-release.html)
## 7.5.0 기본 Java 버전
Amazon EMR 릴리스 7.5 이상은 Apache Livy를 제외하고 Corretto 17(OpenJDK)을 지원하는 애플리케이션에 기본적으로 Amazon Corretto 17(OpenJDK 기반)과 함께 제공됩니다.
다음 표에는 Amazon EMR 7.5.0의 애플리케이션에 대한 기본 Java 버전이 나와 있습니다. 클러스터의 기본 JVM을 변경하려면 클러스터에서 실행되는 각 애플리케이션에 대해 [특정 Java 가상 머신을 사용하도록 애플리케이션 구성](configuring-java8.md)의 지침을 따릅니다. 클러스터에서는 Java 런타임 버전 1개만 사용할 수 있습니다. Amazon EMR은 동일한 클러스터에서 다양한 런타임 버전을 사용해 서로 다른 노드 또는 애플리케이션을 실행하는 것을 지원하지 않습니다.
| 애플리케이션 | Java 및 Amazon Corretto 버전(기본값은 굵은체로 표시) |
| --- | --- |
| 델타 | 17, 11, 8 |
| Flink | 17, 11, 8 |
| HBase | 17, 11, 8 |
| HCatalog | 17, 11, 8 |
| Hadoop | 17, 11, 8 |
| Hive | 17, 11, 8 |
| Hudi | 17, 11, 8 |
| Iceberg | 17, 11, 8 |
| Livy | 17, 11, 8 |
| Oozie | 17, 11, 8 |
| 피닉스 | 17, 11, 8 |
| PrestoDB | 8 |
| Spark | 17, 11, 8 |
| Spark RAPIDS | 17, 11, 8 |
| Tez의 Hive 실행 시간 비교 | 17, 11, 8 |
| Trino | 21, 17 |
| Zeppelin | 17, 11, 8 |
| Pig | 8 |
| Zookeeper | 17, 11, 8 |
## 7.5.0 구성 요소 버전
이 릴리스를 통해 Amazon EMR이 설치하는 구성 요소는 다음과 같습니다. 일부는 빅 데이터 애플리케이션 패키지의 일부로 설치됩니다. 나머지는 Amazon EMR에 고유하며 시스템 프로세스 및 기능을 위해 설치됩니다. 이는 일반적으로 `emr` 또는 `aws`로 시작됩니다. 최근 Amazon EMR 릴리스의 빅 데이터 애플리케이션 패키지는 일반적으로 커뮤니티에서 발견된 최신 버전입니다. 가능한 한 빨리 Amazon EMR에서 커뮤니티 릴리스를 제공합니다.
Amazon EMR의 일부 구성 요소는 커뮤니티 버전과 다릅니다. 이러한 구성 요소에는 `CommunityVersion-amzn-EmrVersion` 양식의 버전 레이블이 있습니다. `EmrVersion`은 0에서 시작합니다. 예를 들어, 버전 2.2의 `myapp-component`라는 오픈 소스 커뮤니티 구성 요소가 다른 Amazon EMR 릴리스에 포함되도록 세 번 수정된 경우 해당 릴리스 버전은 `2.2-amzn-2`로 나열됩니다.
| 구성 요소 | 버전 | 설명 |
| --- | --- | --- |
| adot-java-agent | 1.31.0 | 애플리케이션 대몬(daemon)에서 지표를 수집하는 Java 에이전트입니다. |
| delta | 3.2.1-amzn-0 | Delta Lake는 방대한 분석 데이터 세트를 위한 오픈 테이블 형식입니다. |
| emr-amazon-cloudwatch-agent | 1.300032.2-amzn-0 | Amazon EC2 인스턴스에서 내부 시스템 수준 지표와 사용자 지정 애플리케이션 지표를 수집하는 애플리케이션입니다. |
| emr-ddb | 5.6.0 | 하둡 에코시스템 애플리케이션용 Amazon DynamoDB 커넥터 |
| emr-goodies | 3.14.0 | 편리한 하둡 에코시스템용 추가 라이브러리 |
| emr-kinesis | 3.18.0 | 하둡 에코시스템 애플리케이션용 Amazon Kinesis 커넥터. |
| emr-notebook-env | 1.16.0 | Jupyter Enterprise Gateway가 포함된 EMR 노트북용 Conda 환경 |
| emr-s3-dist-cp | 2.35.0 | Amazon S3용으로 최적화된 분사 복사 애플리케이션. |
| emr-s3-select | 2.14.0 | EMR S3Select 커넥터 |
| emr-wal-cli | 1.3.1 | emrwal 목록/삭제에 사용되는 CLI입니다. |
| emrfs | 2.66.0 | 하둡 에코시스템 애플리케이션용 Amazon S3 커넥터. |
| flink-client | 1.19.1-amzn-1 | Apache Flink 명령줄 클라이언트 스크립트 및 애플리케이션 |
| flink-jobmanager-config | 1.19.1-amzn-1 | Apache Flink JobManager에 대한 EMR 노드에서 리소스를 관리합니다. |
| hadoop-client | 3.4.0-amzn-1 | 'hdfs', 'hadoop', 'yarn' 등과 같은 하둡 명령줄 클라이언트 |
| hadoop-hdfs-datanode | 3.4.0-amzn-1 | 블록을 저장하는 HDFS 노드 수준 서비스 |
| hadoop-hdfs-library | 3.4.0-amzn-1 | HDFS 명령줄 클라이언트 및 라이브러리 |
| hadoop-hdfs-namenode | 3.4.0-amzn-1 | 파일 이름 및 블록 위치를 추적하는 HDFS 서비스 |
| hadoop-hdfs-journalnode | 3.4.0-amzn-1 | HA 클러스터에서 하둡 파일 시스템 저널을 관리하기 위한 HDFS 서비스 |
| hadoop-httpfs-server | 3.4.0-amzn-1 | HDFS 작업에 대한 HTTP 엔드포인트 |
| hadoop-kms-server | 3.4.0-amzn-1 | 하둡의 KeyProvider API를 기반으로 하는 암호화 키 관리 서버 |
| hadoop-mapred | 3.4.0-amzn-1 | MapReduce 애플리케이션을 실행하는 MapReduce 실행 엔진 라이브러리 |
| hadoop-yarn-nodemanager | 3.4.0-amzn-1 | 개별 노드의 컨테이너를 관리하는 YARN 서비스 |
| hadoop-yarn-resourcemanager | 3.4.0-amzn-1 | 클러스터 리소스 및 분산 애플리케이션을 할당 및 관리하는 YARN 서비스 |
| hadoop-yarn-timeline-server | 3.4.0-amzn-1 | YARN 애플리케이션의 현재 및 기록 정보를 가져오는 서비스 |
| hbase-hmaster | 2.5.10-amzn-0 | 리전 조정 및 관리 명령의 실행을 담당하는 HBase 클러스터용 서비스 |
| hbase-region-server | 2.5.10-amzn-0 | 한 개 이상의 HBase 리전에 서비스를 제공하는 서비스 |
| hbase-client | 2.5.10-amzn-0 | HBase 명령줄 클라이언트 |
| hbase-rest-server | 2.5.10-amzn-0 | HBase용 RESTful HTTP 엔드포인트를 제공하는 서비스 |
| hbase-thrift-server | 2.5.10-amzn-0 | HBase에 Thrift 엔드포인트를 제공하는 서비스 |
| hbase-operator-tools | 2.5.10-amzn-0 | Apache HBase 클러스터용 복구 도구. |
| hcatalog-client | 3.1.3-amzn-14 | hcatalog-server를 조정하기 위한 'hcat' 명령줄 클라이언트 |
| hcatalog-server | 3.1.3-amzn-14 | 분산 애플리케이션용 스토리지 관리 계층, 테이블 및 HCatalog를 제공하는 서비스 |
| hcatalog-webhcat-server | 3.1.3-amzn-14 | HCatalog에 REST 인터페이스를 제공하는 HTTP 엔드포인트 |
| hive-client | 3.1.3-amzn-14 | Hive 명령줄 클라이언트 |
| hive-hbase | 3.1.3-amzn-14 | Hive-hbase 클라이언트 |
| hive-metastore-server | 3.1.3-amzn-14 | 하둡 작업에 대한 SQL용 메타데이터가 저장되는 시맨틱 리포지토리인 Hive 메타스토어에 액세스하기 위한 서비스 |
| hive-server2 | 3.1.3-amzn-14 | Hive 쿼리를 웹 요청으로 수락하기 위한 서비스 |
| hudi | 0.15.0-amzn-2 | 짧은 지연 시간 및 높은 효율성으로 데이터 파이프라인을 구동하는 증분 처리 프레임워크. |
| hudi-presto | 0.15.0-amzn-2 | Hudi로 Presto를 실행하기 위한 번들 라이브러리. |
| hudi-trino | 0.15.0-amzn-2 | Hudi와 함께 Trnio를 실행하기 위한 번들 라이브러리. |
| hudi-spark | 0.15.0-amzn-2 | Hudi와 함께 Spark를 실행하기 위한 번들 라이브러리. |
| hue-server | 4.11.0 | 하둡 에코시스템 애플리케이션을 사용하여 데이터를 분석하는 웹 애플리케이션. |
| iceberg | 1.6.1-amzn-1 | Apache Iceberg는 방대한 분석 데이터 세트를 위한 오픈 테이블 형식입니다. |
| jupyterhub | 1.5.0 | Jupyter Notebook용 다중 사용자 서버 |
| livy-server | 0.8.0-incubating | Apache Spark와 상호작용하기 위한 REST 인터페이스 |
| nginx | 1.12.1 | HTTP인 nginx [engine x] 및 역방향 프록시 서버 |
| mariadb-server | 5.5.68 이상 | MariaDB 데이터베이스 서버. |
| nvidia-cuda | 12.3.0 | Nvidia 드라이버와 Cuda 도구 키트 |
| oozie-client | 5.2.1 | Oozie 명령줄 클라이언트 |
| oozie-server | 5.2.1 | Oozie 워크플로 요청을 수락하는 서비스 |
| opencv | 4.7.0 | 오픈 소스 컴퓨터 비전 라이브러리. |
| phoenix-library | 5.2.0 | 서버 및 클라이언트의 phoenix 라이브러리 |
| phoenix-connectors | 6.0.0 | Spark-3용 Apache Phoenix 커넥터 |
| phoenix-query-server | 6.0.0 | Avatica API에 대한 JSON 형식 액세스 및 프로토콜 버퍼 액세스를 비롯하여 JDBC 액세스를 제공하는 경량 서버 |
| presto-coordinator | 0.287-amzn-0 | presto-worker의 쿼리를 수락하고 쿼리 실행을 관리하는 서비스. |
| presto-worker | 0.287-amzn-0 | 여러 쿼리를 실행하는 서비스. |
| presto-client | 0.287-amzn-0 | Presto 서버가 시작되지 않은 HA 클러스터의 대기 마스터에 설치된 Presto 명령줄 클라이언트. |
| trino-coordinator | 446-amzn-0 | trino-workers의 쿼리를 수락하고 쿼리 실행을 관리하는 서비스. |
| trino-worker | 446-amzn-0 | 여러 쿼리를 실행하는 서비스. |
| trino-client | 446-amzn-0 | Trino 서버가 시작되지 않은 HA 클러스터의 대기 마스터에 설치된 Trino 명령줄 클라이언트. |
| pig-client | 0.17.0 | Pig 명령줄 클라이언트. |
| r | 4.3.2 | 통계 컴퓨팅용 R 프로젝트 |
| ranger-kms-server | 2.0.0 | Apache Ranger 키 관리 시스템 |
| spark-client | 3.5.2-amzn-1 | Spark 명령줄 클라이언트. |
| spark-history-server | 3.5.2-amzn-1 | 완료된 Spark 애플리케이션의 수명에 대해 기록된 이벤트를 조회하는 웹 UI. |
| spark-on-yarn | 3.5.2-amzn-1 | YARN용 인 메모리 실행 엔진. |
| spark-yarn-slave | 3.5.2-amzn-1 | YARN 슬레이브에서 필요한 Apache Spark 라이브러리. |
| spark-rapids | 24.08.1-amzn-1 | GPU로 Apache Spark를 가속화하는 Nvidia Spark RAPIDS 플러그인. |
| tensorflow | 2.16.1 | TensorFlow는 고성능 수치 계산용 오픈 소스 소프트웨어 라이브러리입니다. |
| tez-on-yarn | 0.10.2-amzn-12 | tez YARN 애플리케이션 및 라이브러리. |
| tez-on-worker | 0.10.2-amzn-12 | 워커 노드에 대한 tez YARN 애플리케이션 및 라이브러리. |
| zeppelin-server | 0.11.1 | 대화형 데이터 분석이 가능한 웹 기반 노트북 |
| zookeeper-server | 3.9.2-amzn-0 | 구성 정보 유지 관리, 이름 지정, 분산 동기화 제공 및 그룹 서비스 제공을 위한 중앙 집중식 서비스. |
| zookeeper-client | 3.9.2-amzn-0 | ZooKeeper 명령줄 클라이언트. |
## 7.5.0 구성 분류
구성 분류를 사용하면 애플리케이션을 사용자 지정할 수 있습니다. 이는 종종 `hive-site.xml`과 같이 애플리케이션의 구성 XML 파일에 해당합니다. 자세한 내용은 [애플리케이션 구성](emr-configure-apps.md) 단원을 참조하십시오.
재구성 작업은 실행 중인 클러스터의 인스턴스 그룹에 대한 구성을 지정할 때 수행됩니다. Amazon EMR은 사용자가 수정한 분류에 대한 재구성 작업만 시작합니다. 자세한 내용은 [실행 중인 클러스터에서 인스턴스 그룹 재구성](emr-configure-apps-running-cluster.md) 단원을 참조하십시오.
**emr-7.5.0 분류**
| 분류 | 설명 | 재구성 작업 |
| --- | --- | --- |
| capacity-scheduler | Hadoop capacity-scheduler.xml 파일에서 값을 변경합니다. | Restarts the ResourceManager service. |
| container-executor | Hadoop YARN container-executor.cfg 파일에서 값을 변경합니다. | Not available. |
| container-log4j | Hadoop YARN container-log4j.properties 파일에서 값을 변경합니다. | Not available. |
| core-site | Hadoop core-site.xml 파일에서 값을 변경합니다. | Restarts the Hadoop HDFS services Namenode, SecondaryNamenode, Datanode, ZKFC, and Journalnode. Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts Hadoop KMS, Ranger KMS, HiveServer2, Hive MetaStore, Hadoop Httpfs, and MapReduce-HistoryServer. |
| docker-conf | Docker 관련 설정을 변경합니다. | Not available. |
| emrfs-site | EMRFS 설정을 변경합니다. | Restarts the Hadoop HDFS services Namenode, SecondaryNamenode, Datanode, ZKFC, and Journalnode. Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts HBaseRegionserver, HBaseMaster, HBaseThrift, HBaseRest, HiveServer2, Hive MetaStore, Hadoop Httpfs, and MapReduce-HistoryServer. |
| flink-conf | flink-conf.yaml 설정을 변경합니다. | Restarts Flink history server. |
| flink-log4j | Flink log4j.properties 설정을 변경합니다. | Restarts Flink history server. |
| flink-log4j-session | Kubernetes 및 Yarn 세션에 대한 Flink log4j-session.properties 설정을 변경합니다. | Restarts Flink history server. |
| flink-log4j-cli | Flink log4j-cli.properties 설정을 변경합니다. | Restarts Flink history server. |
| hadoop-env | 모든 Hadoop 구성 요소에 대한 Hadoop 환경에서 값을 변경합니다. | Restarts the Hadoop HDFS services Namenode, SecondaryNamenode, Datanode, ZKFC, and Journalnode. Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts PhoenixQueryserver, HiveServer2, Hive MetaStore, and MapReduce-HistoryServer. |
| hadoop-log4j | Hadoop log4j.properties 파일에서 값을 변경합니다. | Restarts the Hadoop HDFS services SecondaryNamenode, Datanode, and Journalnode. Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts Hadoop KMS, Hadoop Httpfs, and MapReduce-HistoryServer. |
| hadoop-ssl-server | hadoop ssl 서버 구성을 변경합니다. | Not available. |
| hadoop-ssl-client | hadoop ssl 클라이언트 구성을 변경합니다. | Not available. |
| hbase | Apache HBase에 대한 Amazon EMR 큐레이트 설정입니다. | Custom EMR specific property. Sets emrfs-site and hbase-site configs. See those for their associated restarts. |
| hbase-env | HBase 환경에서 값을 변경합니다. | Restarts the HBase services RegionServer, HBaseMaster, ThriftServer, RestServer. |
| hbase-log4j | HBase hbase-log4j.properties 파일에서 값을 변경합니다. | Restarts the HBase services RegionServer, HBaseMaster, ThriftServer, RestServer. |
| hbase-metrics | HBase hadoop-metrics2-hbase.properties 파일에서 값을 변경합니다. | Restarts the HBase services RegionServer, HBaseMaster, ThriftServer, RestServer. |
| hbase-policy | HBase hbase-policy.xml 파일에서 값을 변경합니다. | Not available. |
| hbase-site | HBase hbase-site.xml 파일에서 값을 변경합니다. | Restarts the HBase services RegionServer, HBaseMaster, ThriftServer, RestServer. Additionally restarts Phoenix QueryServer. |
| hdfs-encryption-zones | HDFS 암호화 영역을 구성합니다. | This classification should not be reconfigured. |
| hdfs-env | HDFS 환경에서 값을 변경합니다. | Restarts Hadoop HDFS services Namenode, Datanode, and ZKFC. |
| hdfs-site | HDFS hdfs-site.xml에서 값을 변경합니다. | Restarts the Hadoop HDFS services Namenode, SecondaryNamenode, Datanode, ZKFC, and Journalnode. Additionally restarts Hadoop Httpfs. |
| hcatalog-env | HCatalog 환경에서 값을 변경합니다. | Restarts Hive HCatalog Server. |
| hcatalog-server-jndi | HCatalog jndi.properties 환경에서 값을 변경합니다. | Restarts Hive HCatalog Server. |
| hcatalog-server-proto-hive-site | HCatalog proto-hive-site.xml에서 값을 변경합니다. | Restarts Hive HCatalog Server. |
| hcatalog-webhcat-env | HCatalog WebHCat 환경에서 값을 변경합니다. | Restarts Hive WebHCat server. |
| hcatalog-webhcat-log4j2 | HCatalog WebHCat log4j2.properties에서 값을 변경합니다. | Restarts Hive WebHCat server. |
| hcatalog-webhcat-site | HCatalog WebHCat webhcat-site.xml 파일에서 값을 변경합니다. | Restarts Hive WebHCat server. |
| hive | Apache Hive에 대한 Amazon EMR 큐레이트 설정입니다. | Sets configurations to launch Hive LLAP service. |
| hive-beeline-log4j2 | Hive beeline-log4j2.properties 파일에서 값을 변경합니다. | Not available. |
| hive-parquet-logging | Hive parquet-logging.properties 파일에서 값을 변경합니다. | Not available. |
| hive-env | Hive 환경에서 값을 변경합니다. | Restarts HiveServer2, HiveMetastore, and Hive HCatalog-Server. Runs Hive schemaTool CLI commands to verify hive-metastore. |
| hive-exec-log4j2 | Hive hive-exec-log4j2.properties 파일에서 값을 변경합니다. | Not available. |
| hive-llap-daemon-log4j2 | Hive llap-daemon-log4j2.properties 파일에서 값을 변경합니다. | Not available. |
| hive-log4j2 | Hive hive-log4j2.properties 파일에서 값을 변경합니다. | Not available. |
| hive-site | Hive hive-site.xml 파일에서 값을 변경합니다. | Restarts HiveServer2, HiveMetastore, and Hive HCatalog-Server. Runs Hive schemaTool CLI commands to verify hive-metastore. Also restarts Oozie and Zeppelin. |
| hiveserver2-site | Hive Server2 hiveserver2-site.xml 파일에서 값을 변경합니다. | Not available. |
| hue-ini | Hue ini 파일에서 값을 변경합니다. | Restarts Hue. Also activates Hue config override CLI commands to pick up new configurations. |
| httpfs-env | HTTPFS 환경에서 값을 변경합니다. | Restarts Hadoop Httpfs service. |
| httpfs-site | Hadoop httpfs-site.xml 파일에서 값을 변경합니다. | Restarts Hadoop Httpfs service. |
| hadoop-kms-acls | Hadoop kms-acls.xml 파일에서 값을 변경합니다. | Not available. |
| hadoop-kms-env | Hadoop KMS 환경에서 값을 변경합니다. | Restarts Hadoop-KMS service. |
| hadoop-kms-java-home | Hadoop의 KMS java 홈 변경 | Not available. |
| hadoop-kms-log4j | Hadoop kms-log4j.properties 파일에서 값을 변경합니다. | Not available. |
| hadoop-kms-site | Hadoop kms-site.xml 파일에서 값을 변경합니다. | Restarts Hadoop-KMS and Ranger-KMS service. |
| hudi-env | Hudi 환경에서 값을 변경합니다. | Not available. |
| hudi-defaults | Hudi hudi-defaults.conf 파일에서 값을 변경합니다. | Not available. |
| iceberg-defaults | Iceberg iceberg-defaults.conf 파일에서 값을 변경합니다. | Not available. |
| delta-defaults | Delta delta-defaults.conf 파일에서 값을 변경합니다. | Not available. |
| jupyter-notebook-conf | Jupyter Notebook jupyter\$1notebook\$1config.py 파일에서 값을 변경합니다. | Not available. |
| jupyter-hub-conf | JupyterHubs jupyterhub\$1config.py 파일에서 값을 변경합니다. | Not available. |
| jupyter-s3-conf | Jupyter Notebook S3 지속성 구성 | Not available. |
| jupyter-sparkmagic-conf | Sparkmagic config.json 파일에서 값을 변경합니다. | Not available. |
| livy-conf | Livy livy.conf 파일에서 값을 변경합니다. | Restarts Livy Server. |
| livy-env | Livy 환경에서 값을 변경합니다. | Restarts Livy Server. |
| livy-log4j2 | Livy log4j2.properties 설정을 변경합니다. | Restarts Livy Server. |
| mapred-env | MapReduce 애플리케이션 환경에서 값을 변경합니다. | Restarts Hadoop MapReduce-HistoryServer. |
| mapred-site | MapReduce 애플리케이션 mapred-site.xml 파일에서 값을 변경합니다. | Restarts Hadoop MapReduce-HistoryServer. |
| oozie-env | Oozie 환경에서 값을 변경합니다. | Restarts Oozie. |
| oozie-log4j | Oozie oozie-log4j.properties 파일에서 값을 변경합니다. | Restarts Oozie. |
| oozie-site | Oozie oozie-site.xml 파일에서 값을 변경합니다. | Restarts Oozie. |
| phoenix-hbase-metrics | Phoenix hadoop-metrics2-hbase.properties 파일에서 값을 변경합니다. | Not available. |
| phoenix-hbase-site | Phoenix hbase-site.xml 파일에서 값을 변경합니다. | Not available. |
| phoenix-log4j2 | Phoenix log4j2.properties 파일에서 값을 변경합니다. | Restarts Phoenix-QueryServer. |
| phoenix-metrics | Phoenix hadoop-metrics2-phoenix.properties 파일에서 값을 변경합니다. | Not available. |
| pig-env | Pig 환경에서 값을 변경합니다. | Not available. |
| pig-properties | Pig pig.properties 파일에서 값을 변경합니다. | Restarts Oozie. |
| pig-log4j | Pig log4j.properties 파일에서 값을 변경합니다. | Not available. |
| presto-log | Presto log.properties 파일에서 값을 변경합니다. | Restarts Presto-Server (for PrestoDB) |
| presto-config | Presto config.properties 파일에서 값을 변경합니다. | Restarts Presto-Server (for PrestoDB) |
| presto-password-authenticator | Presto password-authenticator.properties 파일에서 값을 변경합니다. | Not available. |
| presto-env | Presto presto-env.sh 파일에서 값을 변경합니다. | Restarts Presto-Server (for PrestoDB) |
| presto-node | Presto node.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-blackhole | Presto blackhole.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-cassandra | Presto cassandra.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-hive | Presto hive.properties 파일에서 값을 변경합니다. | Restarts Presto-Server (for PrestoDB) |
| presto-connector-jmx | Presto jmx.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-kafka | Presto kafka.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-lakeformation | Presto lakeformation.properties 파일에서 값을 변경합니다. | Restarts Presto-Server (for PrestoDB) |
| presto-connector-localfile | Presto localfile.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-memory | Presto memory.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-mongodb | Presto mongodb.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-mysql | Presto mysql.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-postgresql | Presto postgresql.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-raptor | Presto raptor.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-redis | Presto redis.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-redshift | Presto redshift.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-tpch | Presto tpch.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-tpcds | Presto tpcds.properties 파일에서 값을 변경합니다. | Not available. |
| trino-log | Trino log.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-config | Trino config.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-password-authenticator | Trino password-authenticator.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-env | Trino trino-env.sh 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-node | Trino node.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-blackhole | Trino blackhole.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-cassandra | Trino cassandra.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-delta | Trino delta.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-connector-hive | Trino hive.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-exchange-manager | Trino exchange-manager.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-connector-iceberg | Trino iceberg.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-connector-hudi | Trino hudi.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-connector-jmx | Trino jmx.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-kafka | Trino kafka.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-localfile | Trino localfile.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-memory | Trino memory.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-mongodb | Trino mongodb.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-mysql | Trino mysql.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-postgresql | Trino postgresql.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-raptor | Trino raptor.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-redis | Trino redis.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-redshift | Trino redshift.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-tpch | Trino tpch.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-tpcds | Trino tpcds.properties 파일에서 값을 변경합니다. | Not available. |
| ranger-kms-dbks-site | Ranger KMS dbks-site.xml 파일에서 값을 변경합니다. | Restarts Ranger KMS Server. |
| ranger-kms-site | Ranger KMS ranger-kms-site.xml 파일에서 값을 변경합니다. | Restarts Ranger KMS Server. |
| ranger-kms-env | Ranger KMS 환경에서 값을 변경합니다. | Restarts Ranger KMS Server. |
| ranger-kms-logback | Ranger KMS kms-logback.xml 파일에서 값을 변경합니다. | Not available. |
| ranger-kms-db-ca | Ranger KMS와의 MySQL SSL 연결에서 CA 파일의 값을 변경합니다. | Not available. |
| spark | Apache Spark에 대한 Amazon EMR 큐레이트 설정입니다. | This property modifies spark-defaults. See actions there. |
| spark-defaults | Spark spark-defaults.conf 파일에서 값을 변경합니다. | Restarts Spark history server and Spark thrift server. |
| spark-env | Spark 환경에서 값을 변경합니다. | Restarts Spark history server and Spark thrift server. |
| spark-hive-site | Spark hive-site.xml 파일에서 값을 변경합니다. | Not available. |
| spark-log4j2 | Spark log4j2.properties 파일에서 값을 변경합니다. | Restarts Spark history server and Spark thrift server. |
| spark-metrics | Spark metrics.properties 파일에서 값을 변경합니다. | Restarts Spark history server and Spark thrift server. |
| tez-site | Tez tez-site.xml 파일에서 값을 변경합니다. | Restart Oozie and HiveServer2. |
| yarn-env | YARN 환경에서 값을 변경합니다. | Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts MapReduce-HistoryServer. |
| yarn-site | YARN yarn-site.xml 파일에서 값을 변경합니다. | Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts Livy Server and MapReduce-HistoryServer. |
| zeppelin-env | Zeppelin 환경에서 값을 변경합니다. | Restarts Zeppelin. |
| zeppelin-site | zeppelin-site.xml에서 구성 설정을 변경합니다. | Restarts Zeppelin. |
| zookeeper-config | ZooKeeper zoo.cfg 파일에서 값을 변경합니다. | Restarts Zookeeper server. |
| zookeeper-logback | ZooKeeper logback.xml 파일에서 값을 변경합니다. | Restarts Zookeeper server. |
| emr-metrics | 이 노드에 대한 emr 지표 설정을 변경합니다. | Restarts the CloudWatchAgent service. |
## 7.5.0 변경 로그
**7.5.0 릴리스 및 릴리스 정보에 대한 변경 로그**
| Date | 이벤트 | 설명 |
| --- | --- | --- |
| 2024-11-21 | 문서 게시 | Amazon EMR 7.5.0 릴리스 정보 최초 게시 |
| 2024-11-21 | 배포 완료 | [지원되는 모든 리전](https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/)에 Amazon EMR 7.5.0 완전 배포 |
| 2024-11-13 | 초기 릴리스 | Amazon EMR 7.5.0이 초기 상용 리전에 처음 배포됨 |
# Amazon EMR 릴리스 7.4.0
## 7.4.0 지원 수명 주기
다음 표에서는 Amazon EMR 릴리스 7.4.0에 지원되는 수명 주기 날짜를 설명합니다.
| 지원 단계 | Date |
| --- | --- |
| 초기 릴리스 날짜 | 2024년 11월 13일 |
| 표준 지원 종료 시점 | 2026년 11월 12일 |
| 지원 종료 | 2026년 11월 13일 |
| 수명 종료 | 2027년 11월 13일 |
## 7.4.0 애플리케이션 버전
이 릴리스에서 지원되는 애플리케이션은 [https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Install-CloudWatch-Agent.html](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Install-CloudWatch-Agent.html), [https://delta.io/](https://delta.io/), [https://flink.apache.org/](https://flink.apache.org/), [http://hbase.apache.org/](http://hbase.apache.org/), [https://cwiki.apache.org/confluence/display/Hive/HCatalog](https://cwiki.apache.org/confluence/display/Hive/HCatalog), [http://hadoop.apache.org/docs/current/](http://hadoop.apache.org/docs/current/), [http://hive.apache.org/](http://hive.apache.org/), [https://hudi.apache.org](https://hudi.apache.org), [http://gethue.com/](http://gethue.com/), [https://iceberg.apache.org/](https://iceberg.apache.org/), [https://jupyter-enterprise-gateway.readthedocs.io/en/latest/](https://jupyter-enterprise-gateway.readthedocs.io/en/latest/), [https://jupyterhub.readthedocs.io/en/latest/#](https://jupyterhub.readthedocs.io/en/latest/#), [https://livy.incubator.apache.org/](https://livy.incubator.apache.org/), [http://oozie.apache.org/](http://oozie.apache.org/), [https://phoenix.apache.org/](https://phoenix.apache.org/), [http://pig.apache.org/](http://pig.apache.org/), [https://prestodb.io/](https://prestodb.io/), [https://spark.apache.org/docs/latest/](https://spark.apache.org/docs/latest/), [http://sqoop.apache.org/](http://sqoop.apache.org/), [https://www.tensorflow.org/](https://www.tensorflow.org/), [https://tez.apache.org/](https://tez.apache.org/), [https://trino.io/](https://trino.io/), [https://zeppelin.incubator.apache.org/](https://zeppelin.incubator.apache.org/), [https://zookeeper.apache.org](https://zookeeper.apache.org)입니다.
아래 테이블에는 이번 Amazon EMR 릴리스에서 사용할 수 있는 애플리케이션 버전과 이전 세 가지 Amazon EMR 릴리스(해당하는 경우)의 애플리케이션 버전이 나와 있습니다.
각 Amazon EMR 릴리스에서 애플리케이션 버전의 전체 기록은 다음 주제를 참조하세요.
+ [Amazon EMR 7.x 릴리스의 애플리케이션 버전](emr-release-app-versions-7.x.md)
+ [Amazon EMR 6.x 릴리스의 애플리케이션 버전](emr-release-app-versions-6.x.md)
+ [Amazon EMR 5.x 릴리스의 애플리케이션 버전](emr-release-app-versions-5.x.md)
+ [Amazon EMR 4.x 릴리스의 애플리케이션 버전](emr-release-app-versions-4.x.md)
**애플리케이션 버전 정보**
| | emr-7.4.0 | emr-7.3.0 | emr-7.2.0 | emr-7.1.0 |
| --- | --- | --- | --- | --- |
| AWS Java용 SDK | 2.28.8, 1.12.772 | 2.25.70, 1.12.747 | 2.23.18, 1.12.705 | 2.23.18, 1.12.656 |
| Python | 3.9, 3.11 | 3.9, 3.11 | 3.9, 3.11 | 3.9, 3.11 |
| Scala | 2.12.18 | 2.12.18 | 2.12.17 | 2.12.17 |
| AmazonCloudWatchAgent | 1.300032.2-amzn-0 | 1.300032.2-amzn-0 | 1.300032.2-amzn-0 | 1.300032.2-amzn-0 |
| Delta | 3.2.0-amzn-1 | 3.2.0-amzn-0 | 3.1.0 | 3.0.0 |
| Flink | 1.19.1-amzn-0 | 1.18.1-amzn-2 | 1.18.1-amzn-1 | 1.18.1-amzn-0 |
| Ganglia | - | - | - | - |
| HBase | 2.5.5-amzn-0 | 2.4.17-amzn-7 | 2.4.17-amzn-6 | 2.4.17-amzn-5 |
| HCatalog | 3.1.3-amzn-13 | 3.1.3-amzn-12 | 3.1.3-amzn-11 | 3.1.3-amzn-10 |
| Hadoop | 3.4.0-amzn-0 | 3.3.6-amzn-5 | 3.3.6-amzn-4 | 3.3.6-amzn-3 |
| Hive | 3.1.3-amzn-13 | 3.1.3-amzn-12 | 3.1.3-amzn-11 | 3.1.3-amzn-10 |
| Hudi | 0.15.0-amzn-1 | 0.15.0-amzn-0 | 0.14.1-amzn-1 | 0.14.1-amzn-0 |
| Hue | 4.11.0 | 4.11.0 | 4.11.0 | 4.11.0 |
| Iceberg | 1.6.1-amzn-0 | 1.5.2-amzn-0 | 1.5.0-amzn-0 | 1.4.3-amzn-0 |
| JupyterEnterpriseGateway | 2.6.0 | 2.6.0 | 2.6.0 | 2.6.0 |
| JupyterHub | 1.5.0 | 1.5.0 | 1.5.0 | 1.5.0 |
| Livy | 0.8.0-incubating | 0.8.0-incubating | 0.8.0-incubating | 0.8.0-incubating |
| MXNet | - | - | 1.9.1 | 1.9.1 |
| Mahout | - | - | - | - |
| Oozie | 5.2.1 | 5.2.1 | 5.2.1 | 5.2.1 |
| Phoenix | 5.2.0 | 5.1.3 | 5.1.3 | 5.1.3 |
| Pig | 0.17.0 | 0.17.0 | 0.17.0 | 0.17.0 |
| Presto | 0.287-amzn-0 | 0.285-amzn-1 | 0.285-amzn-0 | 0.284-amzn-0 |
| Spark | 3.5.2-amzn-0 | 3.5.1-amzn-1 | 3.5.1-amzn-0 | 3.5.0-amzn-1 |
| Sqoop | 1.4.7 | 1.4.7 | 1.4.7 | 1.4.7 |
| TensorFlow | 2.16.1 | 2.16.1 | 2.11.0 | 2.11.0 |
| Tez | 0.10.2-amzn-11 | 0.10.2-amzn-10 | 0.10.2-amzn-9 | 0.10.2-amzn-8 |
| Trino (PrestoSQL) | 446-amzn-0 | 442-amzn-0 | 436-amzn-0 | 435-amzn-0 |
| Zeppelin | 0.11.1 | 0.11.1 | 0.10.1 | 0.10.1 |
| ZooKeeper | 3.9.2-amzn-0 | 3.9.1-amzn-1 | 3.9.1-amzn-1 | 3.9.1-amzn-0 |
# 7.4.0 릴리스 구성 요소 세부 정보
Amazon EMR 7.4.0의 *추가* 패키지에 대한 자세한 내용은 다음 표를 참조하세요.
| 애플리케이션 | 애플리케이션 유형 | 패키지 | 패키지 유형 | 패키지 버전 |
| --- | --- | --- | --- | --- |
| AmazonCloudWatchAgent | Core | hadoop-hdfs-journalnode | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| AmazonCloudWatchAgent | Core | ranger-kms | 추가 항목 | 2.0.0-1.amzn2023 |
| AmazonCloudWatchAgent | Core | s3-dist-cp | 추가 항목 | 2.33.0-1.amzn2023 |
| AmazonCloudWatchAgent | Core | zookeeper | 추가 항목 | 3.9.1.amzn.1-1.amzn2023 |
| AmazonCloudWatchAgent | Core | zookeeper-server | 추가 항목 | 3.9.1.amzn.1-1.amzn2023 |
| Flink | Core | hadoop-client | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Flink | Core | hadoop-hdfs | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Flink | Core | hadoop-hdfs-datanode | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Flink | Core | hadoop-hdfs-journalnode | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Flink | Core | hadoop-hdfs-namenode | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Flink | Core | hadoop-httpfs | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Flink | Core | hadoop-kms | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Flink | Core | hadoop-mapreduce | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Flink | Core | hadoop-mapreduce-historyserver | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Flink | Core | hadoop-yarn | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Flink | Core | hadoop-yarn-nodemanager | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Flink | Core | hadoop-yarn-proxyserver | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Flink | Core | hadoop-yarn-resourcemanager | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Flink | Core | hadoop-yarn-timelineserver | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Flink | Core | hudi | 추가 항목 | 0.15.0.amzn.0-1.amzn2023 |
| Flink | Core | ranger-kms | 추가 항목 | 2.0.0-1.amzn2023 |
| Flink | Core | hadoop | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| HBase | Core | s3-dist-cp | 추가 항목 | 2.33.0-1.amzn2023 |
| HCatalog | Core | hadoop-yarn-proxyserver | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| HCatalog | Core | mariadb-connector-java | 추가 항목 | |
| Hive | Core | hadoop-httpfs | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Hive | Core | hadoop-yarn-proxyserver | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Hive | Core | hive-hbase | 추가 항목 | 3.1.3.amzn.12-1.amzn2023 |
| Hive | Core | mariadb-connector-java | 추가 항목 | 2.7.2-1 |
| Hive | Core | s3-dist-cp | 추가 항목 | 2.33.0-1.amzn2023 |
| 피닉스 | Core | s3-dist-cp | 추가 항목 | 2.33.0-1.amzn2023 |
| Spark | Core | spark-datanucleus | 추가 항목 | 3.5.1.amzn.0-1.amzn2023 |
| Tez의 Hive 실행 시간 비교 | Core | hadoop-mapreduce | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Tez의 Hive 실행 시간 비교 | Core | hadoop-mapreduce-historyserver | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Tez의 Hive 실행 시간 비교 | Core | hadoop-yarn-proxyserver | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Trino | Core | bigtop-utils | 추가 항목 | 1.2.0-1.amzn2023 |
| Trino | Core | hadoop-client | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Trino | Core | hadoop-hdfs | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Trino | Core | hadoop-hdfs-datanode | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Trino | Core | hadoop-hdfs-journalnode | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Trino | Core | hadoop-hdfs-namenode | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Trino | Core | hadoop-kms | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Trino | Core | hadoop-mapreduce | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Trino | Core | hadoop-mapreduce-historyserver | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Trino | Core | hadoop-yarn | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Trino | Core | hadoop-yarn-nodemanager | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Trino | Core | hadoop-yarn-proxyserver | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Trino | Core | hadoop-yarn-resourcemanager | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Trino | Core | hadoop-yarn-timelineserver | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Trino | Core | hive | 추가 항목 | 3.1.3.amzn.12-1.amzn2023 |
| Trino | Core | hive-hcatalog-server | 추가 항목 | 3.1.3.amzn.12-1.amzn2023 |
| Trino | Core | mariadb-connector-java | 추가 항목 | 2.7.2-1 |
| Trino | Core | ranger-kms | 추가 항목 | 2.0.0-1.amzn2023 |
| Trino | Core | zookeeper | 추가 항목 | 3.9.1.amzn.1-1.amzn2023 |
| Trino | Core | zookeeper-server | 추가 항목 | 3.9.1.amzn.1-1.amzn2023 |
| Trino | Core | bigtop-groovy | 추가 항목 | 2.5.4-1.amzn2023 |
| Trino | Core | bigtop-jsvc | 추가 항목 | 1.2.4-1.amzn2023 |
| Trino | Core | hadoop | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Trino | Core | hadoop-lzo | 추가 항목 | 0.4.19-1.amzn2023 |
| Trino | Core | hive-hcatalog | 추가 항목 | 3.1.3.amzn.12-1.amzn2023 |
| Trino | Core | hive-jdbc | 추가 항목 | 3.1.3.amzn.12-1.amzn2023 |
| Zookeeper | Core | emrfs | 추가 항목 | 2.64.0-1.amzn2023 |
| Zookeeper | Core | hadoop-client | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Zookeeper | Core | hadoop-hdfs | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Zookeeper | Core | hadoop-hdfs-datanode | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Zookeeper | Core | hadoop-hdfs-journalnode | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Zookeeper | Core | hadoop-hdfs-namenode | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Zookeeper | Core | hadoop-httpfs | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Zookeeper | Core | hadoop-kms | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Zookeeper | Core | hadoop-mapreduce | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Zookeeper | Core | hadoop-mapreduce-historyserver | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Zookeeper | Core | hadoop-yarn | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Zookeeper | Core | hadoop-yarn-nodemanager | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Zookeeper | Core | hadoop-yarn-proxyserver | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Zookeeper | Core | hadoop-yarn-resourcemanager | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Zookeeper | Core | hadoop-yarn-timelineserver | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Zookeeper | Core | ranger-kms | 추가 항목 | 2.0.0-1.amzn2023 |
# 7.4.0 일반적인 취약성 및 노출
다음 표에는 Amazon EMR 7.4.0의 권장 구성에서 실행되는 EMR 클러스터에 영향을 주지 않는 모든 CVEs가 나열되어 있습니다. Amazon EMR은 업스트림 오픈 소스의 수정 사항 가용성에 종속되어 있으며, Amazon EMR이 수정 사항을 확인한 후 90일 이내에 코어 엔진 구성 요소의 일부로 안정적인 최신 버전을 제공합니다.
이 표는 2024년 11월 14일에 업데이트되었습니다.
| CVE ID | 심각도 | CVE 세부 정보 URL |
| --- | --- | --- |
| CVE-2013-4002 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2013-4002](https://nvd.nist.gov/vuln/detail/CVE-2013-4002) |
| CVE-2015-1832 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2015-1832](https://nvd.nist.gov/vuln/detail/CVE-2015-1832) |
| CVE-2017-7525 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2017-7525](https://nvd.nist.gov/vuln/detail/CVE-2017-7525) |
| CVE-2018-11307 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-11307](https://nvd.nist.gov/vuln/detail/CVE-2018-11307) |
| CVE-2018-12022 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-12022](https://nvd.nist.gov/vuln/detail/CVE-2018-12022) |
| CVE-2018-14718 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-14718](https://nvd.nist.gov/vuln/detail/CVE-2018-14718) |
| CVE-2018-19360 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-19360](https://nvd.nist.gov/vuln/detail/CVE-2018-19360) |
| CVE-2019-12384 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-12384](https://nvd.nist.gov/vuln/detail/CVE-2019-12384) |
| CVE-2019-14379 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14379](https://nvd.nist.gov/vuln/detail/CVE-2019-14379) |
| CVE-2019-14439 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14439](https://nvd.nist.gov/vuln/detail/CVE-2019-14439) |
| CVE-2019-16335 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-16335](https://nvd.nist.gov/vuln/detail/CVE-2019-16335) |
| CVE-2019-16943 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-16943](https://nvd.nist.gov/vuln/detail/CVE-2019-16943) |
| CVE-2020-10672 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10672](https://nvd.nist.gov/vuln/detail/CVE-2020-10672) |
| CVE-2020-10673 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10673](https://nvd.nist.gov/vuln/detail/CVE-2020-10673) |
| CVE-2020-11112 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11112](https://nvd.nist.gov/vuln/detail/CVE-2020-11112) |
| CVE-2020-13949 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-13949](https://nvd.nist.gov/vuln/detail/CVE-2020-13949) |
| CVE-2020-14195 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14195](https://nvd.nist.gov/vuln/detail/CVE-2020-14195) |
| CVE-2020-17521 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-17521](https://nvd.nist.gov/vuln/detail/CVE-2020-17521) |
| CVE-2020-24616 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-24616](https://nvd.nist.gov/vuln/detail/CVE-2020-24616) |
| CVE-2020-24750 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-24750](https://nvd.nist.gov/vuln/detail/CVE-2020-24750) |
| CVE-2020-25649 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-25649](https://nvd.nist.gov/vuln/detail/CVE-2020-25649) |
| CVE-2020-36183 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36183](https://nvd.nist.gov/vuln/detail/CVE-2020-36183) |
| CVE-2020-36186 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36186](https://nvd.nist.gov/vuln/detail/CVE-2020-36186) |
| CVE-2020-36188 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36188](https://nvd.nist.gov/vuln/detail/CVE-2020-36188) |
| CVE-2020-36189 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36189](https://nvd.nist.gov/vuln/detail/CVE-2020-36189) |
| CVE-2020-8908 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8908](https://nvd.nist.gov/vuln/detail/CVE-2020-8908) |
| CVE-2021-37137 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2021-37137](https://nvd.nist.gov/vuln/detail/CVE-2021-37137) |
| CVE-2021-38153 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2021-38153](https://nvd.nist.gov/vuln/detail/CVE-2021-38153) |
| CVE-2022-25857 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-25857](https://nvd.nist.gov/vuln/detail/CVE-2022-25857) |
| CVE-2022-3509 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3509](https://nvd.nist.gov/vuln/detail/CVE-2022-3509) |
| CVE-2022-37866 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-37866](https://nvd.nist.gov/vuln/detail/CVE-2022-37866) |
| CVE-2022-39135 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-39135](https://nvd.nist.gov/vuln/detail/CVE-2022-39135) |
| CVE-2022-41966 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-41966](https://nvd.nist.gov/vuln/detail/CVE-2022-41966) |
| CVE-2022-45688 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-45688](https://nvd.nist.gov/vuln/detail/CVE-2022-45688) |
| CVE-2023-34455 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2023-34455](https://nvd.nist.gov/vuln/detail/CVE-2023-34455) |
| CVE-2023-3635 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2023-3635](https://nvd.nist.gov/vuln/detail/CVE-2023-3635) |
| CVE-2023-38647 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2023-38647](https://nvd.nist.gov/vuln/detail/CVE-2023-38647) |
| CVE-2023-40167 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2023-40167](https://nvd.nist.gov/vuln/detail/CVE-2023-40167) |
| CVE-2023-43642 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2023-43642](https://nvd.nist.gov/vuln/detail/CVE-2023-43642) |
| CVE-2023-44981 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2023-44981](https://nvd.nist.gov/vuln/detail/CVE-2023-44981) |
| CVE-2023-50387 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2023-50387](https://nvd.nist.gov/vuln/detail/CVE-2023-50387) |
| CVE-2024-23454 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2024-23454](https://nvd.nist.gov/vuln/detail/CVE-2024-23454) |
| CVE-2024-29025 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2024-29025](https://nvd.nist.gov/vuln/detail/CVE-2024-29025) |
| CVE-2024-36124 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2024-36124](https://nvd.nist.gov/vuln/detail/CVE-2024-36124) |
| CVE-2024-8184 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2024-8184](https://nvd.nist.gov/vuln/detail/CVE-2024-8184) |
| CVE-2012-0881 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2012-0881](https://nvd.nist.gov/vuln/detail/CVE-2012-0881) |
| CVE-2012-5783 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2012-5783](https://nvd.nist.gov/vuln/detail/CVE-2012-5783) |
| CVE-2015-5237 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2015-5237](https://nvd.nist.gov/vuln/detail/CVE-2015-5237) |
| CVE-2016-5018 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2016-5018](https://nvd.nist.gov/vuln/detail/CVE-2016-5018) |
| CVE-2016-6796 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2016-6796](https://nvd.nist.gov/vuln/detail/CVE-2016-6796) |
| CVE-2017-15095 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2017-15095](https://nvd.nist.gov/vuln/detail/CVE-2017-15095) |
| CVE-2018-1000180 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-1000180](https://nvd.nist.gov/vuln/detail/CVE-2018-1000180) |
| CVE-2018-10054 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-10054](https://nvd.nist.gov/vuln/detail/CVE-2018-10054) |
| CVE-2018-10237 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-10237](https://nvd.nist.gov/vuln/detail/CVE-2018-10237) |
| CVE-2018-11798 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-11798](https://nvd.nist.gov/vuln/detail/CVE-2018-11798) |
| CVE-2018-12023 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-12023](https://nvd.nist.gov/vuln/detail/CVE-2018-12023) |
| CVE-2018-14721 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-14721](https://nvd.nist.gov/vuln/detail/CVE-2018-14721) |
| CVE-2018-19361 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-19361](https://nvd.nist.gov/vuln/detail/CVE-2018-19361) |
| CVE-2018-5968 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-5968](https://nvd.nist.gov/vuln/detail/CVE-2018-5968) |
| CVE-2018-7489 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-7489](https://nvd.nist.gov/vuln/detail/CVE-2018-7489) |
| CVE-2019-0205 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-0205](https://nvd.nist.gov/vuln/detail/CVE-2019-0205) |
| CVE-2019-12086 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-12086](https://nvd.nist.gov/vuln/detail/CVE-2019-12086) |
| CVE-2019-12814 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-12814](https://nvd.nist.gov/vuln/detail/CVE-2019-12814) |
| CVE-2019-14540 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14540](https://nvd.nist.gov/vuln/detail/CVE-2019-14540) |
| CVE-2019-14892 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14892](https://nvd.nist.gov/vuln/detail/CVE-2019-14892) |
| CVE-2019-14893 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14893](https://nvd.nist.gov/vuln/detail/CVE-2019-14893) |
| CVE-2019-16869 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-16869](https://nvd.nist.gov/vuln/detail/CVE-2019-16869) |
| CVE-2019-16942 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-16942](https://nvd.nist.gov/vuln/detail/CVE-2019-16942) |
| CVE-2019-17267 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-17267](https://nvd.nist.gov/vuln/detail/CVE-2019-17267) |
| CVE-2019-17531 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-17531](https://nvd.nist.gov/vuln/detail/CVE-2019-17531) |
| CVE-2019-20330 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-20330](https://nvd.nist.gov/vuln/detail/CVE-2019-20330) |
| CVE-2019-20444 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-20444](https://nvd.nist.gov/vuln/detail/CVE-2019-20444) |
| CVE-2019-20445 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-20445](https://nvd.nist.gov/vuln/detail/CVE-2019-20445) |
| CVE-2020-10969 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10969](https://nvd.nist.gov/vuln/detail/CVE-2020-10969) |
| CVE-2020-11111 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11111](https://nvd.nist.gov/vuln/detail/CVE-2020-11111) |
| CVE-2020-11619 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11619](https://nvd.nist.gov/vuln/detail/CVE-2020-11619) |
| CVE-2020-11620 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11620](https://nvd.nist.gov/vuln/detail/CVE-2020-11620) |
| CVE-2020-13955 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-13955](https://nvd.nist.gov/vuln/detail/CVE-2020-13955) |
| CVE-2020-13956 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-13956](https://nvd.nist.gov/vuln/detail/CVE-2020-13956) |
| CVE-2020-14060 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14060](https://nvd.nist.gov/vuln/detail/CVE-2020-14060) |
| CVE-2020-14061 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14061](https://nvd.nist.gov/vuln/detail/CVE-2020-14061) |
| CVE-2020-15250 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-15250](https://nvd.nist.gov/vuln/detail/CVE-2020-15250) |
| CVE-2020-26939 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-26939](https://nvd.nist.gov/vuln/detail/CVE-2020-26939) |
| CVE-2020-35491 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-35491](https://nvd.nist.gov/vuln/detail/CVE-2020-35491) |
| CVE-2020-35728 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-35728](https://nvd.nist.gov/vuln/detail/CVE-2020-35728) |
| CVE-2020-36179 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36179](https://nvd.nist.gov/vuln/detail/CVE-2020-36179) |
| CVE-2020-36181 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36181](https://nvd.nist.gov/vuln/detail/CVE-2020-36181) |
| CVE-2020-36182 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36182](https://nvd.nist.gov/vuln/detail/CVE-2020-36182) |
| CVE-2020-36184 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36184](https://nvd.nist.gov/vuln/detail/CVE-2020-36184) |
| CVE-2020-36185 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36185](https://nvd.nist.gov/vuln/detail/CVE-2020-36185) |
| CVE-2020-36187 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36187](https://nvd.nist.gov/vuln/detail/CVE-2020-36187) |
| CVE-2020-36518 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36518](https://nvd.nist.gov/vuln/detail/CVE-2020-36518) |
| CVE-2020-8840 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8840](https://nvd.nist.gov/vuln/detail/CVE-2020-8840) |
| CVE-2020-9546 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-9546](https://nvd.nist.gov/vuln/detail/CVE-2020-9546) |
| CVE-2020-9547 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-9547](https://nvd.nist.gov/vuln/detail/CVE-2020-9547) |
| CVE-2020-9548 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-9548](https://nvd.nist.gov/vuln/detail/CVE-2020-9548) |
| CVE-2021-20190 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-20190](https://nvd.nist.gov/vuln/detail/CVE-2021-20190) |
| CVE-2021-21290 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-21290](https://nvd.nist.gov/vuln/detail/CVE-2021-21290) |
| CVE-2021-22569 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-22569](https://nvd.nist.gov/vuln/detail/CVE-2021-22569) |
| CVE-2021-28170 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-28170](https://nvd.nist.gov/vuln/detail/CVE-2021-28170) |
| CVE-2021-29425 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-29425](https://nvd.nist.gov/vuln/detail/CVE-2021-29425) |
| CVE-2021-31684 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-31684](https://nvd.nist.gov/vuln/detail/CVE-2021-31684) |
| CVE-2021-34538 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-34538](https://nvd.nist.gov/vuln/detail/CVE-2021-34538) |
| CVE-2021-36374 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-36374](https://nvd.nist.gov/vuln/detail/CVE-2021-36374) |
| CVE-2021-37533 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-37533](https://nvd.nist.gov/vuln/detail/CVE-2021-37533) |
| CVE-2021-43859 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-43859](https://nvd.nist.gov/vuln/detail/CVE-2021-43859) |
| CVE-2022-1415 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-1415](https://nvd.nist.gov/vuln/detail/CVE-2022-1415) |
| CVE-2022-1471 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-1471](https://nvd.nist.gov/vuln/detail/CVE-2022-1471) |
| CVE-2022-3171 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3171](https://nvd.nist.gov/vuln/detail/CVE-2022-3171) |
| CVE-2022-3510 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3510](https://nvd.nist.gov/vuln/detail/CVE-2022-3510) |
| CVE-2022-36364 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-36364](https://nvd.nist.gov/vuln/detail/CVE-2022-36364) |
| CVE-2022-37865 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-37865](https://nvd.nist.gov/vuln/detail/CVE-2022-37865) |
| CVE-2022-38749 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-38749](https://nvd.nist.gov/vuln/detail/CVE-2022-38749) |
| CVE-2022-38751 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-38751](https://nvd.nist.gov/vuln/detail/CVE-2022-38751) |
| CVE-2022-40150 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-40150](https://nvd.nist.gov/vuln/detail/CVE-2022-40150) |
| CVE-2022-40151 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-40151](https://nvd.nist.gov/vuln/detail/CVE-2022-40151) |
| CVE-2022-40152 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-40152](https://nvd.nist.gov/vuln/detail/CVE-2022-40152) |
| CVE-2022-41854 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-41854](https://nvd.nist.gov/vuln/detail/CVE-2022-41854) |
| CVE-2022-42003 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42003](https://nvd.nist.gov/vuln/detail/CVE-2022-42003) |
| CVE-2022-42889 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42889](https://nvd.nist.gov/vuln/detail/CVE-2022-42889) |
| CVE-2022-45685 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-45685](https://nvd.nist.gov/vuln/detail/CVE-2022-45685) |
| CVE-2022-45693 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-45693](https://nvd.nist.gov/vuln/detail/CVE-2022-45693) |
| CVE-2022-46337 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-46337](https://nvd.nist.gov/vuln/detail/CVE-2022-46337) |
| CVE-2023-0833 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-0833](https://nvd.nist.gov/vuln/detail/CVE-2023-0833) |
| CVE-2023-1370 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-1370](https://nvd.nist.gov/vuln/detail/CVE-2023-1370) |
| CVE-2023-1436 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-1436](https://nvd.nist.gov/vuln/detail/CVE-2023-1436) |
| CVE-2023-20863 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-20863](https://nvd.nist.gov/vuln/detail/CVE-2023-20863) |
| CVE-2023-25194 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-25194](https://nvd.nist.gov/vuln/detail/CVE-2023-25194) |
| CVE-2023-33201 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-33201](https://nvd.nist.gov/vuln/detail/CVE-2023-33201) |
| CVE-2023-33202 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-33202](https://nvd.nist.gov/vuln/detail/CVE-2023-33202) |
| CVE-2023-34453 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-34453](https://nvd.nist.gov/vuln/detail/CVE-2023-34453) |
| CVE-2023-34454 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-34454](https://nvd.nist.gov/vuln/detail/CVE-2023-34454) |
| CVE-2023-39410 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-39410](https://nvd.nist.gov/vuln/detail/CVE-2023-39410) |
| CVE-2023-42503 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-42503](https://nvd.nist.gov/vuln/detail/CVE-2023-42503) |
| CVE-2023-5072 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-5072](https://nvd.nist.gov/vuln/detail/CVE-2023-5072) |
| CVE-2023-50868 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-50868](https://nvd.nist.gov/vuln/detail/CVE-2023-50868) |
| CVE-2023-52428 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-52428](https://nvd.nist.gov/vuln/detail/CVE-2023-52428) |
| CVE-2023-6378 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-6378](https://nvd.nist.gov/vuln/detail/CVE-2023-6378) |
| CVE-2023-6481 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-6481](https://nvd.nist.gov/vuln/detail/CVE-2023-6481) |
| CVE-2024-21634 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-21634](https://nvd.nist.gov/vuln/detail/CVE-2024-21634) |
| CVE-2024-23944 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-23944](https://nvd.nist.gov/vuln/detail/CVE-2024-23944) |
| CVE-2024-29131 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-29131](https://nvd.nist.gov/vuln/detail/CVE-2024-29131) |
| CVE-2024-30171 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-30171](https://nvd.nist.gov/vuln/detail/CVE-2024-30171) |
| CVE-2024-30172 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-30172](https://nvd.nist.gov/vuln/detail/CVE-2024-30172) |
| CVE-2024-34447 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-34447](https://nvd.nist.gov/vuln/detail/CVE-2024-34447) |
| CVE-2024-35255 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-35255](https://nvd.nist.gov/vuln/detail/CVE-2024-35255) |
| CVE-2024-36114 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-36114](https://nvd.nist.gov/vuln/detail/CVE-2024-36114) |
| CVE-2024-38808 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-38808](https://nvd.nist.gov/vuln/detail/CVE-2024-38808) |
| CVE-2024-39676 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-39676](https://nvd.nist.gov/vuln/detail/CVE-2024-39676) |
| CVE-2024-51504 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-51504](https://nvd.nist.gov/vuln/detail/CVE-2024-51504) |
| CVE-2024-7254 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-7254](https://nvd.nist.gov/vuln/detail/CVE-2024-7254) |
| CVE-2017-17485 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2017-17485](https://nvd.nist.gov/vuln/detail/CVE-2017-17485) |
| CVE-2018-14719 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2018-14719](https://nvd.nist.gov/vuln/detail/CVE-2018-14719) |
| CVE-2018-14720 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2018-14720](https://nvd.nist.gov/vuln/detail/CVE-2018-14720) |
| CVE-2018-19362 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2018-19362](https://nvd.nist.gov/vuln/detail/CVE-2018-19362) |
| CVE-2020-10650 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10650](https://nvd.nist.gov/vuln/detail/CVE-2020-10650) |
| CVE-2020-10968 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10968](https://nvd.nist.gov/vuln/detail/CVE-2020-10968) |
| CVE-2020-13936 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-13936](https://nvd.nist.gov/vuln/detail/CVE-2020-13936) |
| CVE-2020-14062 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14062](https://nvd.nist.gov/vuln/detail/CVE-2020-14062) |
| CVE-2020-15522 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-15522](https://nvd.nist.gov/vuln/detail/CVE-2020-15522) |
| CVE-2020-1945 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-1945](https://nvd.nist.gov/vuln/detail/CVE-2020-1945) |
| CVE-2020-28052 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-28052](https://nvd.nist.gov/vuln/detail/CVE-2020-28052) |
| CVE-2020-35490 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2020-35490](https://nvd.nist.gov/vuln/detail/CVE-2020-35490) |
| CVE-2021-36373 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2021-36373](https://nvd.nist.gov/vuln/detail/CVE-2021-36373) |
| CVE-2022-25647 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2022-25647](https://nvd.nist.gov/vuln/detail/CVE-2022-25647) |
| CVE-2022-38750 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2022-38750](https://nvd.nist.gov/vuln/detail/CVE-2022-38750) |
| CVE-2022-38752 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2022-38752](https://nvd.nist.gov/vuln/detail/CVE-2022-38752) |
| CVE-2022-42004 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42004](https://nvd.nist.gov/vuln/detail/CVE-2022-42004) |
| CVE-2022-46751 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2022-46751](https://nvd.nist.gov/vuln/detail/CVE-2022-46751) |
| CVE-2023-20883 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-20883](https://nvd.nist.gov/vuln/detail/CVE-2023-20883) |
| CVE-2023-26048 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-26048](https://nvd.nist.gov/vuln/detail/CVE-2023-26048) |
| CVE-2023-2976 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-36478 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-36478](https://nvd.nist.gov/vuln/detail/CVE-2023-36478) |
| CVE-2023-51074 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2023-51074](https://nvd.nist.gov/vuln/detail/CVE-2023-51074) |
| CVE-2024-25638 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-25638](https://nvd.nist.gov/vuln/detail/CVE-2024-25638) |
| CVE-2024-25710 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-25710](https://nvd.nist.gov/vuln/detail/CVE-2024-25710) |
| CVE-2024-26308 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-26308](https://nvd.nist.gov/vuln/detail/CVE-2024-26308) |
| CVE-2024-29133 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-29133](https://nvd.nist.gov/vuln/detail/CVE-2024-29133) |
| CVE-2024-47554 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-47554](https://nvd.nist.gov/vuln/detail/CVE-2024-47554) |
| CVE-2024-47561 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-47561](https://nvd.nist.gov/vuln/detail/CVE-2024-47561) |
| CVE-2024-6763 | 중간 | [https://nvd.nist.gov/vuln/detail/CVE-2024-6763](https://nvd.nist.gov/vuln/detail/CVE-2024-6763) |
| CVE-2012-6153 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2012-6153](https://nvd.nist.gov/vuln/detail/CVE-2012-6153) |
| CVE-2020-11113 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11113](https://nvd.nist.gov/vuln/detail/CVE-2020-11113) |
| CVE-2021-22570 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-22570](https://nvd.nist.gov/vuln/detail/CVE-2021-22570) |
| CVE-2021-27568 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-27568](https://nvd.nist.gov/vuln/detail/CVE-2021-27568) |
| CVE-2024-29857 | 낮음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-29857](https://nvd.nist.gov/vuln/detail/CVE-2024-29857) |
| CVE-2018-1313 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-1313](https://nvd.nist.gov/vuln/detail/CVE-2018-1313) |
| CVE-2020-36180 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36180](https://nvd.nist.gov/vuln/detail/CVE-2020-36180) |
| CVE-2021-37136 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-37136](https://nvd.nist.gov/vuln/detail/CVE-2021-37136) |
| CVE-2022-24329 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-24329](https://nvd.nist.gov/vuln/detail/CVE-2022-24329) |
| CVE-2022-40149 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-40149](https://nvd.nist.gov/vuln/detail/CVE-2022-40149) |
| CVE-2023-26049 | 분류되지 않음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-26049](https://nvd.nist.gov/vuln/detail/CVE-2023-26049) |
## 7.4.0 릴리스 정보
다음 릴리스 정보에는 Amazon EMR 릴리스 7.4.0에 대한 정보가 포함되어 있습니다.
**새로운 기능**
+ **애플리케이션 업그레이드** – Amazon EMR 7.4.0 application upgrades include AWS SDK for Java 2.28.8, Delta 3.2.0-amzn-1, Flink 1.19.1, Hadoop 3.4.0, HBase 2.5.5, Hudi 0.15.0-amzn-1, Iceberg 1.6.1-amzn-0, Phoenix 5.2.0, Presto 0.287, Spark 3.5.2, Trino 446, and Zookeeper 3.9.2.
+ 이 릴리스에는 네트워크를 통한 전송 중 데이터 암호화를 지원하는 7개의 오픈 소스 엔드포인트가 추가되었습니다. 이 개선 사항에는 Hue, Livy, JupyterEnterpriseGateway, Zookeeper 및 Ranger KMS 같은 오픈 소스 프레임워크가 포함됩니다. 전송 중 데이터 암호화를 활성화하고 이러한 엔드포인트에 연결하려는 경우 TLS 통신을 지원하도록 코드를 수정해야 할 수 있습니다. 필요한 경우 이러한 엔드포인트에 대한 TLS를 비활성화할 수 있습니다. 지원되는 엔드포인트의 전체 목록은 [전송 중 암호화 이해](https://docs.aws.amazon.com/emr/latest/ManagementGuide/emr-encryption-support-matrix.html)를 참조하세요.
**알려진 문제**
+ emr-6.11.0 이후 이전에 Hive 셔플 핸들러를 지원했던 Yarn ResourceManager의 `yarn.resourcemanager.decommissioning-nodes-watcher.wait-for-shuffle-data` 속성은 이제 emr-7.4.0에서 Yarn에서 Spark를 실행할 때 Spark 외부 셔플 서비스가 제공하는 파일에도 정상적인 폐기를 적용합니다.
Spark on Yarn을 실행할 때 Spark 외부 셔플 서비스의 기본 동작은 애플리케이션이 종료될 때 Yarn NodeManager가 애플리케이션 셔플 파일을 제거합니다. 이는 노드 해제 속도 및 컴퓨팅 사용률에 영향을 미칠 수 있습니다. 오래 실행되는 애플리케이션의 경우 `spark.shuffle.service.removeShuffle`을 `true`로 설정하여 더 이상 사용하지 않는 셔플 파일을 제거하면 활성 셔플 데이터가 없는 노드를 더 빠르게 폐기할 수 있습니다.
+ Amazon S3 Select 가용성 - Amazon S3 Select는 Presto 및 Trino에 대한 리전 간 쿼리를 지원하지 않습니다. Presto 및 Trino 릴리스에 사용할 수 있는 특정 기능에 대한 자세한 내용은 [Presto 및 Trino](https://docs.aws.amazon.com/emr/latest/ReleaseGuide/emr-presto.html)를 참조하세요.
+ Amazon EMR 릴리스 7.4에서는 Apache Ranger가 지원되지 않습니다.
+ Apache Sqoop은 알려진 문제 SQOOP-3485로 인해 Apache Hadoop 3.4와 호환되지 않습니다. Amazon EMR 릴리스 7.4에는 Apache Sqoop이 포함되지만, 지원되지는 않습니다. Apache Sqoop은 Amazon EMR 릴리스 7.5 이상 릴리스에서 제거될 예정입니다.
+ 관리형 조정이 활성화되면 YARN ResourceManager(RM)에 심각한 교착 문제가 발생하여 동시 작업을 통해 **DECOMMISSIONING**에서 **DECOMMISSIONED** 상태로 전환할 때 응답하지 않습니다. 이 문제는 특히 대규모 클러스터 환경에서 발생합니다. 이 경우 노드 상태 전환과 애플리케이션 상태 전환 모두가 처리되지 않아 ResourceManager의 핵심 기능이 마비됩니다. 해결 방법은 프라이머리 노드에서 다음 명령을 사용하여 RM JVM을 다시 시작하는 것입니다.
```
sudo systemctl restart hadoop-yarn-resourcemanager
```
+ `CapacityScheduler` 또는 `FairScheduler` 이외의 YARN 스케줄러(예: FIFO 스케줄러)로 EMR 클러스터를 시작하면 `YARNMemoryAvailablePercentage` 지표가 CloudWatch로 푸시되지 않습니다. 이 문제는 관리형 확장 사용 클러스터의 다운스케일링에 영향을 줍니다. 그리고 `YARNMemoryAvailablePercentage` 지표에 따라 달라지는 경우 사용자 지정 관리 규모 조정에도 영향을 미칠 수 있습니다. 해결 방법으로 `CapacityScheduler` 또는 `FairScheduler`를 사용합니다.
+ **Glue 카탈로그를 사용하여 HBase 테이블을 Hive에 생성** - EMR-7.3.0에서 EMR-7.10.0으로의 Hive Iceberg 통합으로 인해 버그가 발생하여 Glue Data Catalog를 메타스토어로 사용할 때 Hive에서 HBase 테이블 생성이 실패합니다. 이 문제가 발생하면 AWS 지원 팀에 문의하십시오.
+ **Tez UI** - EMR-7.3에서 EMR-7.10까지, 전송 중 암호화가 활성화된 경우 YARN Resource Manager Web UI를 통해 Tez UI에 액세스하지 못하는 버그가 있습니다. 이 문제는 Tez UI에 HTTPS가 필요한 동안 YARN 프록시가 HTTP 프로토콜을 사용하려고 시도하기 때문에 발생합니다. 이 문제를 해결하려면 `tez-site`의 `tez.tez-ui.history-url.base` 구성을 `http`에서 `https`로 수정하세요.
**변경 사항, 향상된 기능 및 해결된 문제**
+ Spark 3.3.1(EMR 버전 6.10 이상에서 지원됨)부터 폐기 호스트의 모든 실행기는 *DECOMMISSIONING* 상태라는 새로운 `ExecutorState` 상태로 설정됩니다. Yarn은 폐기 중인 실행기를 사용하여 작업을 할당할 수 없으므로 필요한 경우 실행 중인 작업에 대해 새 실행기를 요청하세요. 따라서 EMR Managed Scaling, EMR Auto Scaling 또는 EMR-EC2 클러스터의 사용자 지정 조정 메커니즘을 사용하는 동안 Spark DRA를 비활성화하면 Yarn이 각 작업에 허용되는 최대 실행기를 요청할 수 있습니다. 이 문제를 방지하려면 위의 기능 조합을 사용할 때 `spark.dynamicAllocation.enabled` 속성을 `TRUE`(기본값)로 설정한 상태로 둡니다. 또한 Spark 작업의 `spark.dynamicAllocation.maxExecutors` 및 `spark.dynamicAllocation.minExecutors` 속성 값을 설정하여 작업 실행 중에 할당된 실행기 수를 제한하여 최소 및 최대 실행기 제약 조건을 설정할 수도 있습니다.
+ Amazon EMR은 클러스터에 대해 선택한 인스턴스 유형에 따라 다른 빌드의 TensorFlow 라이브러리를 사용합니다. 또한 Amazon EMR은 EMR-7.5.0 이상에서 aarch64 인스턴스 유형(Graviton 인스턴스)이 있는 클러스터에 TensorFlow를 지원합니다.
+ **Iceberg 워크로드에 대한 S3 요청 크기 조정 최적화** - EMR 34 v7.4 릴리스와 함께 Iceberg를 사용하는 고객의 경우, S3는 기본 엔트로피 방식을 20자리 2진법 기반(예: 35 01010110100110110010) 해시로 업데이트했습니다. 이 새로운 base-2 엔트로피 체계는 문자 범위를 줄이고 S3가 대상 Iceberg 워크로드의 수요에 맞게 요청 용량을 더 빠르게 자동으로 조정할 수 있도록 합니다. 또한 이를 통해 워크로드가 503 스로틀 응답을 관찰하는 시간도 감소합니다.
+
[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/ko_kr/emr/latest/ReleaseGuide/emr-740-release.html)
## 7.4.0 기본 Java 버전
Amazon EMR 릴리스 7.4 이상은 Apache Livy를 제외하고 Corretto 17(OpenJDK)을 지원하는 애플리케이션에 기본적으로 Amazon Corretto 17(OpenJDK 기반)과 함께 제공됩니다.
다음 표에는 Amazon EMR 7.4.0의 애플리케이션에 대한 기본 Java 버전이 나와 있습니다. 클러스터의 기본 JVM을 변경하려면 클러스터에서 실행되는 각 애플리케이션에 대해 [특정 Java 가상 머신을 사용하도록 애플리케이션 구성](configuring-java8.md)의 지침을 따릅니다. 클러스터에서는 Java 런타임 버전 1개만 사용할 수 있습니다. Amazon EMR은 동일한 클러스터에서 다양한 런타임 버전을 사용해 서로 다른 노드 또는 애플리케이션을 실행하는 것을 지원하지 않습니다.
| 애플리케이션 | Java 및 Amazon Corretto 버전(기본값은 굵은체로 표시) |
| --- | --- |
| 델타 | 17, 11, 8 |
| Flink | 17, 11, 8 |
| HBase | 17, 11, 8 |
| HCatalog | 17, 11, 8 |
| Hadoop | 17, 11, 8 |
| Hive | 17, 11, 8 |
| Hudi | 17, 11, 8 |
| Iceberg | 17, 11, 8 |
| Livy | 17, 11, 8 |
| Oozie | 17, 11, 8 |
| 피닉스 | 17, 11, 8 |
| PrestoDB | 8 |
| Spark | 17, 11, 8 |
| Spark RAPIDS | 17, 11, 8 |
| Sqoop | 8 |
| Tez의 Hive 실행 시간 비교 | 17, 11, 8 |
| Trino | 21, 17 |
| Zeppelin | 17, 11, 8 |
| Pig | 8 |
| Zookeeper | 8 |
## 7.4.0 구성 요소 버전
이 릴리스를 통해 Amazon EMR이 설치하는 구성 요소는 다음과 같습니다. 일부는 빅 데이터 애플리케이션 패키지의 일부로 설치됩니다. 나머지는 Amazon EMR에 고유하며 시스템 프로세스 및 기능을 위해 설치됩니다. 이는 일반적으로 `emr` 또는 `aws`로 시작됩니다. 최근 Amazon EMR 릴리스의 빅 데이터 애플리케이션 패키지는 일반적으로 커뮤니티에서 발견된 최신 버전입니다. 가능한 한 빨리 Amazon EMR에서 커뮤니티 릴리스를 제공합니다.
Amazon EMR의 일부 구성 요소는 커뮤니티 버전과 다릅니다. 이러한 구성 요소에는 `CommunityVersion-amzn-EmrVersion` 양식의 버전 레이블이 있습니다. `EmrVersion`은 0에서 시작합니다. 예를 들어, 버전 2.2의 `myapp-component`라는 오픈 소스 커뮤니티 구성 요소가 다른 Amazon EMR 릴리스에 포함되도록 세 번 수정된 경우 해당 릴리스 버전은 `2.2-amzn-2`로 나열됩니다.
| 구성 요소 | 버전 | 설명 |
| --- | --- | --- |
| adot-java-agent | 1.31.0 | 애플리케이션 대몬(daemon)에서 지표를 수집하는 Java 에이전트입니다. |
| delta | 3.2.0-amzn-1 | Delta Lake는 방대한 분석 데이터 세트를 위한 오픈 테이블 형식입니다. |
| emr-amazon-cloudwatch-agent | 1.300032.2-amzn-0 | Amazon EC2 인스턴스에서 내부 시스템 수준 지표와 사용자 지정 애플리케이션 지표를 수집하는 애플리케이션입니다. |
| emr-ddb | 5.6.0 | 하둡 에코시스템 애플리케이션용 Amazon DynamoDB 커넥터 |
| emr-goodies | 3.13.0 | 편리한 하둡 에코시스템용 추가 라이브러리 |
| emr-kinesis | 3.17.0 | 하둡 에코시스템 애플리케이션용 Amazon Kinesis 커넥터. |
| emr-notebook-env | 1.17.0 | Jupyter Enterprise Gateway가 포함된 EMR 노트북용 Conda 환경 |
| emr-s3-dist-cp | 2.34.0 | Amazon S3용으로 최적화된 분사 복사 애플리케이션. |
| emr-s3-select | 2.13.0 | EMR S3Select 커넥터 |
| emr-wal-cli | 1.3.1 | emrwal 목록/삭제에 사용되는 CLI입니다. |
| emrfs | 2.65.0 | 하둡 에코시스템 애플리케이션용 Amazon S3 커넥터. |
| flink-client | 1.19.1-amzn-0 | Apache Flink 명령줄 클라이언트 스크립트 및 애플리케이션 |
| flink-jobmanager-config | 1.19.1-amzn-0 | Apache Flink JobManager에 대한 EMR 노드에서 리소스를 관리합니다. |
| hadoop-client | 3.4.0-amzn-0 | 'hdfs', 'hadoop', 'yarn' 등과 같은 하둡 명령줄 클라이언트 |
| hadoop-hdfs-datanode | 3.4.0-amzn-0 | 블록을 저장하는 HDFS 노드 수준 서비스 |
| hadoop-hdfs-library | 3.4.0-amzn-0 | HDFS 명령줄 클라이언트 및 라이브러리 |
| hadoop-hdfs-namenode | 3.4.0-amzn-0 | 파일 이름 및 블록 위치를 추적하는 HDFS 서비스 |
| hadoop-hdfs-journalnode | 3.4.0-amzn-0 | HA 클러스터에서 하둡 파일 시스템 저널을 관리하기 위한 HDFS 서비스 |
| hadoop-httpfs-server | 3.4.0-amzn-0 | HDFS 작업에 대한 HTTP 엔드포인트 |
| hadoop-kms-server | 3.4.0-amzn-0 | 하둡의 KeyProvider API를 기반으로 하는 암호화 키 관리 서버 |
| hadoop-mapred | 3.4.0-amzn-0 | MapReduce 애플리케이션을 실행하는 MapReduce 실행 엔진 라이브러리 |
| hadoop-yarn-nodemanager | 3.4.0-amzn-0 | 개별 노드의 컨테이너를 관리하는 YARN 서비스 |
| hadoop-yarn-resourcemanager | 3.4.0-amzn-0 | 클러스터 리소스 및 분산 애플리케이션을 할당 및 관리하는 YARN 서비스 |
| hadoop-yarn-timeline-server | 3.4.0-amzn-0 | YARN 애플리케이션의 현재 및 기록 정보를 가져오는 서비스 |
| hbase-hmaster | 2.5.5-amzn-0 | 리전 조정 및 관리 명령의 실행을 담당하는 HBase 클러스터용 서비스 |
| hbase-region-server | 2.5.5-amzn-0 | 한 개 이상의 HBase 리전에 서비스를 제공하는 서비스 |
| hbase-client | 2.5.5-amzn-0 | HBase 명령줄 클라이언트 |
| hbase-rest-server | 2.5.5-amzn-0 | HBase용 RESTful HTTP 엔드포인트를 제공하는 서비스 |
| hbase-thrift-server | 2.5.5-amzn-0 | HBase에 Thrift 엔드포인트를 제공하는 서비스 |
| hbase-operator-tools | 2.5.5-amzn-0 | Apache HBase 클러스터용 복구 도구. |
| hcatalog-client | 3.1.3-amzn-13 | hcatalog-server를 조정하기 위한 'hcat' 명령줄 클라이언트 |
| hcatalog-server | 3.1.3-amzn-13 | 분산 애플리케이션용 스토리지 관리 계층, 테이블 및 HCatalog를 제공하는 서비스 |
| hcatalog-webhcat-server | 3.1.3-amzn-13 | HCatalog에 REST 인터페이스를 제공하는 HTTP 엔드포인트 |
| hive-client | 3.1.3-amzn-13 | Hive 명령줄 클라이언트 |
| hive-hbase | 3.1.3-amzn-13 | Hive-hbase 클라이언트 |
| hive-metastore-server | 3.1.3-amzn-13 | 하둡 작업에 대한 SQL용 메타데이터가 저장되는 시맨틱 리포지토리인 Hive 메타스토어에 액세스하기 위한 서비스 |
| hive-server2 | 3.1.3-amzn-13 | Hive 쿼리를 웹 요청으로 수락하기 위한 서비스 |
| hudi | 0.15.0-amzn-1 | 짧은 지연 시간 및 높은 효율성으로 데이터 파이프라인을 구동하는 증분 처리 프레임워크. |
| hudi-presto | 0.15.0-amzn-1 | Hudi로 Presto를 실행하기 위한 번들 라이브러리. |
| hudi-trino | 0.15.0-amzn-1 | Hudi와 함께 Trnio를 실행하기 위한 번들 라이브러리. |
| hudi-spark | 0.15.0-amzn-1 | Hudi와 함께 Spark를 실행하기 위한 번들 라이브러리. |
| hue-server | 4.11.0 | 하둡 에코시스템 애플리케이션을 사용하여 데이터를 분석하는 웹 애플리케이션. |
| iceberg | 1.6.1-amzn-0 | Apache Iceberg는 방대한 분석 데이터 세트를 위한 오픈 테이블 형식입니다. |
| jupyterhub | 1.5.0 | Jupyter Notebook용 다중 사용자 서버 |
| livy-server | 0.8.0-incubating | Apache Spark와 상호작용하기 위한 REST 인터페이스 |
| nginx | 1.12.1 | HTTP인 nginx [engine x] 및 역방향 프록시 서버 |
| mariadb-server | 5.5.68 이상 | MariaDB 데이터베이스 서버. |
| nvidia-cuda | 12.3.0 | Nvidia 드라이버와 Cuda 도구 키트 |
| oozie-client | 5.2.1 | Oozie 명령줄 클라이언트 |
| oozie-server | 5.2.1 | Oozie 워크플로 요청을 수락하는 서비스 |
| opencv | 4.7.0 | 오픈 소스 컴퓨터 비전 라이브러리. |
| phoenix-library | 5.2.0 | 서버 및 클라이언트의 phoenix 라이브러리 |
| phoenix-connectors | 6.0.0 | Spark-3용 Apache Phoenix 커넥터 |
| phoenix-query-server | 6.0.0 | Avatica API에 대한 JSON 형식 액세스 및 프로토콜 버퍼 액세스를 비롯하여 JDBC 액세스를 제공하는 경량 서버 |
| presto-coordinator | 0.287-amzn-0 | presto-worker의 쿼리를 수락하고 쿼리 실행을 관리하는 서비스. |
| presto-worker | 0.287-amzn-0 | 여러 쿼리를 실행하는 서비스. |
| presto-client | 0.287-amzn-0 | Presto 서버가 시작되지 않은 HA 클러스터의 대기 마스터에 설치된 Presto 명령줄 클라이언트. |
| trino-coordinator | 446-amzn-0 | trino-workers의 쿼리를 수락하고 쿼리 실행을 관리하는 서비스. |
| trino-worker | 446-amzn-0 | 여러 쿼리를 실행하는 서비스. |
| trino-client | 446-amzn-0 | Trino 서버가 시작되지 않은 HA 클러스터의 대기 마스터에 설치된 Trino 명령줄 클라이언트. |
| pig-client | 0.17.0 | Pig 명령줄 클라이언트. |
| r | 4.3.2 | 통계 컴퓨팅용 R 프로젝트 |
| ranger-kms-server | 2.0.0 | Apache Ranger 키 관리 시스템 |
| spark-client | 3.5.2-amzn-0 | Spark 명령줄 클라이언트. |
| spark-history-server | 3.5.2-amzn-0 | 완료된 Spark 애플리케이션의 수명에 대해 기록된 이벤트를 조회하는 웹 UI. |
| spark-on-yarn | 3.5.2-amzn-0 | YARN용 인 메모리 실행 엔진. |
| spark-yarn-slave | 3.5.2-amzn-0 | YARN 슬레이브에서 필요한 Apache Spark 라이브러리. |
| spark-rapids | 24.08.1-amzn-0 | GPU로 Apache Spark를 가속화하는 Nvidia Spark RAPIDS 플러그인. |
| sqoop-client | 1.4.7 | Apache Sqoop 명령줄 클라이언트. |
| tensorflow | 2.16.1 | TensorFlow는 고성능 수치 계산용 오픈 소스 소프트웨어 라이브러리입니다. |
| tez-on-yarn | 0.10.2-amzn-11 | tez YARN 애플리케이션 및 라이브러리. |
| tez-on-worker | 0.10.2-amzn-11 | 워커 노드에 대한 tez YARN 애플리케이션 및 라이브러리. |
| zeppelin-server | 0.11.1 | 대화형 데이터 분석이 가능한 웹 기반 노트북 |
| zookeeper-server | 3.9.2-amzn-0 | 구성 정보 유지 관리, 이름 지정, 분산 동기화 제공 및 그룹 서비스 제공을 위한 중앙 집중식 서비스. |
| zookeeper-client | 3.9.2-amzn-0 | ZooKeeper 명령줄 클라이언트. |
## 7.4.0 구성 분류
구성 분류를 사용하면 애플리케이션을 사용자 지정할 수 있습니다. 이는 종종 `hive-site.xml`과 같이 애플리케이션의 구성 XML 파일에 해당합니다. 자세한 내용은 [애플리케이션 구성](emr-configure-apps.md) 단원을 참조하십시오.
재구성 작업은 실행 중인 클러스터의 인스턴스 그룹에 대한 구성을 지정할 때 수행됩니다. Amazon EMR은 사용자가 수정한 분류에 대한 재구성 작업만 시작합니다. 자세한 내용은 [실행 중인 클러스터에서 인스턴스 그룹 재구성](emr-configure-apps-running-cluster.md) 단원을 참조하십시오.
**emr-7.4.0 분류**
| 분류 | 설명 | 재구성 작업 |
| --- | --- | --- |
| capacity-scheduler | Hadoop capacity-scheduler.xml 파일에서 값을 변경합니다. | Restarts the ResourceManager service. |
| container-executor | Hadoop YARN container-executor.cfg 파일에서 값을 변경합니다. | Not available. |
| container-log4j | Hadoop YARN container-log4j.properties 파일에서 값을 변경합니다. | Not available. |
| core-site | Hadoop core-site.xml 파일에서 값을 변경합니다. | Restarts the Hadoop HDFS services Namenode, SecondaryNamenode, Datanode, ZKFC, and Journalnode. Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts Hadoop KMS, Ranger KMS, HiveServer2, Hive MetaStore, Hadoop Httpfs, and MapReduce-HistoryServer. |
| docker-conf | Docker 관련 설정을 변경합니다. | Not available. |
| emrfs-site | EMRFS 설정을 변경합니다. | Restarts the Hadoop HDFS services Namenode, SecondaryNamenode, Datanode, ZKFC, and Journalnode. Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts HBaseRegionserver, HBaseMaster, HBaseThrift, HBaseRest, HiveServer2, Hive MetaStore, Hadoop Httpfs, and MapReduce-HistoryServer. |
| flink-conf | flink-conf.yaml 설정을 변경합니다. | Restarts Flink history server. |
| flink-log4j | Flink log4j.properties 설정을 변경합니다. | Restarts Flink history server. |
| flink-log4j-session | Kubernetes 및 Yarn 세션에 대한 Flink log4j-session.properties 설정을 변경합니다. | Restarts Flink history server. |
| flink-log4j-cli | Flink log4j-cli.properties 설정을 변경합니다. | Restarts Flink history server. |
| hadoop-env | 모든 Hadoop 구성 요소에 대한 Hadoop 환경에서 값을 변경합니다. | Restarts the Hadoop HDFS services Namenode, SecondaryNamenode, Datanode, ZKFC, and Journalnode. Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts PhoenixQueryserver, HiveServer2, Hive MetaStore, and MapReduce-HistoryServer. |
| hadoop-log4j | Hadoop log4j.properties 파일에서 값을 변경합니다. | Restarts the Hadoop HDFS services SecondaryNamenode, Datanode, and Journalnode. Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts Hadoop KMS, Hadoop Httpfs, and MapReduce-HistoryServer. |
| hadoop-ssl-server | hadoop ssl 서버 구성을 변경합니다. | Not available. |
| hadoop-ssl-client | hadoop ssl 클라이언트 구성을 변경합니다. | Not available. |
| hbase | Apache HBase에 대한 Amazon EMR 큐레이트 설정입니다. | Custom EMR specific property. Sets emrfs-site and hbase-site configs. See those for their associated restarts. |
| hbase-env | HBase 환경에서 값을 변경합니다. | Restarts the HBase services RegionServer, HBaseMaster, ThriftServer, RestServer. |
| hbase-log4j | HBase hbase-log4j.properties 파일에서 값을 변경합니다. | Restarts the HBase services RegionServer, HBaseMaster, ThriftServer, RestServer. |
| hbase-metrics | HBase hadoop-metrics2-hbase.properties 파일에서 값을 변경합니다. | Restarts the HBase services RegionServer, HBaseMaster, ThriftServer, RestServer. |
| hbase-policy | HBase hbase-policy.xml 파일에서 값을 변경합니다. | Not available. |
| hbase-site | HBase hbase-site.xml 파일에서 값을 변경합니다. | Restarts the HBase services RegionServer, HBaseMaster, ThriftServer, RestServer. Additionally restarts Phoenix QueryServer. |
| hdfs-encryption-zones | HDFS 암호화 영역을 구성합니다. | This classification should not be reconfigured. |
| hdfs-env | HDFS 환경에서 값을 변경합니다. | Restarts Hadoop HDFS services Namenode, Datanode, and ZKFC. |
| hdfs-site | HDFS hdfs-site.xml에서 값을 변경합니다. | Restarts the Hadoop HDFS services Namenode, SecondaryNamenode, Datanode, ZKFC, and Journalnode. Additionally restarts Hadoop Httpfs. |
| hcatalog-env | HCatalog 환경에서 값을 변경합니다. | Restarts Hive HCatalog Server. |
| hcatalog-server-jndi | HCatalog jndi.properties 환경에서 값을 변경합니다. | Restarts Hive HCatalog Server. |
| hcatalog-server-proto-hive-site | HCatalog proto-hive-site.xml에서 값을 변경합니다. | Restarts Hive HCatalog Server. |
| hcatalog-webhcat-env | HCatalog WebHCat 환경에서 값을 변경합니다. | Restarts Hive WebHCat server. |
| hcatalog-webhcat-log4j2 | HCatalog WebHCat log4j2.properties에서 값을 변경합니다. | Restarts Hive WebHCat server. |
| hcatalog-webhcat-site | HCatalog WebHCat webhcat-site.xml 파일에서 값을 변경합니다. | Restarts Hive WebHCat server. |
| hive | Apache Hive에 대한 Amazon EMR 큐레이트 설정입니다. | Sets configurations to launch Hive LLAP service. |
| hive-beeline-log4j2 | Hive beeline-log4j2.properties 파일에서 값을 변경합니다. | Not available. |
| hive-parquet-logging | Hive parquet-logging.properties 파일에서 값을 변경합니다. | Not available. |
| hive-env | Hive 환경에서 값을 변경합니다. | Restarts HiveServer2, HiveMetastore, and Hive HCatalog-Server. Runs Hive schemaTool CLI commands to verify hive-metastore. |
| hive-exec-log4j2 | Hive hive-exec-log4j2.properties 파일에서 값을 변경합니다. | Not available. |
| hive-llap-daemon-log4j2 | Hive llap-daemon-log4j2.properties 파일에서 값을 변경합니다. | Not available. |
| hive-log4j2 | Hive hive-log4j2.properties 파일에서 값을 변경합니다. | Not available. |
| hive-site | Hive hive-site.xml 파일에서 값을 변경합니다. | Restarts HiveServer2, HiveMetastore, and Hive HCatalog-Server. Runs Hive schemaTool CLI commands to verify hive-metastore. Also restarts Oozie and Zeppelin. |
| hiveserver2-site | Hive Server2 hiveserver2-site.xml 파일에서 값을 변경합니다. | Not available. |
| hue-ini | Hue ini 파일에서 값을 변경합니다. | Restarts Hue. Also activates Hue config override CLI commands to pick up new configurations. |
| httpfs-env | HTTPFS 환경에서 값을 변경합니다. | Restarts Hadoop Httpfs service. |
| httpfs-site | Hadoop httpfs-site.xml 파일에서 값을 변경합니다. | Restarts Hadoop Httpfs service. |
| hadoop-kms-acls | Hadoop kms-acls.xml 파일에서 값을 변경합니다. | Not available. |
| hadoop-kms-env | Hadoop KMS 환경에서 값을 변경합니다. | Restarts Hadoop-KMS service. |
| hadoop-kms-java-home | Hadoop의 KMS java 홈 변경 | Not available. |
| hadoop-kms-log4j | Hadoop kms-log4j.properties 파일에서 값을 변경합니다. | Not available. |
| hadoop-kms-site | Hadoop kms-site.xml 파일에서 값을 변경합니다. | Restarts Hadoop-KMS and Ranger-KMS service. |
| hudi-env | Hudi 환경에서 값을 변경합니다. | Not available. |
| hudi-defaults | Hudi hudi-defaults.conf 파일에서 값을 변경합니다. | Not available. |
| iceberg-defaults | Iceberg iceberg-defaults.conf 파일에서 값을 변경합니다. | Not available. |
| delta-defaults | Delta delta-defaults.conf 파일에서 값을 변경합니다. | Not available. |
| jupyter-notebook-conf | Jupyter Notebook jupyter\$1notebook\$1config.py 파일에서 값을 변경합니다. | Not available. |
| jupyter-hub-conf | JupyterHubs jupyterhub\$1config.py 파일에서 값을 변경합니다. | Not available. |
| jupyter-s3-conf | Jupyter Notebook S3 지속성 구성 | Not available. |
| jupyter-sparkmagic-conf | Sparkmagic config.json 파일에서 값을 변경합니다. | Not available. |
| livy-conf | Livy livy.conf 파일에서 값을 변경합니다. | Restarts Livy Server. |
| livy-env | Livy 환경에서 값을 변경합니다. | Restarts Livy Server. |
| livy-log4j2 | Livy log4j2.properties 설정을 변경합니다. | Restarts Livy Server. |
| mapred-env | MapReduce 애플리케이션 환경에서 값을 변경합니다. | Restarts Hadoop MapReduce-HistoryServer. |
| mapred-site | MapReduce 애플리케이션 mapred-site.xml 파일에서 값을 변경합니다. | Restarts Hadoop MapReduce-HistoryServer. |
| oozie-env | Oozie 환경에서 값을 변경합니다. | Restarts Oozie. |
| oozie-log4j | Oozie oozie-log4j.properties 파일에서 값을 변경합니다. | Restarts Oozie. |
| oozie-site | Oozie oozie-site.xml 파일에서 값을 변경합니다. | Restarts Oozie. |
| phoenix-hbase-metrics | Phoenix hadoop-metrics2-hbase.properties 파일에서 값을 변경합니다. | Not available. |
| phoenix-hbase-site | Phoenix hbase-site.xml 파일에서 값을 변경합니다. | Not available. |
| phoenix-log4j2 | Phoenix log4j2.properties 파일에서 값을 변경합니다. | Restarts Phoenix-QueryServer. |
| phoenix-metrics | Phoenix hadoop-metrics2-phoenix.properties 파일에서 값을 변경합니다. | Not available. |
| pig-env | Pig 환경에서 값을 변경합니다. | Not available. |
| pig-properties | Pig pig.properties 파일에서 값을 변경합니다. | Restarts Oozie. |
| pig-log4j | Pig log4j.properties 파일에서 값을 변경합니다. | Not available. |
| presto-log | Presto log.properties 파일에서 값을 변경합니다. | Restarts Presto-Server (for PrestoDB) |
| presto-config | Presto config.properties 파일에서 값을 변경합니다. | Restarts Presto-Server (for PrestoDB) |
| presto-password-authenticator | Presto password-authenticator.properties 파일에서 값을 변경합니다. | Not available. |
| presto-env | Presto presto-env.sh 파일에서 값을 변경합니다. | Restarts Presto-Server (for PrestoDB) |
| presto-node | Presto node.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-blackhole | Presto blackhole.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-cassandra | Presto cassandra.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-hive | Presto hive.properties 파일에서 값을 변경합니다. | Restarts Presto-Server (for PrestoDB) |
| presto-connector-jmx | Presto jmx.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-kafka | Presto kafka.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-lakeformation | Presto lakeformation.properties 파일에서 값을 변경합니다. | Restarts Presto-Server (for PrestoDB) |
| presto-connector-localfile | Presto localfile.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-memory | Presto memory.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-mongodb | Presto mongodb.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-mysql | Presto mysql.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-postgresql | Presto postgresql.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-raptor | Presto raptor.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-redis | Presto redis.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-redshift | Presto redshift.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-tpch | Presto tpch.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-tpcds | Presto tpcds.properties 파일에서 값을 변경합니다. | Not available. |
| trino-log | Trino log.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-config | Trino config.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-password-authenticator | Trino password-authenticator.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-env | Trino trino-env.sh 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-node | Trino node.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-blackhole | Trino blackhole.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-cassandra | Trino cassandra.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-delta | Trino delta.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-connector-hive | Trino hive.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-exchange-manager | Trino exchange-manager.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-connector-iceberg | Trino iceberg.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-connector-hudi | Trino hudi.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-connector-jmx | Trino jmx.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-kafka | Trino kafka.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-localfile | Trino localfile.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-memory | Trino memory.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-mongodb | Trino mongodb.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-mysql | Trino mysql.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-postgresql | Trino postgresql.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-raptor | Trino raptor.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-redis | Trino redis.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-redshift | Trino redshift.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-tpch | Trino tpch.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-tpcds | Trino tpcds.properties 파일에서 값을 변경합니다. | Not available. |
| ranger-kms-dbks-site | Ranger KMS dbks-site.xml 파일에서 값을 변경합니다. | Restarts Ranger KMS Server. |
| ranger-kms-site | Ranger KMS ranger-kms-site.xml 파일에서 값을 변경합니다. | Restarts Ranger KMS Server. |
| ranger-kms-env | Ranger KMS 환경에서 값을 변경합니다. | Restarts Ranger KMS Server. |
| ranger-kms-logback | Ranger KMS kms-logback.xml 파일에서 값을 변경합니다. | Not available. |
| ranger-kms-db-ca | Ranger KMS와의 MySQL SSL 연결에서 CA 파일의 값을 변경합니다. | Not available. |
| spark | Apache Spark에 대한 Amazon EMR 큐레이트 설정입니다. | This property modifies spark-defaults. See actions there. |
| spark-defaults | Spark spark-defaults.conf 파일에서 값을 변경합니다. | Restarts Spark history server and Spark thrift server. |
| spark-env | Spark 환경에서 값을 변경합니다. | Restarts Spark history server and Spark thrift server. |
| spark-hive-site | Spark hive-site.xml 파일에서 값을 변경합니다. | Not available. |
| spark-log4j2 | Spark log4j2.properties 파일에서 값을 변경합니다. | Restarts Spark history server and Spark thrift server. |
| spark-metrics | Spark metrics.properties 파일에서 값을 변경합니다. | Restarts Spark history server and Spark thrift server. |
| sqoop-env | Sqoop 환경에서 값을 변경합니다. | Not available. |
| sqoop-oraoop-site | Sqoop OraOop oraoop-site.xml 파일에서 값을 변경합니다. | Not available. |
| sqoop-site | Sqoop sqoop-site.xml 파일에서 값을 변경합니다. | Not available. |
| tez-site | Tez tez-site.xml 파일에서 값을 변경합니다. | Restart Oozie and HiveServer2. |
| yarn-env | YARN 환경에서 값을 변경합니다. | Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts MapReduce-HistoryServer. |
| yarn-site | YARN yarn-site.xml 파일에서 값을 변경합니다. | Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts Livy Server and MapReduce-HistoryServer. |
| zeppelin-env | Zeppelin 환경에서 값을 변경합니다. | Restarts Zeppelin. |
| zeppelin-site | zeppelin-site.xml에서 구성 설정을 변경합니다. | Restarts Zeppelin. |
| zookeeper-config | ZooKeeper zoo.cfg 파일에서 값을 변경합니다. | Restarts Zookeeper server. |
| zookeeper-logback | ZooKeeper logback.xml 파일에서 값을 변경합니다. | Restarts Zookeeper server. |
| emr-metrics | 이 노드에 대한 emr 지표 설정을 변경합니다. | Restarts the CloudWatchAgent service. |
## 7.4.0 변경 로그
**7.4.0 릴리스 및 릴리스 정보에 대한 변경 로그**
| Date | 이벤트 | 설명 |
| --- | --- | --- |
| 2024-11-18 | 문서 게시 | Amazon EMR 7.4.0 릴리스 정보 최초 게시 |
| 2024-11-13 | 배포 완료 | [지원되는 모든 리전](https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/)에 Amazon EMR 7.4.0 완전 배포 |
| 2024-10-31 | 배포 시작 | Amazon EMR 7.4.0이 초기 상용 리전에 처음 배포됨 |
# Amazon EMR 릴리스 7.3.0
## 7.3.0 지원 수명 주기
다음 표에서는 Amazon EMR 릴리스 7.3.0에 대해 지원되는 수명 주기 날짜를 설명합니다.
| 지원 단계 | Date |
| --- | --- |
| 초기 릴리스 날짜 | 2024년 10월 16일 |
| 표준 지원 종료 시점 | 2026년 10월 15일 |
| 지원 종료 | 2026년 10월 16일 |
| 수명 종료 | 2027년 10월 16일 |
## 7.3.0 애플리케이션 버전
이 릴리스에서 지원되는 애플리케이션은 [https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Install-CloudWatch-Agent.html](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Install-CloudWatch-Agent.html), [https://delta.io/](https://delta.io/), [https://flink.apache.org/](https://flink.apache.org/), [http://hbase.apache.org/](http://hbase.apache.org/), [https://cwiki.apache.org/confluence/display/Hive/HCatalog](https://cwiki.apache.org/confluence/display/Hive/HCatalog), [http://hadoop.apache.org/docs/current/](http://hadoop.apache.org/docs/current/), [http://hive.apache.org/](http://hive.apache.org/), [https://hudi.apache.org](https://hudi.apache.org), [http://gethue.com/](http://gethue.com/), [https://iceberg.apache.org/](https://iceberg.apache.org/), [https://jupyter-enterprise-gateway.readthedocs.io/en/latest/](https://jupyter-enterprise-gateway.readthedocs.io/en/latest/), [https://jupyterhub.readthedocs.io/en/latest/#](https://jupyterhub.readthedocs.io/en/latest/#), [https://livy.incubator.apache.org/](https://livy.incubator.apache.org/), [http://oozie.apache.org/](http://oozie.apache.org/), [https://phoenix.apache.org/](https://phoenix.apache.org/), [http://pig.apache.org/](http://pig.apache.org/), [https://prestodb.io/](https://prestodb.io/), [https://spark.apache.org/docs/latest/](https://spark.apache.org/docs/latest/), [http://sqoop.apache.org/](http://sqoop.apache.org/), [https://www.tensorflow.org/](https://www.tensorflow.org/), [https://tez.apache.org/](https://tez.apache.org/), [https://trino.io/](https://trino.io/), [https://zeppelin.incubator.apache.org/](https://zeppelin.incubator.apache.org/), [https://zookeeper.apache.org](https://zookeeper.apache.org)입니다.
아래 테이블에는 이번 Amazon EMR 릴리스에서 사용할 수 있는 애플리케이션 버전과 이전 세 가지 Amazon EMR 릴리스(해당하는 경우)의 애플리케이션 버전이 나와 있습니다.
각 Amazon EMR 릴리스에서 애플리케이션 버전의 전체 기록은 다음 주제를 참조하세요.
+ [Amazon EMR 7.x 릴리스의 애플리케이션 버전](emr-release-app-versions-7.x.md)
+ [Amazon EMR 6.x 릴리스의 애플리케이션 버전](emr-release-app-versions-6.x.md)
+ [Amazon EMR 5.x 릴리스의 애플리케이션 버전](emr-release-app-versions-5.x.md)
+ [Amazon EMR 4.x 릴리스의 애플리케이션 버전](emr-release-app-versions-4.x.md)
**애플리케이션 버전 정보**
| | emr-7.3.0 | emr-7.2.0 | emr-7.1.0 | emr-7.0.0 |
| --- | --- | --- | --- | --- |
| AWS Java용 SDK | 2.25.70, 1.12.747 | 2.23.18, 1.12.705 | 2.23.18, 1.12.656 | 2.20.160-amzn-0, 1.12.569 |
| Python | 3.9, 3.11 | 3.9, 3.11 | 3.9, 3.11 | 3.9 |
| Scala | 2.12.18 | 2.12.17 | 2.12.17 | 2.12.17 |
| AmazonCloudWatchAgent | 1.300032.2-amzn-0 | 1.300032.2-amzn-0 | 1.300032.2-amzn-0 | 1.300031.1-amzn-0 |
| Delta | 3.2.0-amzn-0 | 3.1.0 | 3.0.0 | 3.0.0 |
| Flink | 1.18.1-amzn-2 | 1.18.1-amzn-1 | 1.18.1-amzn-0 | 1.18.0-amzn-0 |
| Ganglia | - | - | - | - |
| HBase | 2.4.17-amzn-7 | 2.4.17-amzn-6 | 2.4.17-amzn-5 | 2.4.17-amzn-4 |
| HCatalog | 3.1.3-amzn-12 | 3.1.3-amzn-11 | 3.1.3-amzn-10 | 3.1.3-amzn-9 |
| Hadoop | 3.3.6-amzn-5 | 3.3.6-amzn-4 | 3.3.6-amzn-3 | 3.3.6-amzn-2 |
| Hive | 3.1.3-amzn-12 | 3.1.3-amzn-11 | 3.1.3-amzn-10 | 3.1.3-amzn-9 |
| Hudi | 0.15.0-amzn-0 | 0.14.1-amzn-1 | 0.14.1-amzn-0 | 0.14.0-amzn-1 |
| Hue | 4.11.0 | 4.11.0 | 4.11.0 | 4.11.0 |
| Iceberg | 1.5.2-amzn-0 | 1.5.0-amzn-0 | 1.4.3-amzn-0 | 1.4.2-amzn-0 |
| JupyterEnterpriseGateway | 2.6.0 | 2.6.0 | 2.6.0 | 2.6.0 |
| JupyterHub | 1.5.0 | 1.5.0 | 1.5.0 | 1.5.0 |
| Livy | 0.8.0-incubating | 0.8.0-incubating | 0.8.0-incubating | 0.7.1-incubating |
| MXNet | - | 1.9.1 | 1.9.1 | 1.9.1 |
| Mahout | - | - | - | - |
| Oozie | 5.2.1 | 5.2.1 | 5.2.1 | 5.2.1 |
| Phoenix | 5.1.3 | 5.1.3 | 5.1.3 | 5.1.3 |
| Pig | 0.17.0 | 0.17.0 | 0.17.0 | 0.17.0 |
| Presto | 0.285-amzn-1 | 0.285-amzn-0 | 0.284-amzn-0 | 0.283-amzn-1 |
| Spark | 3.5.1-amzn-1 | 3.5.1-amzn-0 | 3.5.0-amzn-1 | 3.5.0-amzn-0 |
| Sqoop | 1.4.7 | 1.4.7 | 1.4.7 | 1.4.7 |
| TensorFlow | 2.16.1 | 2.11.0 | 2.11.0 | 2.11.0 |
| Tez | 0.10.2-amzn-10 | 0.10.2-amzn-9 | 0.10.2-amzn-8 | 0.10.2-amzn-7 |
| Trino (PrestoSQL) | 442-amzn-0 | 436-amzn-0 | 435-amzn-0 | 426-amzn-1 |
| Zeppelin | 0.11.1 | 0.10.1 | 0.10.1 | 0.10.1 |
| ZooKeeper | 3.9.1-amzn-1 | 3.9.1-amzn-1 | 3.9.1-amzn-0 | 3.5.10 |
# 7.3.0 릴리스 구성 요소 세부 정보
Amazon EMR 7.3.0의 *추가 항목* 패키지에 대한 자세한 내용은 다음 표를 참조하세요.
| 애플리케이션 | 애플리케이션 유형 | 패키지 | 패키지 유형 | 패키지 버전 |
| --- | --- | --- | --- | --- |
| AmazonCloudWatchAgent | Core | hadoop-hdfs-journalnode | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| AmazonCloudWatchAgent | Core | ranger-kms | 추가 항목 | 2.0.0-1.amzn2023 |
| AmazonCloudWatchAgent | Core | s3-dist-cp | 추가 항목 | 2.33.0-1.amzn2023 |
| AmazonCloudWatchAgent | Core | zookeeper | 추가 항목 | 3.9.1.amzn.1-1.amzn2023 |
| AmazonCloudWatchAgent | Core | zookeeper-server | 추가 항목 | 3.9.1.amzn.1-1.amzn2023 |
| Flink | Core | hadoop-client | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Flink | Core | hadoop-hdfs | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Flink | Core | hadoop-hdfs-datanode | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Flink | Core | hadoop-hdfs-journalnode | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Flink | Core | hadoop-hdfs-namenode | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Flink | Core | hadoop-httpfs | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Flink | Core | hadoop-kms | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Flink | Core | hadoop-mapreduce | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Flink | Core | hadoop-mapreduce-historyserver | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Flink | Core | hadoop-yarn | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Flink | Core | hadoop-yarn-nodemanager | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Flink | Core | hadoop-yarn-proxyserver | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Flink | Core | hadoop-yarn-resourcemanager | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Flink | Core | hadoop-yarn-timelineserver | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Flink | Core | hudi | 추가 항목 | 0.15.0.amzn.0-1.amzn2023 |
| Flink | Core | ranger-kms | 추가 항목 | 2.0.0-1.amzn2023 |
| Flink | Core | hadoop | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| HBase | Core | s3-dist-cp | 추가 항목 | 2.33.0-1.amzn2023 |
| HCatalog | Core | hadoop-yarn-proxyserver | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| HCatalog | Core | mariadb-connector-java | 추가 항목 | |
| Hive | Core | hadoop-httpfs | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Hive | Core | hadoop-yarn-proxyserver | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Hive | Core | hive-hbase | 추가 항목 | 3.1.3.amzn.12-1.amzn2023 |
| Hive | Core | mariadb-connector-java | 추가 항목 | 2.7.2-1 |
| Hive | Core | s3-dist-cp | 추가 항목 | 2.33.0-1.amzn2023 |
| 피닉스 | Core | s3-dist-cp | 추가 항목 | 2.33.0-1.amzn2023 |
| Spark | Core | spark-datanucleus | 추가 항목 | 3.5.1.amzn.0-1.amzn2023 |
| Tez의 Hive 실행 시간 비교 | Core | hadoop-mapreduce | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Tez의 Hive 실행 시간 비교 | Core | hadoop-mapreduce-historyserver | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Tez의 Hive 실행 시간 비교 | Core | hadoop-yarn-proxyserver | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Trino | Core | bigtop-utils | 추가 항목 | 1.2.0-1.amzn2023 |
| Trino | Core | hadoop-client | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Trino | Core | hadoop-hdfs | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Trino | Core | hadoop-hdfs-datanode | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Trino | Core | hadoop-hdfs-journalnode | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Trino | Core | hadoop-hdfs-namenode | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Trino | Core | hadoop-kms | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Trino | Core | hadoop-mapreduce | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Trino | Core | hadoop-mapreduce-historyserver | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Trino | Core | hadoop-yarn | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Trino | Core | hadoop-yarn-nodemanager | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Trino | Core | hadoop-yarn-proxyserver | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Trino | Core | hadoop-yarn-resourcemanager | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Trino | Core | hadoop-yarn-timelineserver | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Trino | Core | hive | 추가 항목 | 3.1.3.amzn.12-1.amzn2023 |
| Trino | Core | hive-hcatalog-server | 추가 항목 | 3.1.3.amzn.12-1.amzn2023 |
| Trino | Core | mariadb-connector-java | 추가 항목 | 2.7.2-1 |
| Trino | Core | ranger-kms | 추가 항목 | 2.0.0-1.amzn2023 |
| Trino | Core | zookeeper | 추가 항목 | 3.9.1.amzn.1-1.amzn2023 |
| Trino | Core | zookeeper-server | 추가 항목 | 3.9.1.amzn.1-1.amzn2023 |
| Trino | Core | bigtop-groovy | 추가 항목 | 2.5.4-1.amzn2023 |
| Trino | Core | bigtop-jsvc | 추가 항목 | 1.2.4-1.amzn2023 |
| Trino | Core | hadoop | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Trino | Core | hadoop-lzo | 추가 항목 | 0.4.19-1.amzn2023 |
| Trino | Core | hive-hcatalog | 추가 항목 | 3.1.3.amzn.12-1.amzn2023 |
| Trino | Core | hive-jdbc | 추가 항목 | 3.1.3.amzn.12-1.amzn2023 |
| Zookeeper | Core | emrfs | 추가 항목 | 2.64.0-1.amzn2023 |
| Zookeeper | Core | hadoop-client | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Zookeeper | Core | hadoop-hdfs | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Zookeeper | Core | hadoop-hdfs-datanode | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Zookeeper | Core | hadoop-hdfs-journalnode | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Zookeeper | Core | hadoop-hdfs-namenode | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Zookeeper | Core | hadoop-httpfs | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Zookeeper | Core | hadoop-kms | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Zookeeper | Core | hadoop-mapreduce | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Zookeeper | Core | hadoop-mapreduce-historyserver | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Zookeeper | Core | hadoop-yarn | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Zookeeper | Core | hadoop-yarn-nodemanager | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Zookeeper | Core | hadoop-yarn-proxyserver | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Zookeeper | Core | hadoop-yarn-resourcemanager | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Zookeeper | Core | hadoop-yarn-timelineserver | 추가 항목 | 3.3.6.amzn.5-1.amzn2023 |
| Zookeeper | Core | ranger-kms | 추가 항목 | 2.0.0-1.amzn2023 |
# 7.3.0 일반적인 취약성 및 노출
다음 표에는 Amazon EMR 7.3.0의 권장 구성에서 실행되는 EMR 클러스터에 영향을 주지 않는 모든 CVE가 나와 있습니다. Amazon EMR은 업스트림 오픈 소스의 수정 사항 가용성에 종속되어 있으며, Amazon EMR이 수정 사항을 확인한 후 90일 이내에 코어 엔진 구성 요소의 일부로 안정적인 최신 버전을 제공합니다.
이 표는 2024년 10월 3일에 업데이트되었습니다.
| CVE ID | 심각도 | CVE 세부 정보 URL |
| --- | --- | --- |
| CVE-2015-1832 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2015-1832](https://nvd.nist.gov/vuln/detail/CVE-2015-1832) |
| CVE-2016-5018 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2016-5018](https://nvd.nist.gov/vuln/detail/CVE-2016-5018) |
| CVE-2018-11307 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-11307](https://nvd.nist.gov/vuln/detail/CVE-2018-11307) |
| CVE-2018-14718 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-14718](https://nvd.nist.gov/vuln/detail/CVE-2018-14718) |
| CVE-2018-14719 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-14719](https://nvd.nist.gov/vuln/detail/CVE-2018-14719) |
| CVE-2018-14720 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-14720](https://nvd.nist.gov/vuln/detail/CVE-2018-14720) |
| CVE-2018-14721 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-14721](https://nvd.nist.gov/vuln/detail/CVE-2018-14721) |
| CVE-2018-19360 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-19360](https://nvd.nist.gov/vuln/detail/CVE-2018-19360) |
| CVE-2018-19361 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-19361](https://nvd.nist.gov/vuln/detail/CVE-2018-19361) |
| CVE-2018-19362 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-19362](https://nvd.nist.gov/vuln/detail/CVE-2018-19362) |
| CVE-2018-7489 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-7489](https://nvd.nist.gov/vuln/detail/CVE-2018-7489) |
| CVE-2019-14379 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14379](https://nvd.nist.gov/vuln/detail/CVE-2019-14379) |
| CVE-2019-14540 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14540](https://nvd.nist.gov/vuln/detail/CVE-2019-14540) |
| CVE-2019-14892 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14892](https://nvd.nist.gov/vuln/detail/CVE-2019-14892) |
| CVE-2019-14893 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14893](https://nvd.nist.gov/vuln/detail/CVE-2019-14893) |
| CVE-2019-16335 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-16335](https://nvd.nist.gov/vuln/detail/CVE-2019-16335) |
| CVE-2019-16942 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-16942](https://nvd.nist.gov/vuln/detail/CVE-2019-16942) |
| CVE-2019-16943 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-16943](https://nvd.nist.gov/vuln/detail/CVE-2019-16943) |
| CVE-2019-17267 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-17267](https://nvd.nist.gov/vuln/detail/CVE-2019-17267) |
| CVE-2019-17531 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-17531](https://nvd.nist.gov/vuln/detail/CVE-2019-17531) |
| CVE-2019-20330 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-20330](https://nvd.nist.gov/vuln/detail/CVE-2019-20330) |
| CVE-2019-20444 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-20444](https://nvd.nist.gov/vuln/detail/CVE-2019-20444) |
| CVE-2019-20445 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-20445](https://nvd.nist.gov/vuln/detail/CVE-2019-20445) |
| CVE-2020-8840 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8840](https://nvd.nist.gov/vuln/detail/CVE-2020-8840) |
| CVE-2020-9546 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-9546](https://nvd.nist.gov/vuln/detail/CVE-2020-9546) |
| CVE-2020-9547 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-9547](https://nvd.nist.gov/vuln/detail/CVE-2020-9547) |
| CVE-2020-9548 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-9548](https://nvd.nist.gov/vuln/detail/CVE-2020-9548) |
| CVE-2022-1471 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-1471](https://nvd.nist.gov/vuln/detail/CVE-2022-1471) |
| CVE-2022-1471 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-1471](https://nvd.nist.gov/vuln/detail/CVE-2022-1471) |
| CVE-2022-1471 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-1471](https://nvd.nist.gov/vuln/detail/CVE-2022-1471) |
| CVE-2022-37865 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-37865](https://nvd.nist.gov/vuln/detail/CVE-2022-37865) |
| CVE-2022-39135 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-39135](https://nvd.nist.gov/vuln/detail/CVE-2022-39135) |
| CVE-2022-46337 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-46337](https://nvd.nist.gov/vuln/detail/CVE-2022-46337) |
| CVE-2022-46337 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-46337](https://nvd.nist.gov/vuln/detail/CVE-2022-46337) |
| CVE-2023-44981 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2023-44981](https://nvd.nist.gov/vuln/detail/CVE-2023-44981) |
| CVE-2023-44981 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2023-44981](https://nvd.nist.gov/vuln/detail/CVE-2023-44981) |
| CVE-2023-44981 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2023-44981](https://nvd.nist.gov/vuln/detail/CVE-2023-44981) |
| CVE-2012-0881 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2012-0881](https://nvd.nist.gov/vuln/detail/CVE-2012-0881) |
| CVE-2013-4002 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2013-4002](https://nvd.nist.gov/vuln/detail/CVE-2013-4002) |
| CVE-2015-2156 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2015-2156](https://nvd.nist.gov/vuln/detail/CVE-2015-2156) |
| CVE-2015-5237 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2015-5237](https://nvd.nist.gov/vuln/detail/CVE-2015-5237) |
| CVE-2016-6796 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2016-6796](https://nvd.nist.gov/vuln/detail/CVE-2016-6796) |
| CVE-2017-18640 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2017-18640](https://nvd.nist.gov/vuln/detail/CVE-2017-18640) |
| CVE-2017-18640 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2017-18640](https://nvd.nist.gov/vuln/detail/CVE-2017-18640) |
| CVE-2018-1000180 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-1000180](https://nvd.nist.gov/vuln/detail/CVE-2018-1000180) |
| CVE-2018-12022 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-12022](https://nvd.nist.gov/vuln/detail/CVE-2018-12022) |
| CVE-2018-12023 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-12023](https://nvd.nist.gov/vuln/detail/CVE-2018-12023) |
| CVE-2019-0205 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-0205](https://nvd.nist.gov/vuln/detail/CVE-2019-0205) |
| CVE-2019-0205 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-0205](https://nvd.nist.gov/vuln/detail/CVE-2019-0205) |
| CVE-2019-12086 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-12086](https://nvd.nist.gov/vuln/detail/CVE-2019-12086) |
| CVE-2019-14439 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14439](https://nvd.nist.gov/vuln/detail/CVE-2019-14439) |
| CVE-2019-16869 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-16869](https://nvd.nist.gov/vuln/detail/CVE-2019-16869) |
| CVE-2020-10650 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10650](https://nvd.nist.gov/vuln/detail/CVE-2020-10650) |
| CVE-2020-10672 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10672](https://nvd.nist.gov/vuln/detail/CVE-2020-10672) |
| CVE-2020-10673 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10673](https://nvd.nist.gov/vuln/detail/CVE-2020-10673) |
| CVE-2020-10968 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10968](https://nvd.nist.gov/vuln/detail/CVE-2020-10968) |
| CVE-2020-10969 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10969](https://nvd.nist.gov/vuln/detail/CVE-2020-10969) |
| CVE-2020-11111 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11111](https://nvd.nist.gov/vuln/detail/CVE-2020-11111) |
| CVE-2020-11112 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11112](https://nvd.nist.gov/vuln/detail/CVE-2020-11112) |
| CVE-2020-11113 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11113](https://nvd.nist.gov/vuln/detail/CVE-2020-11113) |
| CVE-2020-11619 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11619](https://nvd.nist.gov/vuln/detail/CVE-2020-11619) |
| CVE-2020-11620 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11620](https://nvd.nist.gov/vuln/detail/CVE-2020-11620) |
| CVE-2020-13936 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-13936](https://nvd.nist.gov/vuln/detail/CVE-2020-13936) |
| CVE-2020-13949 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-13949](https://nvd.nist.gov/vuln/detail/CVE-2020-13949) |
| CVE-2020-13949 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-13949](https://nvd.nist.gov/vuln/detail/CVE-2020-13949) |
| CVE-2020-13949 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-13949](https://nvd.nist.gov/vuln/detail/CVE-2020-13949) |
| CVE-2020-14060 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14060](https://nvd.nist.gov/vuln/detail/CVE-2020-14060) |
| CVE-2020-14061 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14061](https://nvd.nist.gov/vuln/detail/CVE-2020-14061) |
| CVE-2020-14062 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14062](https://nvd.nist.gov/vuln/detail/CVE-2020-14062) |
| CVE-2020-14195 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14195](https://nvd.nist.gov/vuln/detail/CVE-2020-14195) |
| CVE-2020-24616 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-24616](https://nvd.nist.gov/vuln/detail/CVE-2020-24616) |
| CVE-2020-24750 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-24750](https://nvd.nist.gov/vuln/detail/CVE-2020-24750) |
| CVE-2020-25649 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-25649](https://nvd.nist.gov/vuln/detail/CVE-2020-25649) |
| CVE-2020-28052 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-28052](https://nvd.nist.gov/vuln/detail/CVE-2020-28052) |
| CVE-2020-35490 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-35490](https://nvd.nist.gov/vuln/detail/CVE-2020-35490) |
| CVE-2020-35491 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-35491](https://nvd.nist.gov/vuln/detail/CVE-2020-35491) |
| CVE-2020-35728 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-35728](https://nvd.nist.gov/vuln/detail/CVE-2020-35728) |
| CVE-2020-36179 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36179](https://nvd.nist.gov/vuln/detail/CVE-2020-36179) |
| CVE-2020-36180 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36180](https://nvd.nist.gov/vuln/detail/CVE-2020-36180) |
| CVE-2020-36181 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36181](https://nvd.nist.gov/vuln/detail/CVE-2020-36181) |
| CVE-2020-36182 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36182](https://nvd.nist.gov/vuln/detail/CVE-2020-36182) |
| CVE-2020-36183 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36183](https://nvd.nist.gov/vuln/detail/CVE-2020-36183) |
| CVE-2020-36184 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36184](https://nvd.nist.gov/vuln/detail/CVE-2020-36184) |
| CVE-2020-36185 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36185](https://nvd.nist.gov/vuln/detail/CVE-2020-36185) |
| CVE-2020-36186 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36186](https://nvd.nist.gov/vuln/detail/CVE-2020-36186) |
| CVE-2020-36187 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36187](https://nvd.nist.gov/vuln/detail/CVE-2020-36187) |
| CVE-2020-36188 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36188](https://nvd.nist.gov/vuln/detail/CVE-2020-36188) |
| CVE-2020-36189 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36189](https://nvd.nist.gov/vuln/detail/CVE-2020-36189) |
| CVE-2020-36518 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36518](https://nvd.nist.gov/vuln/detail/CVE-2020-36518) |
| CVE-2021-20190 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-20190](https://nvd.nist.gov/vuln/detail/CVE-2021-20190) |
| CVE-2021-31684 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-31684](https://nvd.nist.gov/vuln/detail/CVE-2021-31684) |
| CVE-2021-31684 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-31684](https://nvd.nist.gov/vuln/detail/CVE-2021-31684) |
| CVE-2021-34538 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-34538](https://nvd.nist.gov/vuln/detail/CVE-2021-34538) |
| CVE-2021-34538 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-34538](https://nvd.nist.gov/vuln/detail/CVE-2021-34538) |
| CVE-2021-34538 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-34538](https://nvd.nist.gov/vuln/detail/CVE-2021-34538) |
| CVE-2021-35515 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-35515](https://nvd.nist.gov/vuln/detail/CVE-2021-35515) |
| CVE-2021-35516 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-35516](https://nvd.nist.gov/vuln/detail/CVE-2021-35516) |
| CVE-2021-35517 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-35517](https://nvd.nist.gov/vuln/detail/CVE-2021-35517) |
| CVE-2021-36090 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-36090](https://nvd.nist.gov/vuln/detail/CVE-2021-36090) |
| CVE-2021-37136 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-37136](https://nvd.nist.gov/vuln/detail/CVE-2021-37136) |
| CVE-2021-37137 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-37137](https://nvd.nist.gov/vuln/detail/CVE-2021-37137) |
| CVE-2022-25647 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-25647](https://nvd.nist.gov/vuln/detail/CVE-2022-25647) |
| CVE-2022-25857 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-25857](https://nvd.nist.gov/vuln/detail/CVE-2022-25857) |
| CVE-2022-25857 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-25857](https://nvd.nist.gov/vuln/detail/CVE-2022-25857) |
| CVE-2022-25857 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-25857](https://nvd.nist.gov/vuln/detail/CVE-2022-25857) |
| CVE-2022-3171 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3171](https://nvd.nist.gov/vuln/detail/CVE-2022-3171) |
| CVE-2022-3171 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3171](https://nvd.nist.gov/vuln/detail/CVE-2022-3171) |
| CVE-2022-3171 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3171](https://nvd.nist.gov/vuln/detail/CVE-2022-3171) |
| CVE-2022-3509 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3509](https://nvd.nist.gov/vuln/detail/CVE-2022-3509) |
| CVE-2022-3509 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3509](https://nvd.nist.gov/vuln/detail/CVE-2022-3509) |
| CVE-2022-3509 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3509](https://nvd.nist.gov/vuln/detail/CVE-2022-3509) |
| CVE-2022-3510 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3510](https://nvd.nist.gov/vuln/detail/CVE-2022-3510) |
| CVE-2022-3510 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3510](https://nvd.nist.gov/vuln/detail/CVE-2022-3510) |
| CVE-2022-3510 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3510](https://nvd.nist.gov/vuln/detail/CVE-2022-3510) |
| CVE-2022-36364 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-36364](https://nvd.nist.gov/vuln/detail/CVE-2022-36364) |
| CVE-2022-37866 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-37866](https://nvd.nist.gov/vuln/detail/CVE-2022-37866) |
| CVE-2022-40149 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-40149](https://nvd.nist.gov/vuln/detail/CVE-2022-40149) |
| CVE-2022-40149 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-40149](https://nvd.nist.gov/vuln/detail/CVE-2022-40149) |
| CVE-2022-40149 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-40149](https://nvd.nist.gov/vuln/detail/CVE-2022-40149) |
| CVE-2022-40150 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-40150](https://nvd.nist.gov/vuln/detail/CVE-2022-40150) |
| CVE-2022-40150 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-40150](https://nvd.nist.gov/vuln/detail/CVE-2022-40150) |
| CVE-2022-40150 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-40150](https://nvd.nist.gov/vuln/detail/CVE-2022-40150) |
| CVE-2022-40152 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-40152](https://nvd.nist.gov/vuln/detail/CVE-2022-40152) |
| CVE-2022-42003 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42003](https://nvd.nist.gov/vuln/detail/CVE-2022-42003) |
| CVE-2022-42003 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42003](https://nvd.nist.gov/vuln/detail/CVE-2022-42003) |
| CVE-2022-42003 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42003](https://nvd.nist.gov/vuln/detail/CVE-2022-42003) |
| CVE-2022-42003 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42003](https://nvd.nist.gov/vuln/detail/CVE-2022-42003) |
| CVE-2022-42004 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42004](https://nvd.nist.gov/vuln/detail/CVE-2022-42004) |
| CVE-2022-42004 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42004](https://nvd.nist.gov/vuln/detail/CVE-2022-42004) |
| CVE-2022-42004 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42004](https://nvd.nist.gov/vuln/detail/CVE-2022-42004) |
| CVE-2022-45685 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-45685](https://nvd.nist.gov/vuln/detail/CVE-2022-45685) |
| CVE-2022-45685 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-45685](https://nvd.nist.gov/vuln/detail/CVE-2022-45685) |
| CVE-2022-45685 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-45685](https://nvd.nist.gov/vuln/detail/CVE-2022-45685) |
| CVE-2022-45688 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-45688](https://nvd.nist.gov/vuln/detail/CVE-2022-45688) |
| CVE-2022-45693 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-45693](https://nvd.nist.gov/vuln/detail/CVE-2022-45693) |
| CVE-2022-45693 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-45693](https://nvd.nist.gov/vuln/detail/CVE-2022-45693) |
| CVE-2022-45693 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-45693](https://nvd.nist.gov/vuln/detail/CVE-2022-45693) |
| CVE-2022-46751 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-46751](https://nvd.nist.gov/vuln/detail/CVE-2022-46751) |
| CVE-2023-1370 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-1370](https://nvd.nist.gov/vuln/detail/CVE-2023-1370) |
| CVE-2023-1370 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-1370](https://nvd.nist.gov/vuln/detail/CVE-2023-1370) |
| CVE-2023-1436 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-1436](https://nvd.nist.gov/vuln/detail/CVE-2023-1436) |
| CVE-2023-1436 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-1436](https://nvd.nist.gov/vuln/detail/CVE-2023-1436) |
| CVE-2023-1436 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-1436](https://nvd.nist.gov/vuln/detail/CVE-2023-1436) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-34453 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-34453](https://nvd.nist.gov/vuln/detail/CVE-2023-34453) |
| CVE-2023-34454 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-34454](https://nvd.nist.gov/vuln/detail/CVE-2023-34454) |
| CVE-2023-34455 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-34455](https://nvd.nist.gov/vuln/detail/CVE-2023-34455) |
| CVE-2023-3635 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-3635](https://nvd.nist.gov/vuln/detail/CVE-2023-3635) |
| CVE-2023-36478 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-36478](https://nvd.nist.gov/vuln/detail/CVE-2023-36478) |
| CVE-2023-36478 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-36478](https://nvd.nist.gov/vuln/detail/CVE-2023-36478) |
| CVE-2023-39410 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-39410](https://nvd.nist.gov/vuln/detail/CVE-2023-39410) |
| CVE-2023-39410 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-39410](https://nvd.nist.gov/vuln/detail/CVE-2023-39410) |
| CVE-2023-43642 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-43642](https://nvd.nist.gov/vuln/detail/CVE-2023-43642) |
| CVE-2023-43642 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-43642](https://nvd.nist.gov/vuln/detail/CVE-2023-43642) |
| CVE-2023-50387 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-50387](https://nvd.nist.gov/vuln/detail/CVE-2023-50387) |
| CVE-2023-5072 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-5072](https://nvd.nist.gov/vuln/detail/CVE-2023-5072) |
| CVE-2023-6378 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-6378](https://nvd.nist.gov/vuln/detail/CVE-2023-6378) |
| CVE-2023-6378 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-6378](https://nvd.nist.gov/vuln/detail/CVE-2023-6378) |
| CVE-2023-6481 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-6481](https://nvd.nist.gov/vuln/detail/CVE-2023-6481) |
| CVE-2023-6481 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-6481](https://nvd.nist.gov/vuln/detail/CVE-2023-6481) |
| CVE-2024-21634 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-21634](https://nvd.nist.gov/vuln/detail/CVE-2024-21634) |
## 7.3.0 릴리스 정보
다음 릴리스 정보에는 Amazon EMR 릴리스 7.3.0에 대한 정보가 포함됩니다. 변경 사항은 7.3.0에 관련됩니다.
**새로운 기능**
+ **애플리케이션 업그레이드** – Amazon EMR 7.3.0 application upgrades include Delta 3.2.0-amzn-0, Hudi 0.15.0-amzn-0, TensorFlow 2.16.1, Trino 442, and Zeppelin 0.11.1.
+ 이 릴리스에는 네트워크를 통한 전송 중 데이터 암호화를 지원하는 22개의 오픈 소스 엔드포인트가 추가되었습니다. 이 개선 사항에는 Hadoop, Hive, Tez, HBase, Phoenix 및 Flink와 같은 오픈 소스 프레임워크가 포함됩니다. 전송 중 데이터 암호화를 활성화하고 이러한 엔드포인트에 연결하려는 경우 TLS 통신을 지원하도록 코드를 수정해야 할 수 있습니다. 필요한 경우 이러한 엔드포인트에 대한 TLS를 비활성화할 수 있습니다. 지원되는 엔드포인트의 전체 목록은 [전송 중 암호화 이해](https://docs.aws.amazon.com/emr/latest/ManagementGuide/emr-encryption-support-matrix.html)를 참조하세요.
+ Amazon EMR 7.3.0을 사용하면 Iceberg를 사용하는 Apache Hive가 이제 AWS Glue 데이터 카탈로그를 메타스토어로 지원하므로 메타데이터를 저장하고, 데이터 소스를 자동으로 크롤링하고, 메타데이터를 추출하고, 원활한 워크플로를 위해 다른 서비스와 통합하는 중앙 집중식 리포지토리와 같은 이점을 누릴 수 있습니다.
**알려진 문제**
+ Python 3.11은 EMR Studio에서 지원되지 않습니다.
+ 전송 중 암호화 및 Kerberos 인증을 사용하는 경우 Hive 메타스토어에 의존하는 Spark 애플리케이션을 사용할 수 없습니다. 이 문제는 [HIVE-16340](https://issues.apache.org/jira/browse/HIVE-16340)에서 수정되었으며, 오픈 소스 Spark를 Hive 3으로 업그레이드할 수 있는 경우 [SPARK-44114](https://issues.apache.org/jira/browse/SPARK-44114)에서 완전히 해결됩니다. 그동안 `hive.metastore.use.SSL`을 `false`로 설정하여 이 문제를 일시적으로 해결할 수 있습니다. 자세한 내용은 [애플리케이션 구성](https://docs.aws.amazon.com/emr/latest/ReleaseGuide/emr-configure-apps.html)을 참조하세요.
+ Kerberos 인증을 사용하지 않는 경우 SSL을 사용하도록 Spark를 구성해야 합니다. 이를 수행하려면 클러스터를 프로비저닝할 때 다음 구성을 설정합니다.
```
[{
"Classification": "spark-defaults",
"Properties": {
"spark.hadoop.hive.metastore.truststore.path": "/usr/share/aws/emr/security/conf/keystore-thrift.jks",
"spark.hadoop.hive.metastore.use.SSL": "true"
}
}]
```
+ 사용자 지정 도메인을 사용하는 경우 AWS 콘솔의 Spark 기록 서버 UI에 있는 일부 링크가 작동하지 않을 수 있습니다. 다음 스크립트를 S3 버킷에 업로드한 다음, 쉘 스크립트를 사용하도록 [단계를 추가](https://docs.aws.amazon.com/emr/latest/ManagementGuide/emr-add-steps-console.html)합니다.
```
#!/bin/bash
if grep -q ":8042" /etc/nginx/nginx.conf; then
sudo sed -i '=s#\^(\\/nm\\/(?.*:8042)\\/(?.*)\$)#^(\\/nm\\/(?(\\.|-|[a-zA-Z0-9])*:8042)\\/(?(node|conf|logs|stacks|jmx).*)\$)#g' /etc/nginx/nginx.conf
else
sudo sed -i 's#\^(\\/nm\\/(?.*:8044)\\/(?.*)\$)#^(\\/nm\\/(?(\\.|-|[a-zA-Z0-9])*:8044)\\/(?(node|conf|logs|stacks|jmx).*)\$)#g' /etc/nginx/nginx.conf
fi
sudo systemctl restart nginx
```
+ **Glue 카탈로그를 사용하여 HBase 테이블을 Hive에 생성** - EMR-7.3.0에서 EMR-7.10.0으로의 Hive Iceberg 통합으로 인해 버그가 발생하여 Glue Data Catalog를 메타스토어로 사용할 때 Hive에서 HBase 테이블 생성이 실패합니다. 이 문제가 발생하면 AWS 지원 팀에 문의하십시오.
+ **Tez UI** - EMR-7.3에서 EMR-7.10까지, 전송 중 암호화가 활성화된 경우 YARN Resource Manager Web UI를 통해 Tez UI에 액세스하지 못하는 버그가 있습니다. 이 문제는 Tez UI에 HTTPS가 필요한 동안 YARN 프록시가 HTTP 프로토콜을 사용하려고 시도하기 때문에 발생합니다. 이 문제를 해결하려면 `tez-site`의 `tez.tez-ui.history-url.base` 구성을 `http`에서 `https`로 수정하세요.
**변경 사항, 향상된 기능 및 해결된 문제**
+ Spark 3.3.1(EMR 버전 6.10 이상에서 지원됨)부터 폐기 호스트의 모든 실행기는 *DECOMMISSIONING* 상태라는 새로운 `ExecutorState` 상태로 설정됩니다. Yarn은 폐기 중인 실행기를 사용하여 작업을 할당할 수 없으므로 필요한 경우 실행 중인 작업에 대해 새 실행기를 요청하세요. 따라서 EMR Managed Scaling, EMR Auto Scaling 또는 EMR-EC2 클러스터의 사용자 지정 조정 메커니즘을 사용하는 동안 Spark DRA를 비활성화하면 Yarn이 각 작업에 허용되는 최대 실행기를 요청할 수 있습니다. 이 문제를 방지하려면 위의 기능 조합을 사용할 때 `spark.dynamicAllocation.enabled` 속성을 `TRUE`(기본값)로 설정한 상태로 둡니다. 또한 Spark 작업의 `spark.dynamicAllocation.maxExecutors` 및 `spark.dynamicAllocation.minExecutors` 속성 값을 설정하여 작업 실행 중에 할당된 실행기 수를 제한하여 최소 및 최대 실행기 제약 조건을 설정할 수도 있습니다.
+ YARN에 대한 TLS 호스트 이름 확인을 지원하기 위해 이 릴리스에서는 `yarn.resourcemanager.hostname` 구성을 기본 인스턴스 IP 주소에서 기본 인스턴스 프라이빗 DNS 이름으로 변경합니다.
+ [MXNet 프로젝트](https://github.com/apache/mxnet)는 수명이 다하여 이제 아카이브됩니다. [Amazon EMR 릴리스 7.2.0](emr-720-release.md)는 MXNet이 포함된 마지막 릴리스입니다.
+ Amazon EMR 5.36 이상, 6.6 이상 또는 7.0 이상의 *최신 패치 릴리스*가 적용된 클러스터를 시작하는 경우 Amazon EMR은 기본 Amazon EMR AMI에 대한 최신 Amazon Linux 2023 or Amazon Linux 2 릴리스를 사용합니다. 자세한 내용은 [Amazon EMR에 대한 기본 Amazon Linux AMI 사용](https://docs.aws.amazon.com/emr/latest/ManagementGuide/emr-default-ami.html)을 참조하세요.
[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/ko_kr/emr/latest/ReleaseGuide/emr-730-release.html)
## 7.3.0 기본 Java 버전
Amazon EMR 릴리스 7.3 이상에서는 Apache Livy를 제외한 Corretto 17(JDK 17)을 지원하는 애플리케이션에 대해 기본적으로 Amazon Corretto 17(OpenJDK 기반)이 함께 제공됩니다.
다음 표에서는 Amazon EMR 7.3.0에 있는 애플리케이션의 기본 Java 버전을 확인할 수 있습니다. 클러스터의 기본 JVM을 변경하려면 클러스터에서 실행되는 각 애플리케이션에 대해 [특정 Java 가상 머신을 사용하도록 애플리케이션 구성](configuring-java8.md)의 지침을 따릅니다. 클러스터에서는 Java 런타임 버전 1개만 사용할 수 있습니다. Amazon EMR은 동일한 클러스터에서 다양한 런타임 버전을 사용해 서로 다른 노드 또는 애플리케이션을 실행하는 것을 지원하지 않습니다.
| 애플리케이션 | Java 및 Amazon Corretto 버전(기본값은 굵은체로 표시) |
| --- | --- |
| 델타 | 17, 11, 8 |
| Flink | 17, 11, 8 |
| HBase | 17, 11, 8 |
| HCatalog | 17, 11, 8 |
| Hadoop | 17, 11, 8 |
| Hive | 17, 11, 8 |
| Hudi | 17, 11, 8 |
| Iceberg | 17, 11, 8 |
| Livy | 17, 11, 8 |
| Oozie | 17, 11, 8 |
| 피닉스 | 17, 11, 8 |
| PrestoDB | 8 |
| Spark | 17, 11, 8 |
| Spark RAPIDS | 17, 11, 8 |
| Sqoop | 8 |
| Tez의 Hive 실행 시간 비교 | 17, 11, 8 |
| Trino | 21, 17 |
| Zeppelin | 8 |
| Pig | 8 |
| Zookeeper | 17, 11, 8 |
## 7.3.0 구성 요소 버전
이 릴리스를 통해 Amazon EMR이 설치하는 구성 요소는 다음과 같습니다. 일부는 빅 데이터 애플리케이션 패키지의 일부로 설치됩니다. 나머지는 Amazon EMR에 고유하며 시스템 프로세스 및 기능을 위해 설치됩니다. 이는 일반적으로 `emr` 또는 `aws`로 시작됩니다. 최근 Amazon EMR 릴리스의 빅 데이터 애플리케이션 패키지는 일반적으로 커뮤니티에서 발견된 최신 버전입니다. 가능한 한 빨리 Amazon EMR에서 커뮤니티 릴리스를 제공합니다.
Amazon EMR의 일부 구성 요소는 커뮤니티 버전과 다릅니다. 이러한 구성 요소에는 `CommunityVersion-amzn-EmrVersion` 양식의 버전 레이블이 있습니다. `EmrVersion`은 0에서 시작합니다. 예를 들어, 버전 2.2의 `myapp-component`라는 오픈 소스 커뮤니티 구성 요소가 다른 Amazon EMR 릴리스에 포함되도록 세 번 수정된 경우 해당 릴리스 버전은 `2.2-amzn-2`로 나열됩니다.
| 구성 요소 | 버전 | 설명 |
| --- | --- | --- |
| adot-java-agent | 1.31.0 | 애플리케이션 대몬(daemon)에서 지표를 수집하는 Java 에이전트입니다. |
| delta | 3.2.0-amzn-0 | Delta Lake는 방대한 분석 데이터 세트를 위한 오픈 테이블 형식입니다. |
| emr-amazon-cloudwatch-agent | 1.300032.2-amzn-0 | Amazon EC2 인스턴스에서 내부 시스템 수준 지표와 사용자 지정 애플리케이션 지표를 수집하는 애플리케이션입니다. |
| emr-ddb | 5.5.0 | 하둡 에코시스템 애플리케이션용 Amazon DynamoDB 커넥터 |
| emr-goodies | 3.12.0 | 편리한 하둡 에코시스템용 추가 라이브러리 |
| emr-kinesis | 3.16.0 | 하둡 에코시스템 애플리케이션용 Amazon Kinesis 커넥터. |
| emr-notebook-env | 1.16.0 | Jupyter Enterprise Gateway가 포함된 EMR 노트북용 Conda 환경 |
| emr-s3-dist-cp | 2.33.0 | Amazon S3용으로 최적화된 분사 복사 애플리케이션. |
| emr-s3-select | 2.12.0 | EMR S3Select 커넥터 |
| emr-wal-cli | 1.3.0 | emrwal 목록/삭제에 사용되는 CLI입니다. |
| emrfs | 2.64.0 | 하둡 에코시스템 애플리케이션용 Amazon S3 커넥터. |
| flink-client | 1.18.1-amzn-2 | Apache Flink 명령줄 클라이언트 스크립트 및 애플리케이션 |
| flink-jobmanager-config | 1.18.1-amzn-2 | Apache Flink JobManager에 대한 EMR 노드에서 리소스를 관리합니다. |
| hadoop-client | 3.3.6-amzn-5 | 'hdfs', 'hadoop', 'yarn' 등과 같은 하둡 명령줄 클라이언트 |
| hadoop-hdfs-datanode | 3.3.6-amzn-5 | 블록을 저장하는 HDFS 노드 수준 서비스 |
| hadoop-hdfs-library | 3.3.6-amzn-5 | HDFS 명령줄 클라이언트 및 라이브러리 |
| hadoop-hdfs-namenode | 3.3.6-amzn-5 | 파일 이름 및 블록 위치를 추적하는 HDFS 서비스 |
| hadoop-hdfs-journalnode | 3.3.6-amzn-5 | HA 클러스터에서 하둡 파일 시스템 저널을 관리하기 위한 HDFS 서비스 |
| hadoop-httpfs-server | 3.3.6-amzn-5 | HDFS 작업에 대한 HTTP 엔드포인트 |
| hadoop-kms-server | 3.3.6-amzn-5 | 하둡의 KeyProvider API를 기반으로 하는 암호화 키 관리 서버 |
| hadoop-mapred | 3.3.6-amzn-5 | MapReduce 애플리케이션을 실행하는 MapReduce 실행 엔진 라이브러리 |
| hadoop-yarn-nodemanager | 3.3.6-amzn-5 | 개별 노드의 컨테이너를 관리하는 YARN 서비스 |
| hadoop-yarn-resourcemanager | 3.3.6-amzn-5 | 클러스터 리소스 및 분산 애플리케이션을 할당 및 관리하는 YARN 서비스 |
| hadoop-yarn-timeline-server | 3.3.6-amzn-5 | YARN 애플리케이션의 현재 및 기록 정보를 가져오는 서비스 |
| hbase-hmaster | 2.4.17-amzn-7 | 리전 조정 및 관리 명령의 실행을 담당하는 HBase 클러스터용 서비스 |
| hbase-region-server | 2.4.17-amzn-7 | 한 개 이상의 HBase 리전에 서비스를 제공하는 서비스 |
| hbase-client | 2.4.17-amzn-7 | HBase 명령줄 클라이언트 |
| hbase-rest-server | 2.4.17-amzn-7 | HBase용 RESTful HTTP 엔드포인트를 제공하는 서비스 |
| hbase-thrift-server | 2.4.17-amzn-7 | HBase에 Thrift 엔드포인트를 제공하는 서비스 |
| hbase-operator-tools | 2.4.17-amzn-7 | Apache HBase 클러스터용 복구 도구. |
| hcatalog-client | 3.1.3-amzn-12 | hcatalog-server를 조정하기 위한 'hcat' 명령줄 클라이언트 |
| hcatalog-server | 3.1.3-amzn-12 | 분산 애플리케이션용 스토리지 관리 계층, 테이블 및 HCatalog를 제공하는 서비스 |
| hcatalog-webhcat-server | 3.1.3-amzn-12 | HCatalog에 REST 인터페이스를 제공하는 HTTP 엔드포인트 |
| hive-client | 3.1.3-amzn-12 | Hive 명령줄 클라이언트 |
| hive-hbase | 3.1.3-amzn-12 | Hive-hbase 클라이언트 |
| hive-metastore-server | 3.1.3-amzn-12 | 하둡 작업에 대한 SQL용 메타데이터가 저장되는 시맨틱 리포지토리인 Hive 메타스토어에 액세스하기 위한 서비스 |
| hive-server2 | 3.1.3-amzn-12 | Hive 쿼리를 웹 요청으로 수락하기 위한 서비스 |
| hudi | 0.15.0-amzn-0 | 짧은 지연 시간 및 높은 효율성으로 데이터 파이프라인을 구동하는 증분 처리 프레임워크. |
| hudi-presto | 0.15.0-amzn-0 | Hudi로 Presto를 실행하기 위한 번들 라이브러리. |
| hudi-trino | 0.15.0-amzn-0 | Hudi와 함께 Trnio를 실행하기 위한 번들 라이브러리. |
| hudi-spark | 0.15.0-amzn-0 | Hudi와 함께 Spark를 실행하기 위한 번들 라이브러리. |
| hue-server | 4.11.0 | 하둡 에코시스템 애플리케이션을 사용하여 데이터를 분석하는 웹 애플리케이션. |
| iceberg | 1.5.2-amzn-0 | Apache Iceberg는 방대한 분석 데이터 세트를 위한 오픈 테이블 형식입니다. |
| jupyterhub | 1.5.0 | Jupyter Notebook용 다중 사용자 서버 |
| livy-server | 0.8.0-incubating | Apache Spark와 상호작용하기 위한 REST 인터페이스 |
| nginx | 1.12.1 | HTTP인 nginx [engine x] 및 역방향 프록시 서버 |
| mariadb-server | 5.5.68 이상 | MariaDB 데이터베이스 서버. |
| nvidia-cuda | 12.3.0 | Nvidia 드라이버와 Cuda 도구 키트 |
| oozie-client | 5.2.1 | Oozie 명령줄 클라이언트 |
| oozie-server | 5.2.1 | Oozie 워크플로 요청을 수락하는 서비스 |
| opencv | 4.7.0 | 오픈 소스 컴퓨터 비전 라이브러리. |
| phoenix-library | 5.1.3 | 서버 및 클라이언트의 phoenix 라이브러리 |
| phoenix-connectors | 6.0.0 | Spark-3용 Apache Phoenix 커넥터 |
| phoenix-query-server | 6.0.0 | Avatica API에 대한 JSON 형식 액세스 및 프로토콜 버퍼 액세스를 비롯하여 JDBC 액세스를 제공하는 경량 서버 |
| presto-coordinator | 0.285-amzn-1 | presto-worker의 쿼리를 수락하고 쿼리 실행을 관리하는 서비스. |
| presto-worker | 0.285-amzn-1 | 여러 쿼리를 실행하는 서비스. |
| presto-client | 0.285-amzn-1 | Presto 서버가 시작되지 않은 HA 클러스터의 대기 마스터에 설치된 Presto 명령줄 클라이언트. |
| trino-coordinator | 442-amzn-0 | trino-workers의 쿼리를 수락하고 쿼리 실행을 관리하는 서비스. |
| trino-worker | 442-amzn-0 | 여러 쿼리를 실행하는 서비스. |
| trino-client | 442-amzn-0 | Trino 서버가 시작되지 않은 HA 클러스터의 대기 마스터에 설치된 Trino 명령줄 클라이언트. |
| pig-client | 0.17.0 | Pig 명령줄 클라이언트. |
| r | 4.3.2 | 통계 컴퓨팅용 R 프로젝트 |
| ranger-kms-server | 2.0.0 | Apache Ranger 키 관리 시스템 |
| spark-client | 3.5.1-amzn-1 | Spark 명령줄 클라이언트. |
| spark-history-server | 3.5.1-amzn-1 | 완료된 Spark 애플리케이션의 수명에 대해 기록된 이벤트를 조회하는 웹 UI. |
| spark-on-yarn | 3.5.1-amzn-1 | YARN용 인 메모리 실행 엔진. |
| spark-yarn-slave | 3.5.1-amzn-1 | YARN 슬레이브에서 필요한 Apache Spark 라이브러리. |
| spark-rapids | 24.06.1-amzn-0 | GPU로 Apache Spark를 가속화하는 Nvidia Spark RAPIDS 플러그인. |
| sqoop-client | 1.4.7 | Apache Sqoop 명령줄 클라이언트. |
| tensorflow | 2.16.1 | TensorFlow는 고성능 수치 계산용 오픈 소스 소프트웨어 라이브러리입니다. |
| tez-on-yarn | 0.10.2-amzn-10 | tez YARN 애플리케이션 및 라이브러리. |
| tez-on-worker | 0.10.2-amzn-10 | 워커 노드에 대한 tez YARN 애플리케이션 및 라이브러리. |
| zeppelin-server | 0.11.1 | 대화형 데이터 분석이 가능한 웹 기반 노트북 |
| zookeeper-server | 3.9.1-amzn-1 | 구성 정보 유지 관리, 이름 지정, 분산 동기화 제공 및 그룹 서비스 제공을 위한 중앙 집중식 서비스. |
| zookeeper-client | 3.9.1-amzn-1 | ZooKeeper 명령줄 클라이언트. |
## 7.3.0 구성 분류
구성 분류를 사용하면 애플리케이션을 사용자 지정할 수 있습니다. 이는 종종 `hive-site.xml`과 같이 애플리케이션의 구성 XML 파일에 해당합니다. 자세한 내용은 [애플리케이션 구성](emr-configure-apps.md) 단원을 참조하십시오.
재구성 작업은 실행 중인 클러스터의 인스턴스 그룹에 대한 구성을 지정할 때 수행됩니다. Amazon EMR은 사용자가 수정한 분류에 대한 재구성 작업만 시작합니다. 자세한 내용은 [실행 중인 클러스터에서 인스턴스 그룹 재구성](emr-configure-apps-running-cluster.md) 단원을 참조하십시오.
**emr-7.3.0 분류**
| 분류 | 설명 | 재구성 작업 |
| --- | --- | --- |
| capacity-scheduler | Hadoop capacity-scheduler.xml 파일에서 값을 변경합니다. | Restarts the ResourceManager service. |
| container-executor | Hadoop YARN container-executor.cfg 파일에서 값을 변경합니다. | Not available. |
| container-log4j | Hadoop YARN container-log4j.properties 파일에서 값을 변경합니다. | Not available. |
| core-site | Hadoop core-site.xml 파일에서 값을 변경합니다. | Restarts the Hadoop HDFS services Namenode, SecondaryNamenode, Datanode, ZKFC, and Journalnode. Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts Hadoop KMS, Ranger KMS, HiveServer2, Hive MetaStore, Hadoop Httpfs, and MapReduce-HistoryServer. |
| docker-conf | Docker 관련 설정을 변경합니다. | Not available. |
| emrfs-site | EMRFS 설정을 변경합니다. | Restarts the Hadoop HDFS services Namenode, SecondaryNamenode, Datanode, ZKFC, and Journalnode. Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts HBaseRegionserver, HBaseMaster, HBaseThrift, HBaseRest, HiveServer2, Hive MetaStore, Hadoop Httpfs, and MapReduce-HistoryServer. |
| flink-conf | flink-conf.yaml 설정을 변경합니다. | Restarts Flink history server. |
| flink-log4j | Flink log4j.properties 설정을 변경합니다. | Restarts Flink history server. |
| flink-log4j-session | Kubernetes 및 Yarn 세션에 대한 Flink log4j-session.properties 설정을 변경합니다. | Restarts Flink history server. |
| flink-log4j-cli | Flink log4j-cli.properties 설정을 변경합니다. | Restarts Flink history server. |
| hadoop-env | 모든 Hadoop 구성 요소에 대한 Hadoop 환경에서 값을 변경합니다. | Restarts the Hadoop HDFS services Namenode, SecondaryNamenode, Datanode, ZKFC, and Journalnode. Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts PhoenixQueryserver, HiveServer2, Hive MetaStore, and MapReduce-HistoryServer. |
| hadoop-log4j | Hadoop log4j.properties 파일에서 값을 변경합니다. | Restarts the Hadoop HDFS services SecondaryNamenode, Datanode, and Journalnode. Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts Hadoop KMS, Hadoop Httpfs, and MapReduce-HistoryServer. |
| hadoop-ssl-server | hadoop ssl 서버 구성을 변경합니다. | Not available. |
| hadoop-ssl-client | hadoop ssl 클라이언트 구성을 변경합니다. | Not available. |
| hbase | Apache HBase에 대한 Amazon EMR 큐레이트 설정입니다. | Custom EMR specific property. Sets emrfs-site and hbase-site configs. See those for their associated restarts. |
| hbase-env | HBase 환경에서 값을 변경합니다. | Restarts the HBase services RegionServer, HBaseMaster, ThriftServer, RestServer. |
| hbase-log4j | HBase hbase-log4j.properties 파일에서 값을 변경합니다. | Restarts the HBase services RegionServer, HBaseMaster, ThriftServer, RestServer. |
| hbase-metrics | HBase hadoop-metrics2-hbase.properties 파일에서 값을 변경합니다. | Restarts the HBase services RegionServer, HBaseMaster, ThriftServer, RestServer. |
| hbase-policy | HBase hbase-policy.xml 파일에서 값을 변경합니다. | Not available. |
| hbase-site | HBase hbase-site.xml 파일에서 값을 변경합니다. | Restarts the HBase services RegionServer, HBaseMaster, ThriftServer, RestServer. Additionally restarts Phoenix QueryServer. |
| hdfs-encryption-zones | HDFS 암호화 영역을 구성합니다. | This classification should not be reconfigured. |
| hdfs-env | HDFS 환경에서 값을 변경합니다. | Restarts Hadoop HDFS services Namenode, Datanode, and ZKFC. |
| hdfs-site | HDFS hdfs-site.xml에서 값을 변경합니다. | Restarts the Hadoop HDFS services Namenode, SecondaryNamenode, Datanode, ZKFC, and Journalnode. Additionally restarts Hadoop Httpfs. |
| hcatalog-env | HCatalog 환경에서 값을 변경합니다. | Restarts Hive HCatalog Server. |
| hcatalog-server-jndi | HCatalog jndi.properties 환경에서 값을 변경합니다. | Restarts Hive HCatalog Server. |
| hcatalog-server-proto-hive-site | HCatalog proto-hive-site.xml에서 값을 변경합니다. | Restarts Hive HCatalog Server. |
| hcatalog-webhcat-env | HCatalog WebHCat 환경에서 값을 변경합니다. | Restarts Hive WebHCat server. |
| hcatalog-webhcat-log4j2 | HCatalog WebHCat log4j2.properties에서 값을 변경합니다. | Restarts Hive WebHCat server. |
| hcatalog-webhcat-site | HCatalog WebHCat webhcat-site.xml 파일에서 값을 변경합니다. | Restarts Hive WebHCat server. |
| hive | Apache Hive에 대한 Amazon EMR 큐레이트 설정입니다. | Sets configurations to launch Hive LLAP service. |
| hive-beeline-log4j2 | Hive beeline-log4j2.properties 파일에서 값을 변경합니다. | Not available. |
| hive-parquet-logging | Hive parquet-logging.properties 파일에서 값을 변경합니다. | Not available. |
| hive-env | Hive 환경에서 값을 변경합니다. | Restarts HiveServer2, HiveMetastore, and Hive HCatalog-Server. Runs Hive schemaTool CLI commands to verify hive-metastore. |
| hive-exec-log4j2 | Hive hive-exec-log4j2.properties 파일에서 값을 변경합니다. | Not available. |
| hive-llap-daemon-log4j2 | Hive llap-daemon-log4j2.properties 파일에서 값을 변경합니다. | Not available. |
| hive-log4j2 | Hive hive-log4j2.properties 파일에서 값을 변경합니다. | Not available. |
| hive-site | Hive hive-site.xml 파일에서 값을 변경합니다. | Restarts HiveServer2, HiveMetastore, and Hive HCatalog-Server. Runs Hive schemaTool CLI commands to verify hive-metastore. Also restarts Oozie and Zeppelin. |
| hiveserver2-site | Hive Server2 hiveserver2-site.xml 파일에서 값을 변경합니다. | Not available. |
| hue-ini | Hue ini 파일에서 값을 변경합니다. | Restarts Hue. Also activates Hue config override CLI commands to pick up new configurations. |
| httpfs-env | HTTPFS 환경에서 값을 변경합니다. | Restarts Hadoop Httpfs service. |
| httpfs-site | Hadoop httpfs-site.xml 파일에서 값을 변경합니다. | Restarts Hadoop Httpfs service. |
| hadoop-kms-acls | Hadoop kms-acls.xml 파일에서 값을 변경합니다. | Not available. |
| hadoop-kms-env | Hadoop KMS 환경에서 값을 변경합니다. | Restarts Hadoop-KMS service. |
| hadoop-kms-java-home | Hadoop의 KMS java 홈 변경 | Not available. |
| hadoop-kms-log4j | Hadoop kms-log4j.properties 파일에서 값을 변경합니다. | Not available. |
| hadoop-kms-site | Hadoop kms-site.xml 파일에서 값을 변경합니다. | Restarts Hadoop-KMS and Ranger-KMS service. |
| hudi-env | Hudi 환경에서 값을 변경합니다. | Not available. |
| hudi-defaults | Hudi hudi-defaults.conf 파일에서 값을 변경합니다. | Not available. |
| iceberg-defaults | Iceberg iceberg-defaults.conf 파일에서 값을 변경합니다. | Not available. |
| delta-defaults | Delta delta-defaults.conf 파일에서 값을 변경합니다. | Not available. |
| jupyter-notebook-conf | Jupyter Notebook jupyter\$1notebook\$1config.py 파일에서 값을 변경합니다. | Not available. |
| jupyter-hub-conf | JupyterHubs jupyterhub\$1config.py 파일에서 값을 변경합니다. | Not available. |
| jupyter-s3-conf | Jupyter Notebook S3 지속성 구성 | Not available. |
| jupyter-sparkmagic-conf | Sparkmagic config.json 파일에서 값을 변경합니다. | Not available. |
| livy-conf | Livy livy.conf 파일에서 값을 변경합니다. | Restarts Livy Server. |
| livy-env | Livy 환경에서 값을 변경합니다. | Restarts Livy Server. |
| livy-log4j2 | Livy log4j2.properties 설정을 변경합니다. | Restarts Livy Server. |
| mapred-env | MapReduce 애플리케이션 환경에서 값을 변경합니다. | Restarts Hadoop MapReduce-HistoryServer. |
| mapred-site | MapReduce 애플리케이션 mapred-site.xml 파일에서 값을 변경합니다. | Restarts Hadoop MapReduce-HistoryServer. |
| oozie-env | Oozie 환경에서 값을 변경합니다. | Restarts Oozie. |
| oozie-log4j | Oozie oozie-log4j.properties 파일에서 값을 변경합니다. | Restarts Oozie. |
| oozie-site | Oozie oozie-site.xml 파일에서 값을 변경합니다. | Restarts Oozie. |
| phoenix-hbase-metrics | Phoenix hadoop-metrics2-hbase.properties 파일에서 값을 변경합니다. | Not available. |
| phoenix-hbase-site | Phoenix hbase-site.xml 파일에서 값을 변경합니다. | Not available. |
| phoenix-log4j | Phoenix log4j.properties 파일에서 값을 변경합니다. | Restarts Phoenix-QueryServer. |
| phoenix-metrics | Phoenix hadoop-metrics2-phoenix.properties 파일에서 값을 변경합니다. | Not available. |
| pig-env | Pig 환경에서 값을 변경합니다. | Not available. |
| pig-properties | Pig pig.properties 파일에서 값을 변경합니다. | Restarts Oozie. |
| pig-log4j | Pig log4j.properties 파일에서 값을 변경합니다. | Not available. |
| presto-log | Presto log.properties 파일에서 값을 변경합니다. | Restarts Presto-Server (for PrestoDB) |
| presto-config | Presto config.properties 파일에서 값을 변경합니다. | Restarts Presto-Server (for PrestoDB) |
| presto-password-authenticator | Presto password-authenticator.properties 파일에서 값을 변경합니다. | Not available. |
| presto-env | Presto presto-env.sh 파일에서 값을 변경합니다. | Restarts Presto-Server (for PrestoDB) |
| presto-node | Presto node.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-blackhole | Presto blackhole.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-cassandra | Presto cassandra.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-hive | Presto hive.properties 파일에서 값을 변경합니다. | Restarts Presto-Server (for PrestoDB) |
| presto-connector-jmx | Presto jmx.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-kafka | Presto kafka.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-lakeformation | Presto lakeformation.properties 파일에서 값을 변경합니다. | Restarts Presto-Server (for PrestoDB) |
| presto-connector-localfile | Presto localfile.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-memory | Presto memory.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-mongodb | Presto mongodb.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-mysql | Presto mysql.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-postgresql | Presto postgresql.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-raptor | Presto raptor.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-redis | Presto redis.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-redshift | Presto redshift.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-tpch | Presto tpch.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-tpcds | Presto tpcds.properties 파일에서 값을 변경합니다. | Not available. |
| trino-log | Trino log.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-config | Trino config.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-password-authenticator | Trino password-authenticator.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-env | Trino trino-env.sh 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-node | Trino node.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-blackhole | Trino blackhole.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-cassandra | Trino cassandra.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-delta | Trino delta.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-connector-hive | Trino hive.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-exchange-manager | Trino exchange-manager.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-connector-iceberg | Trino iceberg.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-connector-hudi | Trino hudi.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-connector-jmx | Trino jmx.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-kafka | Trino kafka.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-localfile | Trino localfile.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-memory | Trino memory.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-mongodb | Trino mongodb.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-mysql | Trino mysql.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-postgresql | Trino postgresql.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-raptor | Trino raptor.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-redis | Trino redis.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-redshift | Trino redshift.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-tpch | Trino tpch.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-tpcds | Trino tpcds.properties 파일에서 값을 변경합니다. | Not available. |
| ranger-kms-dbks-site | Ranger KMS dbks-site.xml 파일에서 값을 변경합니다. | Restarts Ranger KMS Server. |
| ranger-kms-site | Ranger KMS ranger-kms-site.xml 파일에서 값을 변경합니다. | Restarts Ranger KMS Server. |
| ranger-kms-env | Ranger KMS 환경에서 값을 변경합니다. | Restarts Ranger KMS Server. |
| ranger-kms-logback | Ranger KMS kms-logback.xml 파일에서 값을 변경합니다. | Not available. |
| ranger-kms-db-ca | Ranger KMS와의 MySQL SSL 연결에서 CA 파일의 값을 변경합니다. | Not available. |
| spark | Apache Spark에 대한 Amazon EMR 큐레이트 설정입니다. | This property modifies spark-defaults. See actions there. |
| spark-defaults | Spark spark-defaults.conf 파일에서 값을 변경합니다. | Restarts Spark history server and Spark thrift server. |
| spark-env | Spark 환경에서 값을 변경합니다. | Restarts Spark history server and Spark thrift server. |
| spark-hive-site | Spark hive-site.xml 파일에서 값을 변경합니다. | Not available. |
| spark-log4j2 | Spark log4j2.properties 파일에서 값을 변경합니다. | Restarts Spark history server and Spark thrift server. |
| spark-metrics | Spark metrics.properties 파일에서 값을 변경합니다. | Restarts Spark history server and Spark thrift server. |
| sqoop-env | Sqoop 환경에서 값을 변경합니다. | Not available. |
| sqoop-oraoop-site | Sqoop OraOop oraoop-site.xml 파일에서 값을 변경합니다. | Not available. |
| sqoop-site | Sqoop sqoop-site.xml 파일에서 값을 변경합니다. | Not available. |
| tez-site | Tez tez-site.xml 파일에서 값을 변경합니다. | Restart Oozie and HiveServer2. |
| yarn-env | YARN 환경에서 값을 변경합니다. | Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts MapReduce-HistoryServer. |
| yarn-site | YARN yarn-site.xml 파일에서 값을 변경합니다. | Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts Livy Server and MapReduce-HistoryServer. |
| zeppelin-env | Zeppelin 환경에서 값을 변경합니다. | Restarts Zeppelin. |
| zeppelin-site | zeppelin-site.xml에서 구성 설정을 변경합니다. | Restarts Zeppelin. |
| zookeeper-config | ZooKeeper zoo.cfg 파일에서 값을 변경합니다. | Restarts Zookeeper server. |
| zookeeper-logback | ZooKeeper logback.xml 파일에서 값을 변경합니다. | Restarts Zookeeper server. |
| emr-metrics | 이 노드에 대한 emr 지표 설정을 변경합니다. | Restarts the CloudWatchAgent service. |
## 7.3.0 변경 로그
**7.3.0 릴리스 및 릴리스 정보에 대한 변경 로그**
| Date | 이벤트 | 설명 |
| --- | --- | --- |
| 2024-10-17 | 문서 게시 | Amazon EMR 7.3.0 릴리스 정보 최초 게시됨 |
| 2024-10-16 | 배포 완료 | 모든 [지원되는 리전](https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/)에 Amazon EMR 7.3.0 전체 배포됨 |
| 2024-10-14 | 초기 릴리스 | 최초 상용 리전에 Amazon EMR 7.3.0 최초 배포됨 |
# Amazon EMR 릴리스 7.2.0
## 7.2.0 지원 수명 주기
다음 표에서는 Amazon EMR 릴리스 7.2.0에 대해 지원되는 수명 주기 날짜를 설명합니다.
| 지원 단계 | Date |
| --- | --- |
| 초기 릴리스 날짜 | 2024년 7월 25일 |
| 표준 지원 종료 시점 | 2026년 7월 24일 |
| 지원 종료 | 2026년 7월 25일 |
| 수명 종료 | 2027년 7월 25일 |
## 7.2.0 애플리케이션 버전
이 릴리스에서 지원되는 애플리케이션은 [https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Install-CloudWatch-Agent.html](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Install-CloudWatch-Agent.html), [https://delta.io/](https://delta.io/), [https://flink.apache.org/](https://flink.apache.org/), [http://hbase.apache.org/](http://hbase.apache.org/), [https://cwiki.apache.org/confluence/display/Hive/HCatalog](https://cwiki.apache.org/confluence/display/Hive/HCatalog), [http://hadoop.apache.org/docs/current/](http://hadoop.apache.org/docs/current/), [http://hive.apache.org/](http://hive.apache.org/), [https://hudi.apache.org](https://hudi.apache.org), [http://gethue.com/](http://gethue.com/), [https://iceberg.apache.org/](https://iceberg.apache.org/), [https://jupyter-enterprise-gateway.readthedocs.io/en/latest/](https://jupyter-enterprise-gateway.readthedocs.io/en/latest/), [https://jupyterhub.readthedocs.io/en/latest/#](https://jupyterhub.readthedocs.io/en/latest/#), [https://livy.incubator.apache.org/](https://livy.incubator.apache.org/), [https://mxnet.incubator.apache.org/](https://mxnet.incubator.apache.org/), [http://oozie.apache.org/](http://oozie.apache.org/), [https://phoenix.apache.org/](https://phoenix.apache.org/), [http://pig.apache.org/](http://pig.apache.org/), [https://prestodb.io/](https://prestodb.io/), [https://spark.apache.org/docs/latest/](https://spark.apache.org/docs/latest/), [http://sqoop.apache.org/](http://sqoop.apache.org/), [https://www.tensorflow.org/](https://www.tensorflow.org/), [https://tez.apache.org/](https://tez.apache.org/), [https://trino.io/](https://trino.io/), [https://zeppelin.incubator.apache.org/](https://zeppelin.incubator.apache.org/), [https://zookeeper.apache.org](https://zookeeper.apache.org)입니다.
아래 테이블에는 이번 Amazon EMR 릴리스에서 사용할 수 있는 애플리케이션 버전과 이전 세 가지 Amazon EMR 릴리스(해당하는 경우)의 애플리케이션 버전이 나와 있습니다.
각 Amazon EMR 릴리스에서 애플리케이션 버전의 전체 기록은 다음 주제를 참조하세요.
+ [Amazon EMR 7.x 릴리스의 애플리케이션 버전](emr-release-app-versions-7.x.md)
+ [Amazon EMR 6.x 릴리스의 애플리케이션 버전](emr-release-app-versions-6.x.md)
+ [Amazon EMR 5.x 릴리스의 애플리케이션 버전](emr-release-app-versions-5.x.md)
+ [Amazon EMR 4.x 릴리스의 애플리케이션 버전](emr-release-app-versions-4.x.md)
**애플리케이션 버전 정보**
| | emr-7.3.0 | emr-7.2.0 | emr-7.1.0 | emr-7.0.0 |
| --- | --- | --- | --- | --- |
| AWS Java용 SDK | 2.25.70, 1.12.747 | 2.23.18, 1.12.705 | 2.23.18, 1.12.656 | 2.20.160-amzn-0, 1.12.569 |
| Python | 3.9, 3.11 | 3.9, 3.11 | 3.9, 3.11 | 3.9 |
| Scala | 2.12.18 | 2.12.17 | 2.12.17 | 2.12.17 |
| AmazonCloudWatchAgent | 1.300032.2-amzn-0 | 1.300032.2-amzn-0 | 1.300032.2-amzn-0 | 1.300031.1-amzn-0 |
| Delta | 3.2.0-amzn-0 | 3.1.0 | 3.0.0 | 3.0.0 |
| Flink | 1.18.1-amzn-2 | 1.18.1-amzn-1 | 1.18.1-amzn-0 | 1.18.0-amzn-0 |
| Ganglia | - | - | - | - |
| HBase | 2.4.17-amzn-7 | 2.4.17-amzn-6 | 2.4.17-amzn-5 | 2.4.17-amzn-4 |
| HCatalog | 3.1.3-amzn-12 | 3.1.3-amzn-11 | 3.1.3-amzn-10 | 3.1.3-amzn-9 |
| Hadoop | 3.3.6-amzn-5 | 3.3.6-amzn-4 | 3.3.6-amzn-3 | 3.3.6-amzn-2 |
| Hive | 3.1.3-amzn-12 | 3.1.3-amzn-11 | 3.1.3-amzn-10 | 3.1.3-amzn-9 |
| Hudi | 0.15.0-amzn-0 | 0.14.1-amzn-1 | 0.14.1-amzn-0 | 0.14.0-amzn-1 |
| Hue | 4.11.0 | 4.11.0 | 4.11.0 | 4.11.0 |
| Iceberg | 1.5.2-amzn-0 | 1.5.0-amzn-0 | 1.4.3-amzn-0 | 1.4.2-amzn-0 |
| JupyterEnterpriseGateway | 2.6.0 | 2.6.0 | 2.6.0 | 2.6.0 |
| JupyterHub | 1.5.0 | 1.5.0 | 1.5.0 | 1.5.0 |
| Livy | 0.8.0-incubating | 0.8.0-incubating | 0.8.0-incubating | 0.7.1-incubating |
| MXNet | - | 1.9.1 | 1.9.1 | 1.9.1 |
| Mahout | - | - | - | - |
| Oozie | 5.2.1 | 5.2.1 | 5.2.1 | 5.2.1 |
| Phoenix | 5.1.3 | 5.1.3 | 5.1.3 | 5.1.3 |
| Pig | 0.17.0 | 0.17.0 | 0.17.0 | 0.17.0 |
| Presto | 0.285-amzn-1 | 0.285-amzn-0 | 0.284-amzn-0 | 0.283-amzn-1 |
| Spark | 3.5.1-amzn-1 | 3.5.1-amzn-0 | 3.5.0-amzn-1 | 3.5.0-amzn-0 |
| Sqoop | 1.4.7 | 1.4.7 | 1.4.7 | 1.4.7 |
| TensorFlow | 2.16.1 | 2.11.0 | 2.11.0 | 2.11.0 |
| Tez | 0.10.2-amzn-10 | 0.10.2-amzn-9 | 0.10.2-amzn-8 | 0.10.2-amzn-7 |
| Trino (PrestoSQL) | 442-amzn-0 | 436-amzn-0 | 435-amzn-0 | 426-amzn-1 |
| Zeppelin | 0.11.1 | 0.10.1 | 0.10.1 | 0.10.1 |
| ZooKeeper | 3.9.1-amzn-1 | 3.9.1-amzn-1 | 3.9.1-amzn-0 | 3.5.10 |
# 7.2.0 릴리스 구성 요소 세부 정보
Amazon EMR 7.2.0의 *추가 항목* 패키지에 대한 자세한 내용은 다음 표를 참조하세요.
| 애플리케이션 | 애플리케이션 유형 | 패키지 | 패키지 유형 | 패키지 버전 |
| --- | --- | --- | --- | --- |
| AmazonCloudWatchAgent | Core | hadoop-hdfs-journalnode | 추가 항목 | 3.3.6.amzn.4-1.amzn2023 |
| AmazonCloudWatchAgent | Core | ranger-kms | 추가 항목 | 2.0.0-1.amzn2023 |
| AmazonCloudWatchAgent | Core | s3-dist-cp | 추가 항목 | 2.32.0-1.amzn2023 |
| AmazonCloudWatchAgent | Core | zookeeper | 추가 항목 | 3.9.1.amzn.1-1.amzn2023 |
| AmazonCloudWatchAgent | Core | zookeeper-server | 추가 항목 | 3.9.1.amzn.1-1.amzn2023 |
| Flink | Core | hadoop-client | 추가 항목 | 3.3.6.amzn.4-1.amzn2023 |
| Flink | Core | hadoop-hdfs | 추가 항목 | 3.3.6.amzn.4-1.amzn2023 |
| Flink | Core | hadoop-hdfs-datanode | 추가 항목 | 3.3.6.amzn.4-1.amzn2023 |
| Flink | Core | hadoop-hdfs-journalnode | 추가 항목 | 3.3.6.amzn.4-1.amzn2023 |
| Flink | Core | hadoop-hdfs-namenode | 추가 항목 | 3.3.6.amzn.4-1.amzn2023 |
| Flink | Core | hadoop-httpfs | 추가 항목 | 3.3.6.amzn.4-1.amzn2023 |
| Flink | Core | hadoop-kms | 추가 항목 | 3.3.6.amzn.4-1.amzn2023 |
| Flink | Core | hadoop-mapreduce | 추가 항목 | 3.3.6.amzn.4-1.amzn2023 |
| Flink | Core | hadoop-mapreduce-historyserver | 추가 항목 | 3.3.6.amzn.4-1.amzn2023 |
| Flink | Core | hadoop-yarn | 추가 항목 | 3.3.6.amzn.4-1.amzn2023 |
| Flink | Core | hadoop-yarn-nodemanager | 추가 항목 | 3.3.6.amzn.4-1.amzn2023 |
| Flink | Core | hadoop-yarn-proxyserver | 추가 항목 | 3.3.6.amzn.4-1.amzn2023 |
| Flink | Core | hadoop-yarn-resourcemanager | 추가 항목 | 3.3.6.amzn.4-1.amzn2023 |
| Flink | Core | hadoop-yarn-timelineserver | 추가 항목 | 3.3.6.amzn.4-1.amzn2023 |
| Flink | Core | hudi | 추가 항목 | 0.14.1.amzn.1-1.amzn2023 |
| Flink | Core | ranger-kms | 추가 항목 | 2.0.0-1.amzn2023 |
| Flink | Core | hadoop | 추가 항목 | 3.3.6.amzn.4-1.amzn2023 |
| HBase | Core | s3-dist-cp | 추가 항목 | 2.32.0-1.amzn2023 |
| HCatalog | Core | hadoop-yarn-proxyserver | 추가 항목 | 3.3.6.amzn.4-1.amzn2023 |
| HCatalog | Core | mariadb-connector-java | 추가 항목 | 2.7.2-1 |
| Hive | Core | hadoop-httpfs | 추가 항목 | 3.3.6.amzn.4-1.amzn2023 |
| Hive | Core | hadoop-yarn-proxyserver | 추가 항목 | 3.3.6.amzn.4-1.amzn2023 |
| Hive | Core | hive-hbase | 추가 항목 | 3.1.3.amzn.11-1.amzn2023 |
| Hive | Core | mariadb-connector-java | 추가 항목 | 2.7.2-1 |
| Hive | Core | s3-dist-cp | 추가 항목 | 2.32.0-1.amzn2023 |
| 피닉스 | Core | s3-dist-cp | 추가 항목 | 2.32.0-1.amzn2023 |
| Spark | Core | spark-datanucleus | 추가 항목 | 3.5.1.amzn.0-1.amzn2023 |
| Tez의 Hive 실행 시간 비교 | Core | hadoop-mapreduce | 추가 항목 | 3.3.6.amzn.4-1.amzn2023 |
| Tez의 Hive 실행 시간 비교 | Core | hadoop-mapreduce-historyserver | 추가 항목 | 3.3.6.amzn.4-1.amzn2023 |
| Tez의 Hive 실행 시간 비교 | Core | hadoop-yarn-proxyserver | 추가 항목 | 3.3.6.amzn.4-1.amzn2023 |
| Trino | Core | bigtop-utils | 추가 항목 | 1.2.0-1.amzn2023 |
| Trino | Core | hadoop-client | 추가 항목 | 3.3.6.amzn.4-1.amzn2023 |
| Trino | Core | hadoop-hdfs | 추가 항목 | 3.3.6.amzn.4-1.amzn2023 |
| Trino | Core | hadoop-hdfs-datanode | 추가 항목 | 3.3.6.amzn.4-1.amzn2023 |
| Trino | Core | hadoop-hdfs-journalnode | 추가 항목 | 3.3.6.amzn.4-1.amzn2023 |
| Trino | Core | hadoop-hdfs-namenode | 추가 항목 | 3.3.6.amzn.4-1.amzn2023 |
| Trino | Core | hadoop-kms | 추가 항목 | 3.3.6.amzn.4-1.amzn2023 |
| Trino | Core | hadoop-mapreduce | 추가 항목 | 3.3.6.amzn.4-1.amzn2023 |
| Trino | Core | hadoop-mapreduce-historyserver | 추가 항목 | 3.3.6.amzn.4-1.amzn2023 |
| Trino | Core | hadoop-yarn | 추가 항목 | 3.3.6.amzn.4-1.amzn2023 |
| Trino | Core | hadoop-yarn-nodemanager | 추가 항목 | 3.3.6.amzn.4-1.amzn2023 |
| Trino | Core | hadoop-yarn-proxyserver | 추가 항목 | 3.3.6.amzn.4-1.amzn2023 |
| Trino | Core | hadoop-yarn-resourcemanager | 추가 항목 | 3.3.6.amzn.4-1.amzn2023 |
| Trino | Core | hadoop-yarn-timelineserver | 추가 항목 | 3.3.6.amzn.4-1.amzn2023 |
| Trino | Core | hive | 추가 항목 | 3.1.3.amzn.11-1.amzn2023 |
| Trino | Core | hive-hcatalog-server | 추가 항목 | 3.1.3.amzn.11-1.amzn2023 |
| Trino | Core | mariadb-connector-java | 추가 항목 | 2.7.2-1 |
| Trino | Core | ranger-kms | 추가 항목 | 2.0.0-1.amzn2023 |
| Trino | Core | zookeeper | 추가 항목 | 3.9.1.amzn.1-1.amzn2023 |
| Trino | Core | zookeeper-server | 추가 항목 | 3.9.1.amzn.1-1.amzn2023 |
| Trino | Core | bigtop-groovy | 추가 항목 | 2.5.4-1.amzn2023 |
| Trino | Core | bigtop-jsvc | 추가 항목 | 1.2.4-1.amzn2023 |
| Trino | Core | hadoop | 추가 항목 | 3.3.6.amzn.4-1.amzn2023 |
| Trino | Core | hadoop-lzo | 추가 항목 | 0.4.19-1.amzn2023 |
| Trino | Core | hive-hcatalog | 추가 항목 | 3.1.3.amzn.11-1.amzn2023 |
| Trino | Core | hive-jdbc | 추가 항목 | 3.1.3.amzn.11-1.amzn2023 |
| Zookeeper | Core | emrfs | 추가 항목 | 2.63.0-1.amzn2023 |
| Zookeeper | Core | hadoop-client | 추가 항목 | 3.3.6.amzn.4-1.amzn2023 |
| Zookeeper | Core | hadoop-hdfs | 추가 항목 | 3.3.6.amzn.4-1.amzn2023 |
| Zookeeper | Core | hadoop-hdfs-datanode | 추가 항목 | 3.3.6.amzn.4-1.amzn2023 |
| Zookeeper | Core | hadoop-hdfs-journalnode | 추가 항목 | 3.3.6.amzn.4-1.amzn2023 |
| Zookeeper | Core | hadoop-hdfs-namenode | 추가 항목 | 3.3.6.amzn.4-1.amzn2023 |
| Zookeeper | Core | hadoop-httpfs | 추가 항목 | 3.3.6.amzn.4-1.amzn2023 |
| Zookeeper | Core | hadoop-kms | 추가 항목 | 3.3.6.amzn.4-1.amzn2023 |
| Zookeeper | Core | hadoop-mapreduce | 추가 항목 | 3.3.6.amzn.4-1.amzn2023 |
| Zookeeper | Core | hadoop-mapreduce-historyserver | 추가 항목 | 3.3.6.amzn.4-1.amzn2023 |
| Zookeeper | Core | hadoop-yarn | 추가 항목 | 3.3.6.amzn.4-1.amzn2023 |
| Zookeeper | Core | hadoop-yarn-nodemanager | 추가 항목 | 3.3.6.amzn.4-1.amzn2023 |
| Zookeeper | Core | hadoop-yarn-proxyserver | 추가 항목 | 3.3.6.amzn.4-1.amzn2023 |
| Zookeeper | Core | hadoop-yarn-resourcemanager | 추가 항목 | 3.3.6.amzn.4-1.amzn2023 |
| Zookeeper | Core | hadoop-yarn-timelineserver | 추가 항목 | 3.3.6.amzn.4-1.amzn2023 |
| Zookeeper | Core | ranger-kms | 추가 항목 | 2.0.0-1.amzn2023 |
# 7.2.0 일반적인 취약성 및 노출
다음 표에는 Amazon EMR 7.2.0의 권장 구성에서 실행되는 EMR 클러스터에 영향을 주지 않는 모든 CVE가 나와 있습니다. Amazon EMR은 업스트림 오픈 소스의 수정 사항 가용성에 종속되어 있으며, Amazon EMR이 수정 사항을 확인한 후 90일 이내에 코어 엔진 구성 요소의 일부로 안정적인 최신 버전을 제공합니다.
이 표는 2024년 9월 15일에 업데이트되었습니다.
| CVE ID | 심각도 | CVE 세부 정보 URL |
| --- | --- | --- |
| CVE-2015-1832 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2015-1832](https://nvd.nist.gov/vuln/detail/CVE-2015-1832) |
| CVE-2015-4852 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2015-4852](https://nvd.nist.gov/vuln/detail/CVE-2015-4852) |
| CVE-2015-7501 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2015-7501](https://nvd.nist.gov/vuln/detail/CVE-2015-7501) |
| CVE-2016-5018 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2016-5018](https://nvd.nist.gov/vuln/detail/CVE-2016-5018) |
| CVE-2017-1000487 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2017-1000487](https://nvd.nist.gov/vuln/detail/CVE-2017-1000487) |
| CVE-2017-12629 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2017-12629](https://nvd.nist.gov/vuln/detail/CVE-2017-12629) |
| CVE-2017-15095 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2017-15095](https://nvd.nist.gov/vuln/detail/CVE-2017-15095) |
| CVE-2017-15095 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2017-15095](https://nvd.nist.gov/vuln/detail/CVE-2017-15095) |
| CVE-2017-17485 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2017-17485](https://nvd.nist.gov/vuln/detail/CVE-2017-17485) |
| CVE-2017-17485 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2017-17485](https://nvd.nist.gov/vuln/detail/CVE-2017-17485) |
| CVE-2017-7525 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2017-7525](https://nvd.nist.gov/vuln/detail/CVE-2017-7525) |
| CVE-2017-7657 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2017-7657](https://nvd.nist.gov/vuln/detail/CVE-2017-7657) |
| CVE-2017-7658 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2017-7658](https://nvd.nist.gov/vuln/detail/CVE-2017-7658) |
| CVE-2018-11307 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-11307](https://nvd.nist.gov/vuln/detail/CVE-2018-11307) |
| CVE-2018-11307 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-11307](https://nvd.nist.gov/vuln/detail/CVE-2018-11307) |
| CVE-2018-11307 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-11307](https://nvd.nist.gov/vuln/detail/CVE-2018-11307) |
| CVE-2018-14718 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-14718](https://nvd.nist.gov/vuln/detail/CVE-2018-14718) |
| CVE-2018-14718 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-14718](https://nvd.nist.gov/vuln/detail/CVE-2018-14718) |
| CVE-2018-14718 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-14718](https://nvd.nist.gov/vuln/detail/CVE-2018-14718) |
| CVE-2018-14719 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-14719](https://nvd.nist.gov/vuln/detail/CVE-2018-14719) |
| CVE-2018-14719 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-14719](https://nvd.nist.gov/vuln/detail/CVE-2018-14719) |
| CVE-2018-14719 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-14719](https://nvd.nist.gov/vuln/detail/CVE-2018-14719) |
| CVE-2018-14720 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-14720](https://nvd.nist.gov/vuln/detail/CVE-2018-14720) |
| CVE-2018-14720 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-14720](https://nvd.nist.gov/vuln/detail/CVE-2018-14720) |
| CVE-2018-14720 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-14720](https://nvd.nist.gov/vuln/detail/CVE-2018-14720) |
| CVE-2018-14721 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-14721](https://nvd.nist.gov/vuln/detail/CVE-2018-14721) |
| CVE-2018-14721 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-14721](https://nvd.nist.gov/vuln/detail/CVE-2018-14721) |
| CVE-2018-14721 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-14721](https://nvd.nist.gov/vuln/detail/CVE-2018-14721) |
| CVE-2018-17190 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-17190](https://nvd.nist.gov/vuln/detail/CVE-2018-17190) |
| CVE-2018-19360 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-19360](https://nvd.nist.gov/vuln/detail/CVE-2018-19360) |
| CVE-2018-19360 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-19360](https://nvd.nist.gov/vuln/detail/CVE-2018-19360) |
| CVE-2018-19360 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-19360](https://nvd.nist.gov/vuln/detail/CVE-2018-19360) |
| CVE-2018-19361 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-19361](https://nvd.nist.gov/vuln/detail/CVE-2018-19361) |
| CVE-2018-19361 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-19361](https://nvd.nist.gov/vuln/detail/CVE-2018-19361) |
| CVE-2018-19361 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-19361](https://nvd.nist.gov/vuln/detail/CVE-2018-19361) |
| CVE-2018-19362 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-19362](https://nvd.nist.gov/vuln/detail/CVE-2018-19362) |
| CVE-2018-19362 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-19362](https://nvd.nist.gov/vuln/detail/CVE-2018-19362) |
| CVE-2018-19362 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-19362](https://nvd.nist.gov/vuln/detail/CVE-2018-19362) |
| CVE-2018-7489 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-7489](https://nvd.nist.gov/vuln/detail/CVE-2018-7489) |
| CVE-2018-7489 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-7489](https://nvd.nist.gov/vuln/detail/CVE-2018-7489) |
| CVE-2018-7489 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2018-7489](https://nvd.nist.gov/vuln/detail/CVE-2018-7489) |
| CVE-2019-10202 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-10202](https://nvd.nist.gov/vuln/detail/CVE-2019-10202) |
| CVE-2019-14379 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14379](https://nvd.nist.gov/vuln/detail/CVE-2019-14379) |
| CVE-2019-14379 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14379](https://nvd.nist.gov/vuln/detail/CVE-2019-14379) |
| CVE-2019-14379 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14379](https://nvd.nist.gov/vuln/detail/CVE-2019-14379) |
| CVE-2019-14379 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14379](https://nvd.nist.gov/vuln/detail/CVE-2019-14379) |
| CVE-2019-14540 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14540](https://nvd.nist.gov/vuln/detail/CVE-2019-14540) |
| CVE-2019-14540 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14540](https://nvd.nist.gov/vuln/detail/CVE-2019-14540) |
| CVE-2019-14540 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14540](https://nvd.nist.gov/vuln/detail/CVE-2019-14540) |
| CVE-2019-14540 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14540](https://nvd.nist.gov/vuln/detail/CVE-2019-14540) |
| CVE-2019-14892 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14892](https://nvd.nist.gov/vuln/detail/CVE-2019-14892) |
| CVE-2019-14892 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14892](https://nvd.nist.gov/vuln/detail/CVE-2019-14892) |
| CVE-2019-14892 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14892](https://nvd.nist.gov/vuln/detail/CVE-2019-14892) |
| CVE-2019-14892 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14892](https://nvd.nist.gov/vuln/detail/CVE-2019-14892) |
| CVE-2019-14893 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14893](https://nvd.nist.gov/vuln/detail/CVE-2019-14893) |
| CVE-2019-14893 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14893](https://nvd.nist.gov/vuln/detail/CVE-2019-14893) |
| CVE-2019-14893 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14893](https://nvd.nist.gov/vuln/detail/CVE-2019-14893) |
| CVE-2019-16335 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-16335](https://nvd.nist.gov/vuln/detail/CVE-2019-16335) |
| CVE-2019-16335 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-16335](https://nvd.nist.gov/vuln/detail/CVE-2019-16335) |
| CVE-2019-16335 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-16335](https://nvd.nist.gov/vuln/detail/CVE-2019-16335) |
| CVE-2019-16335 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-16335](https://nvd.nist.gov/vuln/detail/CVE-2019-16335) |
| CVE-2019-16942 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-16942](https://nvd.nist.gov/vuln/detail/CVE-2019-16942) |
| CVE-2019-16942 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-16942](https://nvd.nist.gov/vuln/detail/CVE-2019-16942) |
| CVE-2019-16942 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-16942](https://nvd.nist.gov/vuln/detail/CVE-2019-16942) |
| CVE-2019-16942 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-16942](https://nvd.nist.gov/vuln/detail/CVE-2019-16942) |
| CVE-2019-16943 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-16943](https://nvd.nist.gov/vuln/detail/CVE-2019-16943) |
| CVE-2019-16943 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-16943](https://nvd.nist.gov/vuln/detail/CVE-2019-16943) |
| CVE-2019-16943 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-16943](https://nvd.nist.gov/vuln/detail/CVE-2019-16943) |
| CVE-2019-16943 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-16943](https://nvd.nist.gov/vuln/detail/CVE-2019-16943) |
| CVE-2019-17195 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-17195](https://nvd.nist.gov/vuln/detail/CVE-2019-17195) |
| CVE-2019-17195 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-17195](https://nvd.nist.gov/vuln/detail/CVE-2019-17195) |
| CVE-2019-17267 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-17267](https://nvd.nist.gov/vuln/detail/CVE-2019-17267) |
| CVE-2019-17267 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-17267](https://nvd.nist.gov/vuln/detail/CVE-2019-17267) |
| CVE-2019-17267 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-17267](https://nvd.nist.gov/vuln/detail/CVE-2019-17267) |
| CVE-2019-17267 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-17267](https://nvd.nist.gov/vuln/detail/CVE-2019-17267) |
| CVE-2019-17531 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-17531](https://nvd.nist.gov/vuln/detail/CVE-2019-17531) |
| CVE-2019-17531 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-17531](https://nvd.nist.gov/vuln/detail/CVE-2019-17531) |
| CVE-2019-17531 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-17531](https://nvd.nist.gov/vuln/detail/CVE-2019-17531) |
| CVE-2019-17531 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-17531](https://nvd.nist.gov/vuln/detail/CVE-2019-17531) |
| CVE-2019-20330 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-20330](https://nvd.nist.gov/vuln/detail/CVE-2019-20330) |
| CVE-2019-20330 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-20330](https://nvd.nist.gov/vuln/detail/CVE-2019-20330) |
| CVE-2019-20330 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-20330](https://nvd.nist.gov/vuln/detail/CVE-2019-20330) |
| CVE-2019-20330 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-20330](https://nvd.nist.gov/vuln/detail/CVE-2019-20330) |
| CVE-2019-20444 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-20444](https://nvd.nist.gov/vuln/detail/CVE-2019-20444) |
| CVE-2019-20444 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-20444](https://nvd.nist.gov/vuln/detail/CVE-2019-20444) |
| CVE-2019-20445 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-20445](https://nvd.nist.gov/vuln/detail/CVE-2019-20445) |
| CVE-2019-20445 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2019-20445](https://nvd.nist.gov/vuln/detail/CVE-2019-20445) |
| CVE-2020-7692 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-7692](https://nvd.nist.gov/vuln/detail/CVE-2020-7692) |
| CVE-2020-7692 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-7692](https://nvd.nist.gov/vuln/detail/CVE-2020-7692) |
| CVE-2020-8840 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8840](https://nvd.nist.gov/vuln/detail/CVE-2020-8840) |
| CVE-2020-8840 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8840](https://nvd.nist.gov/vuln/detail/CVE-2020-8840) |
| CVE-2020-8840 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8840](https://nvd.nist.gov/vuln/detail/CVE-2020-8840) |
| CVE-2020-8840 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-8840](https://nvd.nist.gov/vuln/detail/CVE-2020-8840) |
| CVE-2020-9480 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-9480](https://nvd.nist.gov/vuln/detail/CVE-2020-9480) |
| CVE-2020-9546 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-9546](https://nvd.nist.gov/vuln/detail/CVE-2020-9546) |
| CVE-2020-9546 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-9546](https://nvd.nist.gov/vuln/detail/CVE-2020-9546) |
| CVE-2020-9546 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-9546](https://nvd.nist.gov/vuln/detail/CVE-2020-9546) |
| CVE-2020-9546 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-9546](https://nvd.nist.gov/vuln/detail/CVE-2020-9546) |
| CVE-2020-9547 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-9547](https://nvd.nist.gov/vuln/detail/CVE-2020-9547) |
| CVE-2020-9547 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-9547](https://nvd.nist.gov/vuln/detail/CVE-2020-9547) |
| CVE-2020-9547 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-9547](https://nvd.nist.gov/vuln/detail/CVE-2020-9547) |
| CVE-2020-9547 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-9547](https://nvd.nist.gov/vuln/detail/CVE-2020-9547) |
| CVE-2020-9548 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-9548](https://nvd.nist.gov/vuln/detail/CVE-2020-9548) |
| CVE-2020-9548 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-9548](https://nvd.nist.gov/vuln/detail/CVE-2020-9548) |
| CVE-2020-9548 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-9548](https://nvd.nist.gov/vuln/detail/CVE-2020-9548) |
| CVE-2020-9548 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2020-9548](https://nvd.nist.gov/vuln/detail/CVE-2020-9548) |
| CVE-2021-26291 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2021-26291](https://nvd.nist.gov/vuln/detail/CVE-2021-26291) |
| CVE-2021-26291 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2021-26291](https://nvd.nist.gov/vuln/detail/CVE-2021-26291) |
| CVE-2021-32797 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2021-32797](https://nvd.nist.gov/vuln/detail/CVE-2021-32797) |
| CVE-2021-32798 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2021-32798](https://nvd.nist.gov/vuln/detail/CVE-2021-32798) |
| CVE-2021-35958 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2021-35958](https://nvd.nist.gov/vuln/detail/CVE-2021-35958) |
| CVE-2021-37404 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2021-37404](https://nvd.nist.gov/vuln/detail/CVE-2021-37404) |
| CVE-2022-1471 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-1471](https://nvd.nist.gov/vuln/detail/CVE-2022-1471) |
| CVE-2022-1471 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-1471](https://nvd.nist.gov/vuln/detail/CVE-2022-1471) |
| CVE-2022-1471 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-1471](https://nvd.nist.gov/vuln/detail/CVE-2022-1471) |
| CVE-2022-1471 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-1471](https://nvd.nist.gov/vuln/detail/CVE-2022-1471) |
| CVE-2022-25168 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-25168](https://nvd.nist.gov/vuln/detail/CVE-2022-25168) |
| CVE-2022-26612 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-26612](https://nvd.nist.gov/vuln/detail/CVE-2022-26612) |
| CVE-2022-32532 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-32532](https://nvd.nist.gov/vuln/detail/CVE-2022-32532) |
| CVE-2022-33980 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-33980](https://nvd.nist.gov/vuln/detail/CVE-2022-33980) |
| CVE-2022-37865 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-37865](https://nvd.nist.gov/vuln/detail/CVE-2022-37865) |
| CVE-2022-39135 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-39135](https://nvd.nist.gov/vuln/detail/CVE-2022-39135) |
| CVE-2022-40664 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-40664](https://nvd.nist.gov/vuln/detail/CVE-2022-40664) |
| CVE-2022-42889 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42889](https://nvd.nist.gov/vuln/detail/CVE-2022-42889) |
| CVE-2022-46337 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-46337](https://nvd.nist.gov/vuln/detail/CVE-2022-46337) |
| CVE-2022-46337 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-46337](https://nvd.nist.gov/vuln/detail/CVE-2022-46337) |
| CVE-2022-46337 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2022-46337](https://nvd.nist.gov/vuln/detail/CVE-2022-46337) |
| CVE-2023-38647 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2023-38647](https://nvd.nist.gov/vuln/detail/CVE-2023-38647) |
| CVE-2023-38647 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2023-38647](https://nvd.nist.gov/vuln/detail/CVE-2023-38647) |
| CVE-2023-44981 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2023-44981](https://nvd.nist.gov/vuln/detail/CVE-2023-44981) |
| CVE-2023-44981 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2023-44981](https://nvd.nist.gov/vuln/detail/CVE-2023-44981) |
| CVE-2023-44981 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2023-44981](https://nvd.nist.gov/vuln/detail/CVE-2023-44981) |
| CVE-2023-44981 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2023-44981](https://nvd.nist.gov/vuln/detail/CVE-2023-44981) |
| CVE-2023-44981 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2023-44981](https://nvd.nist.gov/vuln/detail/CVE-2023-44981) |
| CVE-2023-44981 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2023-44981](https://nvd.nist.gov/vuln/detail/CVE-2023-44981) |
| CVE-2024-1597 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2024-1597](https://nvd.nist.gov/vuln/detail/CVE-2024-1597) |
| CVE-2024-1597 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2024-1597](https://nvd.nist.gov/vuln/detail/CVE-2024-1597) |
| CVE-2024-1597 | 심각 | [https://nvd.nist.gov/vuln/detail/CVE-2024-1597](https://nvd.nist.gov/vuln/detail/CVE-2024-1597) |
| CVE-2012-0881 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2012-0881](https://nvd.nist.gov/vuln/detail/CVE-2012-0881) |
| CVE-2012-0881 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2012-0881](https://nvd.nist.gov/vuln/detail/CVE-2012-0881) |
| CVE-2013-4002 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2013-4002](https://nvd.nist.gov/vuln/detail/CVE-2013-4002) |
| CVE-2013-4002 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2013-4002](https://nvd.nist.gov/vuln/detail/CVE-2013-4002) |
| CVE-2014-0114 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2014-0114](https://nvd.nist.gov/vuln/detail/CVE-2014-0114) |
| CVE-2014-0114 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2014-0114](https://nvd.nist.gov/vuln/detail/CVE-2014-0114) |
| CVE-2015-2080 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2015-2080](https://nvd.nist.gov/vuln/detail/CVE-2015-2080) |
| CVE-2015-2156 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2015-2156](https://nvd.nist.gov/vuln/detail/CVE-2015-2156) |
| CVE-2015-2156 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2015-2156](https://nvd.nist.gov/vuln/detail/CVE-2015-2156) |
| CVE-2015-5237 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2015-5237](https://nvd.nist.gov/vuln/detail/CVE-2015-5237) |
| CVE-2015-5237 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2015-5237](https://nvd.nist.gov/vuln/detail/CVE-2015-5237) |
| CVE-2015-6420 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2015-6420](https://nvd.nist.gov/vuln/detail/CVE-2015-6420) |
| CVE-2016-1000338 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2016-1000338](https://nvd.nist.gov/vuln/detail/CVE-2016-1000338) |
| CVE-2016-1000340 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2016-1000340](https://nvd.nist.gov/vuln/detail/CVE-2016-1000340) |
| CVE-2016-1000342 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2016-1000342](https://nvd.nist.gov/vuln/detail/CVE-2016-1000342) |
| CVE-2016-1000343 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2016-1000343](https://nvd.nist.gov/vuln/detail/CVE-2016-1000343) |
| CVE-2016-1000344 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2016-1000344](https://nvd.nist.gov/vuln/detail/CVE-2016-1000344) |
| CVE-2016-1000352 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2016-1000352](https://nvd.nist.gov/vuln/detail/CVE-2016-1000352) |
| CVE-2016-6796 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2016-6796](https://nvd.nist.gov/vuln/detail/CVE-2016-6796) |
| CVE-2017-1000034 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2017-1000034](https://nvd.nist.gov/vuln/detail/CVE-2017-1000034) |
| CVE-2017-12612 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2017-12612](https://nvd.nist.gov/vuln/detail/CVE-2017-12612) |
| CVE-2017-15288 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2017-15288](https://nvd.nist.gov/vuln/detail/CVE-2017-15288) |
| CVE-2017-18640 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2017-18640](https://nvd.nist.gov/vuln/detail/CVE-2017-18640) |
| CVE-2017-18640 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2017-18640](https://nvd.nist.gov/vuln/detail/CVE-2017-18640) |
| CVE-2017-5637 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2017-5637](https://nvd.nist.gov/vuln/detail/CVE-2017-5637) |
| CVE-2017-7656 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2017-7656](https://nvd.nist.gov/vuln/detail/CVE-2017-7656) |
| CVE-2017-7687 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2017-7687](https://nvd.nist.gov/vuln/detail/CVE-2017-7687) |
| CVE-2017-9735 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2017-9735](https://nvd.nist.gov/vuln/detail/CVE-2017-9735) |
| CVE-2017-9790 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2017-9790](https://nvd.nist.gov/vuln/detail/CVE-2017-9790) |
| CVE-2018-10054 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-10054](https://nvd.nist.gov/vuln/detail/CVE-2018-10054) |
| CVE-2018-10936 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-10936](https://nvd.nist.gov/vuln/detail/CVE-2018-10936) |
| CVE-2018-11793 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-11793](https://nvd.nist.gov/vuln/detail/CVE-2018-11793) |
| CVE-2018-11804 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-11804](https://nvd.nist.gov/vuln/detail/CVE-2018-11804) |
| CVE-2018-12022 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-12022](https://nvd.nist.gov/vuln/detail/CVE-2018-12022) |
| CVE-2018-12022 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-12022](https://nvd.nist.gov/vuln/detail/CVE-2018-12022) |
| CVE-2018-12022 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-12022](https://nvd.nist.gov/vuln/detail/CVE-2018-12022) |
| CVE-2018-12023 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-12023](https://nvd.nist.gov/vuln/detail/CVE-2018-12023) |
| CVE-2018-12023 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-12023](https://nvd.nist.gov/vuln/detail/CVE-2018-12023) |
| CVE-2018-12023 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-12023](https://nvd.nist.gov/vuln/detail/CVE-2018-12023) |
| CVE-2018-3258 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-3258](https://nvd.nist.gov/vuln/detail/CVE-2018-3258) |
| CVE-2018-3827 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-3827](https://nvd.nist.gov/vuln/detail/CVE-2018-3827) |
| CVE-2018-3831 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-3831](https://nvd.nist.gov/vuln/detail/CVE-2018-3831) |
| CVE-2018-5968 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-5968](https://nvd.nist.gov/vuln/detail/CVE-2018-5968) |
| CVE-2018-5968 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-5968](https://nvd.nist.gov/vuln/detail/CVE-2018-5968) |
| CVE-2018-8012 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-8012](https://nvd.nist.gov/vuln/detail/CVE-2018-8012) |
| CVE-2018-8768 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2018-8768](https://nvd.nist.gov/vuln/detail/CVE-2018-8768) |
| CVE-2019-0204 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-0204](https://nvd.nist.gov/vuln/detail/CVE-2019-0204) |
| CVE-2019-0205 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-0205](https://nvd.nist.gov/vuln/detail/CVE-2019-0205) |
| CVE-2019-0205 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-0205](https://nvd.nist.gov/vuln/detail/CVE-2019-0205) |
| CVE-2019-0205 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-0205](https://nvd.nist.gov/vuln/detail/CVE-2019-0205) |
| CVE-2019-0205 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-0205](https://nvd.nist.gov/vuln/detail/CVE-2019-0205) |
| CVE-2019-10086 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-10086](https://nvd.nist.gov/vuln/detail/CVE-2019-10086) |
| CVE-2019-10086 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-10086](https://nvd.nist.gov/vuln/detail/CVE-2019-10086) |
| CVE-2019-10086 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-10086](https://nvd.nist.gov/vuln/detail/CVE-2019-10086) |
| CVE-2019-10086 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-10086](https://nvd.nist.gov/vuln/detail/CVE-2019-10086) |
| CVE-2019-10099 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-10099](https://nvd.nist.gov/vuln/detail/CVE-2019-10099) |
| CVE-2019-10172 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-10172](https://nvd.nist.gov/vuln/detail/CVE-2019-10172) |
| CVE-2019-12086 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-12086](https://nvd.nist.gov/vuln/detail/CVE-2019-12086) |
| CVE-2019-12086 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-12086](https://nvd.nist.gov/vuln/detail/CVE-2019-12086) |
| CVE-2019-12086 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-12086](https://nvd.nist.gov/vuln/detail/CVE-2019-12086) |
| CVE-2019-12086 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-12086](https://nvd.nist.gov/vuln/detail/CVE-2019-12086) |
| CVE-2019-14439 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14439](https://nvd.nist.gov/vuln/detail/CVE-2019-14439) |
| CVE-2019-14439 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14439](https://nvd.nist.gov/vuln/detail/CVE-2019-14439) |
| CVE-2019-14439 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14439](https://nvd.nist.gov/vuln/detail/CVE-2019-14439) |
| CVE-2019-14439 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-14439](https://nvd.nist.gov/vuln/detail/CVE-2019-14439) |
| CVE-2019-16869 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-16869](https://nvd.nist.gov/vuln/detail/CVE-2019-16869) |
| CVE-2019-16869 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-16869](https://nvd.nist.gov/vuln/detail/CVE-2019-16869) |
| CVE-2019-17566 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-17566](https://nvd.nist.gov/vuln/detail/CVE-2019-17566) |
| CVE-2019-17566 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-17566](https://nvd.nist.gov/vuln/detail/CVE-2019-17566) |
| CVE-2019-7611 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2019-7611](https://nvd.nist.gov/vuln/detail/CVE-2019-7611) |
| CVE-2020-10650 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10650](https://nvd.nist.gov/vuln/detail/CVE-2020-10650) |
| CVE-2020-10650 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10650](https://nvd.nist.gov/vuln/detail/CVE-2020-10650) |
| CVE-2020-10650 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10650](https://nvd.nist.gov/vuln/detail/CVE-2020-10650) |
| CVE-2020-10650 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10650](https://nvd.nist.gov/vuln/detail/CVE-2020-10650) |
| CVE-2020-10672 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10672](https://nvd.nist.gov/vuln/detail/CVE-2020-10672) |
| CVE-2020-10672 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10672](https://nvd.nist.gov/vuln/detail/CVE-2020-10672) |
| CVE-2020-10672 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10672](https://nvd.nist.gov/vuln/detail/CVE-2020-10672) |
| CVE-2020-10672 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10672](https://nvd.nist.gov/vuln/detail/CVE-2020-10672) |
| CVE-2020-10673 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10673](https://nvd.nist.gov/vuln/detail/CVE-2020-10673) |
| CVE-2020-10673 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10673](https://nvd.nist.gov/vuln/detail/CVE-2020-10673) |
| CVE-2020-10673 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10673](https://nvd.nist.gov/vuln/detail/CVE-2020-10673) |
| CVE-2020-10673 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10673](https://nvd.nist.gov/vuln/detail/CVE-2020-10673) |
| CVE-2020-10968 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10968](https://nvd.nist.gov/vuln/detail/CVE-2020-10968) |
| CVE-2020-10968 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10968](https://nvd.nist.gov/vuln/detail/CVE-2020-10968) |
| CVE-2020-10968 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10968](https://nvd.nist.gov/vuln/detail/CVE-2020-10968) |
| CVE-2020-10968 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10968](https://nvd.nist.gov/vuln/detail/CVE-2020-10968) |
| CVE-2020-10969 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10969](https://nvd.nist.gov/vuln/detail/CVE-2020-10969) |
| CVE-2020-10969 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10969](https://nvd.nist.gov/vuln/detail/CVE-2020-10969) |
| CVE-2020-10969 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10969](https://nvd.nist.gov/vuln/detail/CVE-2020-10969) |
| CVE-2020-10969 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-10969](https://nvd.nist.gov/vuln/detail/CVE-2020-10969) |
| CVE-2020-11111 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11111](https://nvd.nist.gov/vuln/detail/CVE-2020-11111) |
| CVE-2020-11111 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11111](https://nvd.nist.gov/vuln/detail/CVE-2020-11111) |
| CVE-2020-11111 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11111](https://nvd.nist.gov/vuln/detail/CVE-2020-11111) |
| CVE-2020-11111 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11111](https://nvd.nist.gov/vuln/detail/CVE-2020-11111) |
| CVE-2020-11112 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11112](https://nvd.nist.gov/vuln/detail/CVE-2020-11112) |
| CVE-2020-11112 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11112](https://nvd.nist.gov/vuln/detail/CVE-2020-11112) |
| CVE-2020-11112 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11112](https://nvd.nist.gov/vuln/detail/CVE-2020-11112) |
| CVE-2020-11113 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11113](https://nvd.nist.gov/vuln/detail/CVE-2020-11113) |
| CVE-2020-11113 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11113](https://nvd.nist.gov/vuln/detail/CVE-2020-11113) |
| CVE-2020-11113 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11113](https://nvd.nist.gov/vuln/detail/CVE-2020-11113) |
| CVE-2020-11619 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11619](https://nvd.nist.gov/vuln/detail/CVE-2020-11619) |
| CVE-2020-11619 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11619](https://nvd.nist.gov/vuln/detail/CVE-2020-11619) |
| CVE-2020-11619 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11619](https://nvd.nist.gov/vuln/detail/CVE-2020-11619) |
| CVE-2020-11620 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11620](https://nvd.nist.gov/vuln/detail/CVE-2020-11620) |
| CVE-2020-11620 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11620](https://nvd.nist.gov/vuln/detail/CVE-2020-11620) |
| CVE-2020-11620 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11620](https://nvd.nist.gov/vuln/detail/CVE-2020-11620) |
| CVE-2020-11620 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11620](https://nvd.nist.gov/vuln/detail/CVE-2020-11620) |
| CVE-2020-11988 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-11988](https://nvd.nist.gov/vuln/detail/CVE-2020-11988) |
| CVE-2020-13692 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-13692](https://nvd.nist.gov/vuln/detail/CVE-2020-13692) |
| CVE-2020-13936 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-13936](https://nvd.nist.gov/vuln/detail/CVE-2020-13936) |
| CVE-2020-13949 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-13949](https://nvd.nist.gov/vuln/detail/CVE-2020-13949) |
| CVE-2020-13949 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-13949](https://nvd.nist.gov/vuln/detail/CVE-2020-13949) |
| CVE-2020-13949 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-13949](https://nvd.nist.gov/vuln/detail/CVE-2020-13949) |
| CVE-2020-13949 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-13949](https://nvd.nist.gov/vuln/detail/CVE-2020-13949) |
| CVE-2020-13949 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-13949](https://nvd.nist.gov/vuln/detail/CVE-2020-13949) |
| CVE-2020-14060 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14060](https://nvd.nist.gov/vuln/detail/CVE-2020-14060) |
| CVE-2020-14060 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14060](https://nvd.nist.gov/vuln/detail/CVE-2020-14060) |
| CVE-2020-14060 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14060](https://nvd.nist.gov/vuln/detail/CVE-2020-14060) |
| CVE-2020-14060 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14060](https://nvd.nist.gov/vuln/detail/CVE-2020-14060) |
| CVE-2020-14061 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14061](https://nvd.nist.gov/vuln/detail/CVE-2020-14061) |
| CVE-2020-14061 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14061](https://nvd.nist.gov/vuln/detail/CVE-2020-14061) |
| CVE-2020-14061 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14061](https://nvd.nist.gov/vuln/detail/CVE-2020-14061) |
| CVE-2020-14061 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14061](https://nvd.nist.gov/vuln/detail/CVE-2020-14061) |
| CVE-2020-14062 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14062](https://nvd.nist.gov/vuln/detail/CVE-2020-14062) |
| CVE-2020-14062 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14062](https://nvd.nist.gov/vuln/detail/CVE-2020-14062) |
| CVE-2020-14062 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14062](https://nvd.nist.gov/vuln/detail/CVE-2020-14062) |
| CVE-2020-14062 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14062](https://nvd.nist.gov/vuln/detail/CVE-2020-14062) |
| CVE-2020-14195 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14195](https://nvd.nist.gov/vuln/detail/CVE-2020-14195) |
| CVE-2020-14195 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14195](https://nvd.nist.gov/vuln/detail/CVE-2020-14195) |
| CVE-2020-14195 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14195](https://nvd.nist.gov/vuln/detail/CVE-2020-14195) |
| CVE-2020-14195 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-14195](https://nvd.nist.gov/vuln/detail/CVE-2020-14195) |
| CVE-2020-17533 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-17533](https://nvd.nist.gov/vuln/detail/CVE-2020-17533) |
| CVE-2020-24616 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-24616](https://nvd.nist.gov/vuln/detail/CVE-2020-24616) |
| CVE-2020-24616 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-24616](https://nvd.nist.gov/vuln/detail/CVE-2020-24616) |
| CVE-2020-24616 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-24616](https://nvd.nist.gov/vuln/detail/CVE-2020-24616) |
| CVE-2020-24616 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-24616](https://nvd.nist.gov/vuln/detail/CVE-2020-24616) |
| CVE-2020-24750 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-24750](https://nvd.nist.gov/vuln/detail/CVE-2020-24750) |
| CVE-2020-24750 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-24750](https://nvd.nist.gov/vuln/detail/CVE-2020-24750) |
| CVE-2020-24750 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-24750](https://nvd.nist.gov/vuln/detail/CVE-2020-24750) |
| CVE-2020-24750 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-24750](https://nvd.nist.gov/vuln/detail/CVE-2020-24750) |
| CVE-2020-25649 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-25649](https://nvd.nist.gov/vuln/detail/CVE-2020-25649) |
| CVE-2020-25649 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-25649](https://nvd.nist.gov/vuln/detail/CVE-2020-25649) |
| CVE-2020-25649 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-25649](https://nvd.nist.gov/vuln/detail/CVE-2020-25649) |
| CVE-2020-25649 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-25649](https://nvd.nist.gov/vuln/detail/CVE-2020-25649) |
| CVE-2020-28491 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-28491](https://nvd.nist.gov/vuln/detail/CVE-2020-28491) |
| CVE-2020-35211 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-35211](https://nvd.nist.gov/vuln/detail/CVE-2020-35211) |
| CVE-2020-35490 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-35490](https://nvd.nist.gov/vuln/detail/CVE-2020-35490) |
| CVE-2020-35490 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-35490](https://nvd.nist.gov/vuln/detail/CVE-2020-35490) |
| CVE-2020-35490 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-35490](https://nvd.nist.gov/vuln/detail/CVE-2020-35490) |
| CVE-2020-35490 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-35490](https://nvd.nist.gov/vuln/detail/CVE-2020-35490) |
| CVE-2020-35490 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-35490](https://nvd.nist.gov/vuln/detail/CVE-2020-35490) |
| CVE-2020-35491 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-35491](https://nvd.nist.gov/vuln/detail/CVE-2020-35491) |
| CVE-2020-35491 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-35491](https://nvd.nist.gov/vuln/detail/CVE-2020-35491) |
| CVE-2020-35491 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-35491](https://nvd.nist.gov/vuln/detail/CVE-2020-35491) |
| CVE-2020-35491 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-35491](https://nvd.nist.gov/vuln/detail/CVE-2020-35491) |
| CVE-2020-35491 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-35491](https://nvd.nist.gov/vuln/detail/CVE-2020-35491) |
| CVE-2020-35728 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-35728](https://nvd.nist.gov/vuln/detail/CVE-2020-35728) |
| CVE-2020-35728 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-35728](https://nvd.nist.gov/vuln/detail/CVE-2020-35728) |
| CVE-2020-35728 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-35728](https://nvd.nist.gov/vuln/detail/CVE-2020-35728) |
| CVE-2020-35728 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-35728](https://nvd.nist.gov/vuln/detail/CVE-2020-35728) |
| CVE-2020-35728 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-35728](https://nvd.nist.gov/vuln/detail/CVE-2020-35728) |
| CVE-2020-36179 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36179](https://nvd.nist.gov/vuln/detail/CVE-2020-36179) |
| CVE-2020-36179 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36179](https://nvd.nist.gov/vuln/detail/CVE-2020-36179) |
| CVE-2020-36179 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36179](https://nvd.nist.gov/vuln/detail/CVE-2020-36179) |
| CVE-2020-36179 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36179](https://nvd.nist.gov/vuln/detail/CVE-2020-36179) |
| CVE-2020-36179 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36179](https://nvd.nist.gov/vuln/detail/CVE-2020-36179) |
| CVE-2020-36180 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36180](https://nvd.nist.gov/vuln/detail/CVE-2020-36180) |
| CVE-2020-36180 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36180](https://nvd.nist.gov/vuln/detail/CVE-2020-36180) |
| CVE-2020-36180 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36180](https://nvd.nist.gov/vuln/detail/CVE-2020-36180) |
| CVE-2020-36180 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36180](https://nvd.nist.gov/vuln/detail/CVE-2020-36180) |
| CVE-2020-36180 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36180](https://nvd.nist.gov/vuln/detail/CVE-2020-36180) |
| CVE-2020-36181 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36181](https://nvd.nist.gov/vuln/detail/CVE-2020-36181) |
| CVE-2020-36181 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36181](https://nvd.nist.gov/vuln/detail/CVE-2020-36181) |
| CVE-2020-36181 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36181](https://nvd.nist.gov/vuln/detail/CVE-2020-36181) |
| CVE-2020-36181 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36181](https://nvd.nist.gov/vuln/detail/CVE-2020-36181) |
| CVE-2020-36181 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36181](https://nvd.nist.gov/vuln/detail/CVE-2020-36181) |
| CVE-2020-36182 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36182](https://nvd.nist.gov/vuln/detail/CVE-2020-36182) |
| CVE-2020-36182 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36182](https://nvd.nist.gov/vuln/detail/CVE-2020-36182) |
| CVE-2020-36182 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36182](https://nvd.nist.gov/vuln/detail/CVE-2020-36182) |
| CVE-2020-36182 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36182](https://nvd.nist.gov/vuln/detail/CVE-2020-36182) |
| CVE-2020-36182 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36182](https://nvd.nist.gov/vuln/detail/CVE-2020-36182) |
| CVE-2020-36183 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36183](https://nvd.nist.gov/vuln/detail/CVE-2020-36183) |
| CVE-2020-36183 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36183](https://nvd.nist.gov/vuln/detail/CVE-2020-36183) |
| CVE-2020-36183 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36183](https://nvd.nist.gov/vuln/detail/CVE-2020-36183) |
| CVE-2020-36183 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36183](https://nvd.nist.gov/vuln/detail/CVE-2020-36183) |
| CVE-2020-36183 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36183](https://nvd.nist.gov/vuln/detail/CVE-2020-36183) |
| CVE-2020-36184 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36184](https://nvd.nist.gov/vuln/detail/CVE-2020-36184) |
| CVE-2020-36184 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36184](https://nvd.nist.gov/vuln/detail/CVE-2020-36184) |
| CVE-2020-36184 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36184](https://nvd.nist.gov/vuln/detail/CVE-2020-36184) |
| CVE-2020-36184 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36184](https://nvd.nist.gov/vuln/detail/CVE-2020-36184) |
| CVE-2020-36184 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36184](https://nvd.nist.gov/vuln/detail/CVE-2020-36184) |
| CVE-2020-36185 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36185](https://nvd.nist.gov/vuln/detail/CVE-2020-36185) |
| CVE-2020-36185 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36185](https://nvd.nist.gov/vuln/detail/CVE-2020-36185) |
| CVE-2020-36185 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36185](https://nvd.nist.gov/vuln/detail/CVE-2020-36185) |
| CVE-2020-36185 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36185](https://nvd.nist.gov/vuln/detail/CVE-2020-36185) |
| CVE-2020-36185 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36185](https://nvd.nist.gov/vuln/detail/CVE-2020-36185) |
| CVE-2020-36186 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36186](https://nvd.nist.gov/vuln/detail/CVE-2020-36186) |
| CVE-2020-36186 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36186](https://nvd.nist.gov/vuln/detail/CVE-2020-36186) |
| CVE-2020-36186 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36186](https://nvd.nist.gov/vuln/detail/CVE-2020-36186) |
| CVE-2020-36186 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36186](https://nvd.nist.gov/vuln/detail/CVE-2020-36186) |
| CVE-2020-36186 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36186](https://nvd.nist.gov/vuln/detail/CVE-2020-36186) |
| CVE-2020-36187 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36187](https://nvd.nist.gov/vuln/detail/CVE-2020-36187) |
| CVE-2020-36187 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36187](https://nvd.nist.gov/vuln/detail/CVE-2020-36187) |
| CVE-2020-36187 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36187](https://nvd.nist.gov/vuln/detail/CVE-2020-36187) |
| CVE-2020-36187 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36187](https://nvd.nist.gov/vuln/detail/CVE-2020-36187) |
| CVE-2020-36187 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36187](https://nvd.nist.gov/vuln/detail/CVE-2020-36187) |
| CVE-2020-36188 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36188](https://nvd.nist.gov/vuln/detail/CVE-2020-36188) |
| CVE-2020-36188 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36188](https://nvd.nist.gov/vuln/detail/CVE-2020-36188) |
| CVE-2020-36188 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36188](https://nvd.nist.gov/vuln/detail/CVE-2020-36188) |
| CVE-2020-36188 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36188](https://nvd.nist.gov/vuln/detail/CVE-2020-36188) |
| CVE-2020-36188 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36188](https://nvd.nist.gov/vuln/detail/CVE-2020-36188) |
| CVE-2020-36189 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36189](https://nvd.nist.gov/vuln/detail/CVE-2020-36189) |
| CVE-2020-36189 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36189](https://nvd.nist.gov/vuln/detail/CVE-2020-36189) |
| CVE-2020-36189 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36189](https://nvd.nist.gov/vuln/detail/CVE-2020-36189) |
| CVE-2020-36189 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36189](https://nvd.nist.gov/vuln/detail/CVE-2020-36189) |
| CVE-2020-36189 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36189](https://nvd.nist.gov/vuln/detail/CVE-2020-36189) |
| CVE-2020-36518 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36518](https://nvd.nist.gov/vuln/detail/CVE-2020-36518) |
| CVE-2020-36518 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36518](https://nvd.nist.gov/vuln/detail/CVE-2020-36518) |
| CVE-2020-36518 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36518](https://nvd.nist.gov/vuln/detail/CVE-2020-36518) |
| CVE-2020-36518 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36518](https://nvd.nist.gov/vuln/detail/CVE-2020-36518) |
| CVE-2020-36518 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36518](https://nvd.nist.gov/vuln/detail/CVE-2020-36518) |
| CVE-2020-36518 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-36518](https://nvd.nist.gov/vuln/detail/CVE-2020-36518) |
| CVE-2020-9492 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2020-9492](https://nvd.nist.gov/vuln/detail/CVE-2020-9492) |
| CVE-2021-20190 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-20190](https://nvd.nist.gov/vuln/detail/CVE-2021-20190) |
| CVE-2021-20190 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-20190](https://nvd.nist.gov/vuln/detail/CVE-2021-20190) |
| CVE-2021-20190 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-20190](https://nvd.nist.gov/vuln/detail/CVE-2021-20190) |
| CVE-2021-20190 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-20190](https://nvd.nist.gov/vuln/detail/CVE-2021-20190) |
| CVE-2021-20190 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-20190](https://nvd.nist.gov/vuln/detail/CVE-2021-20190) |
| CVE-2021-22573 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-22573](https://nvd.nist.gov/vuln/detail/CVE-2021-22573) |
| CVE-2021-22573 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-22573](https://nvd.nist.gov/vuln/detail/CVE-2021-22573) |
| CVE-2021-22573 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-22573](https://nvd.nist.gov/vuln/detail/CVE-2021-22573) |
| CVE-2021-25646 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-25646](https://nvd.nist.gov/vuln/detail/CVE-2021-25646) |
| CVE-2021-26919 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-26919](https://nvd.nist.gov/vuln/detail/CVE-2021-26919) |
| CVE-2021-28165 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-28165](https://nvd.nist.gov/vuln/detail/CVE-2021-28165) |
| CVE-2021-31684 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-31684](https://nvd.nist.gov/vuln/detail/CVE-2021-31684) |
| CVE-2021-31684 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-31684](https://nvd.nist.gov/vuln/detail/CVE-2021-31684) |
| CVE-2021-31684 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-31684](https://nvd.nist.gov/vuln/detail/CVE-2021-31684) |
| CVE-2021-33036 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-33036](https://nvd.nist.gov/vuln/detail/CVE-2021-33036) |
| CVE-2021-33813 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-33813](https://nvd.nist.gov/vuln/detail/CVE-2021-33813) |
| CVE-2021-33813 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-33813](https://nvd.nist.gov/vuln/detail/CVE-2021-33813) |
| CVE-2021-34538 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-34538](https://nvd.nist.gov/vuln/detail/CVE-2021-34538) |
| CVE-2021-34538 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-34538](https://nvd.nist.gov/vuln/detail/CVE-2021-34538) |
| CVE-2021-34538 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-34538](https://nvd.nist.gov/vuln/detail/CVE-2021-34538) |
| CVE-2021-35515 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-35515](https://nvd.nist.gov/vuln/detail/CVE-2021-35515) |
| CVE-2021-35515 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-35515](https://nvd.nist.gov/vuln/detail/CVE-2021-35515) |
| CVE-2021-35515 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-35515](https://nvd.nist.gov/vuln/detail/CVE-2021-35515) |
| CVE-2021-35515 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-35515](https://nvd.nist.gov/vuln/detail/CVE-2021-35515) |
| CVE-2021-35515 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-35515](https://nvd.nist.gov/vuln/detail/CVE-2021-35515) |
| CVE-2021-35515 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-35515](https://nvd.nist.gov/vuln/detail/CVE-2021-35515) |
| CVE-2021-35515 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-35515](https://nvd.nist.gov/vuln/detail/CVE-2021-35515) |
| CVE-2021-35516 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-35516](https://nvd.nist.gov/vuln/detail/CVE-2021-35516) |
| CVE-2021-35516 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-35516](https://nvd.nist.gov/vuln/detail/CVE-2021-35516) |
| CVE-2021-35516 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-35516](https://nvd.nist.gov/vuln/detail/CVE-2021-35516) |
| CVE-2021-35516 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-35516](https://nvd.nist.gov/vuln/detail/CVE-2021-35516) |
| CVE-2021-35516 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-35516](https://nvd.nist.gov/vuln/detail/CVE-2021-35516) |
| CVE-2021-35516 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-35516](https://nvd.nist.gov/vuln/detail/CVE-2021-35516) |
| CVE-2021-35516 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-35516](https://nvd.nist.gov/vuln/detail/CVE-2021-35516) |
| CVE-2021-35517 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-35517](https://nvd.nist.gov/vuln/detail/CVE-2021-35517) |
| CVE-2021-35517 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-35517](https://nvd.nist.gov/vuln/detail/CVE-2021-35517) |
| CVE-2021-35517 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-35517](https://nvd.nist.gov/vuln/detail/CVE-2021-35517) |
| CVE-2021-35517 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-35517](https://nvd.nist.gov/vuln/detail/CVE-2021-35517) |
| CVE-2021-35517 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-35517](https://nvd.nist.gov/vuln/detail/CVE-2021-35517) |
| CVE-2021-36090 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-36090](https://nvd.nist.gov/vuln/detail/CVE-2021-36090) |
| CVE-2021-36090 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-36090](https://nvd.nist.gov/vuln/detail/CVE-2021-36090) |
| CVE-2021-36090 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-36090](https://nvd.nist.gov/vuln/detail/CVE-2021-36090) |
| CVE-2021-36090 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-36090](https://nvd.nist.gov/vuln/detail/CVE-2021-36090) |
| CVE-2021-36090 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-36090](https://nvd.nist.gov/vuln/detail/CVE-2021-36090) |
| CVE-2021-37136 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-37136](https://nvd.nist.gov/vuln/detail/CVE-2021-37136) |
| CVE-2021-37136 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-37136](https://nvd.nist.gov/vuln/detail/CVE-2021-37136) |
| CVE-2021-37137 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-37137](https://nvd.nist.gov/vuln/detail/CVE-2021-37137) |
| CVE-2021-37137 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-37137](https://nvd.nist.gov/vuln/detail/CVE-2021-37137) |
| CVE-2021-37714 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-37714](https://nvd.nist.gov/vuln/detail/CVE-2021-37714) |
| CVE-2021-37714 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-37714](https://nvd.nist.gov/vuln/detail/CVE-2021-37714) |
| CVE-2021-37714 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-37714](https://nvd.nist.gov/vuln/detail/CVE-2021-37714) |
| CVE-2021-37714 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-37714](https://nvd.nist.gov/vuln/detail/CVE-2021-37714) |
| CVE-2021-46877 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2021-46877](https://nvd.nist.gov/vuln/detail/CVE-2021-46877) |
| CVE-2022-24758 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-24758](https://nvd.nist.gov/vuln/detail/CVE-2022-24758) |
| CVE-2022-25647 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-25647](https://nvd.nist.gov/vuln/detail/CVE-2022-25647) |
| CVE-2022-25647 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-25647](https://nvd.nist.gov/vuln/detail/CVE-2022-25647) |
| CVE-2022-25647 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-25647](https://nvd.nist.gov/vuln/detail/CVE-2022-25647) |
| CVE-2022-25647 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-25647](https://nvd.nist.gov/vuln/detail/CVE-2022-25647) |
| CVE-2022-25647 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-25647](https://nvd.nist.gov/vuln/detail/CVE-2022-25647) |
| CVE-2022-25647 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-25647](https://nvd.nist.gov/vuln/detail/CVE-2022-25647) |
| CVE-2022-25647 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-25647](https://nvd.nist.gov/vuln/detail/CVE-2022-25647) |
| CVE-2022-25647 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-25647](https://nvd.nist.gov/vuln/detail/CVE-2022-25647) |
| CVE-2022-25857 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-25857](https://nvd.nist.gov/vuln/detail/CVE-2022-25857) |
| CVE-2022-25857 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-25857](https://nvd.nist.gov/vuln/detail/CVE-2022-25857) |
| CVE-2022-25857 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-25857](https://nvd.nist.gov/vuln/detail/CVE-2022-25857) |
| CVE-2022-25857 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-25857](https://nvd.nist.gov/vuln/detail/CVE-2022-25857) |
| CVE-2022-31197 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-31197](https://nvd.nist.gov/vuln/detail/CVE-2022-31197) |
| CVE-2022-3171 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3171](https://nvd.nist.gov/vuln/detail/CVE-2022-3171) |
| CVE-2022-3171 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3171](https://nvd.nist.gov/vuln/detail/CVE-2022-3171) |
| CVE-2022-3171 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3171](https://nvd.nist.gov/vuln/detail/CVE-2022-3171) |
| CVE-2022-3171 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3171](https://nvd.nist.gov/vuln/detail/CVE-2022-3171) |
| CVE-2022-3171 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3171](https://nvd.nist.gov/vuln/detail/CVE-2022-3171) |
| CVE-2022-3171 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3171](https://nvd.nist.gov/vuln/detail/CVE-2022-3171) |
| CVE-2022-3171 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3171](https://nvd.nist.gov/vuln/detail/CVE-2022-3171) |
| CVE-2022-3171 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3171](https://nvd.nist.gov/vuln/detail/CVE-2022-3171) |
| CVE-2022-3171 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3171](https://nvd.nist.gov/vuln/detail/CVE-2022-3171) |
| CVE-2022-34169 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-34169](https://nvd.nist.gov/vuln/detail/CVE-2022-34169) |
| CVE-2022-3509 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3509](https://nvd.nist.gov/vuln/detail/CVE-2022-3509) |
| CVE-2022-3509 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3509](https://nvd.nist.gov/vuln/detail/CVE-2022-3509) |
| CVE-2022-3509 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3509](https://nvd.nist.gov/vuln/detail/CVE-2022-3509) |
| CVE-2022-3509 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3509](https://nvd.nist.gov/vuln/detail/CVE-2022-3509) |
| CVE-2022-3509 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3509](https://nvd.nist.gov/vuln/detail/CVE-2022-3509) |
| CVE-2022-3509 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3509](https://nvd.nist.gov/vuln/detail/CVE-2022-3509) |
| CVE-2022-3509 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3509](https://nvd.nist.gov/vuln/detail/CVE-2022-3509) |
| CVE-2022-3509 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3509](https://nvd.nist.gov/vuln/detail/CVE-2022-3509) |
| CVE-2022-3509 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3509](https://nvd.nist.gov/vuln/detail/CVE-2022-3509) |
| CVE-2022-3510 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3510](https://nvd.nist.gov/vuln/detail/CVE-2022-3510) |
| CVE-2022-3510 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3510](https://nvd.nist.gov/vuln/detail/CVE-2022-3510) |
| CVE-2022-3510 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3510](https://nvd.nist.gov/vuln/detail/CVE-2022-3510) |
| CVE-2022-3510 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3510](https://nvd.nist.gov/vuln/detail/CVE-2022-3510) |
| CVE-2022-3510 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3510](https://nvd.nist.gov/vuln/detail/CVE-2022-3510) |
| CVE-2022-3510 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3510](https://nvd.nist.gov/vuln/detail/CVE-2022-3510) |
| CVE-2022-3510 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3510](https://nvd.nist.gov/vuln/detail/CVE-2022-3510) |
| CVE-2022-3510 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3510](https://nvd.nist.gov/vuln/detail/CVE-2022-3510) |
| CVE-2022-3510 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-3510](https://nvd.nist.gov/vuln/detail/CVE-2022-3510) |
| CVE-2022-36364 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-36364](https://nvd.nist.gov/vuln/detail/CVE-2022-36364) |
| CVE-2022-37866 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-37866](https://nvd.nist.gov/vuln/detail/CVE-2022-37866) |
| CVE-2022-37866 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-37866](https://nvd.nist.gov/vuln/detail/CVE-2022-37866) |
| CVE-2022-40146 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-40146](https://nvd.nist.gov/vuln/detail/CVE-2022-40146) |
| CVE-2022-40149 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-40149](https://nvd.nist.gov/vuln/detail/CVE-2022-40149) |
| CVE-2022-40149 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-40149](https://nvd.nist.gov/vuln/detail/CVE-2022-40149) |
| CVE-2022-40149 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-40149](https://nvd.nist.gov/vuln/detail/CVE-2022-40149) |
| CVE-2022-40149 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-40149](https://nvd.nist.gov/vuln/detail/CVE-2022-40149) |
| CVE-2022-40149 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-40149](https://nvd.nist.gov/vuln/detail/CVE-2022-40149) |
| CVE-2022-40150 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-40150](https://nvd.nist.gov/vuln/detail/CVE-2022-40150) |
| CVE-2022-40150 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-40150](https://nvd.nist.gov/vuln/detail/CVE-2022-40150) |
| CVE-2022-40150 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-40150](https://nvd.nist.gov/vuln/detail/CVE-2022-40150) |
| CVE-2022-40150 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-40150](https://nvd.nist.gov/vuln/detail/CVE-2022-40150) |
| CVE-2022-40150 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-40150](https://nvd.nist.gov/vuln/detail/CVE-2022-40150) |
| CVE-2022-40152 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-40152](https://nvd.nist.gov/vuln/detail/CVE-2022-40152) |
| CVE-2022-40152 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-40152](https://nvd.nist.gov/vuln/detail/CVE-2022-40152) |
| CVE-2022-41704 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-41704](https://nvd.nist.gov/vuln/detail/CVE-2022-41704) |
| CVE-2022-42003 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42003](https://nvd.nist.gov/vuln/detail/CVE-2022-42003) |
| CVE-2022-42003 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42003](https://nvd.nist.gov/vuln/detail/CVE-2022-42003) |
| CVE-2022-42003 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42003](https://nvd.nist.gov/vuln/detail/CVE-2022-42003) |
| CVE-2022-42003 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42003](https://nvd.nist.gov/vuln/detail/CVE-2022-42003) |
| CVE-2022-42003 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42003](https://nvd.nist.gov/vuln/detail/CVE-2022-42003) |
| CVE-2022-42003 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42003](https://nvd.nist.gov/vuln/detail/CVE-2022-42003) |
| CVE-2022-42003 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42003](https://nvd.nist.gov/vuln/detail/CVE-2022-42003) |
| CVE-2022-42003 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42003](https://nvd.nist.gov/vuln/detail/CVE-2022-42003) |
| CVE-2022-42003 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42003](https://nvd.nist.gov/vuln/detail/CVE-2022-42003) |
| CVE-2022-42003 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42003](https://nvd.nist.gov/vuln/detail/CVE-2022-42003) |
| CVE-2022-42003 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42003](https://nvd.nist.gov/vuln/detail/CVE-2022-42003) |
| CVE-2022-42003 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42003](https://nvd.nist.gov/vuln/detail/CVE-2022-42003) |
| CVE-2022-42004 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42004](https://nvd.nist.gov/vuln/detail/CVE-2022-42004) |
| CVE-2022-42004 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42004](https://nvd.nist.gov/vuln/detail/CVE-2022-42004) |
| CVE-2022-42004 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42004](https://nvd.nist.gov/vuln/detail/CVE-2022-42004) |
| CVE-2022-42004 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42004](https://nvd.nist.gov/vuln/detail/CVE-2022-42004) |
| CVE-2022-42004 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42004](https://nvd.nist.gov/vuln/detail/CVE-2022-42004) |
| CVE-2022-42004 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42004](https://nvd.nist.gov/vuln/detail/CVE-2022-42004) |
| CVE-2022-42004 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42004](https://nvd.nist.gov/vuln/detail/CVE-2022-42004) |
| CVE-2022-42004 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42004](https://nvd.nist.gov/vuln/detail/CVE-2022-42004) |
| CVE-2022-42004 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42004](https://nvd.nist.gov/vuln/detail/CVE-2022-42004) |
| CVE-2022-42004 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42004](https://nvd.nist.gov/vuln/detail/CVE-2022-42004) |
| CVE-2022-4244 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-4244](https://nvd.nist.gov/vuln/detail/CVE-2022-4244) |
| CVE-2022-42890 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-42890](https://nvd.nist.gov/vuln/detail/CVE-2022-42890) |
| CVE-2022-44729 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-44729](https://nvd.nist.gov/vuln/detail/CVE-2022-44729) |
| CVE-2022-44729 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-44729](https://nvd.nist.gov/vuln/detail/CVE-2022-44729) |
| CVE-2022-44729 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-44729](https://nvd.nist.gov/vuln/detail/CVE-2022-44729) |
| CVE-2022-45685 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-45685](https://nvd.nist.gov/vuln/detail/CVE-2022-45685) |
| CVE-2022-45685 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-45685](https://nvd.nist.gov/vuln/detail/CVE-2022-45685) |
| CVE-2022-45685 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-45685](https://nvd.nist.gov/vuln/detail/CVE-2022-45685) |
| CVE-2022-45685 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-45685](https://nvd.nist.gov/vuln/detail/CVE-2022-45685) |
| CVE-2022-45685 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-45685](https://nvd.nist.gov/vuln/detail/CVE-2022-45685) |
| CVE-2022-45688 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-45688](https://nvd.nist.gov/vuln/detail/CVE-2022-45688) |
| CVE-2022-45688 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-45688](https://nvd.nist.gov/vuln/detail/CVE-2022-45688) |
| CVE-2022-45688 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-45688](https://nvd.nist.gov/vuln/detail/CVE-2022-45688) |
| CVE-2022-45693 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-45693](https://nvd.nist.gov/vuln/detail/CVE-2022-45693) |
| CVE-2022-45693 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-45693](https://nvd.nist.gov/vuln/detail/CVE-2022-45693) |
| CVE-2022-45693 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-45693](https://nvd.nist.gov/vuln/detail/CVE-2022-45693) |
| CVE-2022-45693 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-45693](https://nvd.nist.gov/vuln/detail/CVE-2022-45693) |
| CVE-2022-45693 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-45693](https://nvd.nist.gov/vuln/detail/CVE-2022-45693) |
| CVE-2022-46751 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-46751](https://nvd.nist.gov/vuln/detail/CVE-2022-46751) |
| CVE-2022-46751 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-46751](https://nvd.nist.gov/vuln/detail/CVE-2022-46751) |
| CVE-2022-46751 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2022-46751](https://nvd.nist.gov/vuln/detail/CVE-2022-46751) |
| CVE-2023-1370 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-1370](https://nvd.nist.gov/vuln/detail/CVE-2023-1370) |
| CVE-2023-1370 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-1370](https://nvd.nist.gov/vuln/detail/CVE-2023-1370) |
| CVE-2023-1370 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-1370](https://nvd.nist.gov/vuln/detail/CVE-2023-1370) |
| CVE-2023-1370 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-1370](https://nvd.nist.gov/vuln/detail/CVE-2023-1370) |
| CVE-2023-1370 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-1370](https://nvd.nist.gov/vuln/detail/CVE-2023-1370) |
| CVE-2023-1428 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-1428](https://nvd.nist.gov/vuln/detail/CVE-2023-1428) |
| CVE-2023-1436 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-1436](https://nvd.nist.gov/vuln/detail/CVE-2023-1436) |
| CVE-2023-1436 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-1436](https://nvd.nist.gov/vuln/detail/CVE-2023-1436) |
| CVE-2023-1436 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-1436](https://nvd.nist.gov/vuln/detail/CVE-2023-1436) |
| CVE-2023-1436 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-1436](https://nvd.nist.gov/vuln/detail/CVE-2023-1436) |
| CVE-2023-1436 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-1436](https://nvd.nist.gov/vuln/detail/CVE-2023-1436) |
| CVE-2023-20883 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-20883](https://nvd.nist.gov/vuln/detail/CVE-2023-20883) |
| CVE-2023-24580 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-24580](https://nvd.nist.gov/vuln/detail/CVE-2023-24580) |
| CVE-2023-25194 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-25194](https://nvd.nist.gov/vuln/detail/CVE-2023-25194) |
| CVE-2023-25194 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-25194](https://nvd.nist.gov/vuln/detail/CVE-2023-25194) |
| CVE-2023-25194 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-25194](https://nvd.nist.gov/vuln/detail/CVE-2023-25194) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-2976 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-2976](https://nvd.nist.gov/vuln/detail/CVE-2023-2976) |
| CVE-2023-31418 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-31418](https://nvd.nist.gov/vuln/detail/CVE-2023-31418) |
| CVE-2023-32731 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-32731](https://nvd.nist.gov/vuln/detail/CVE-2023-32731) |
| CVE-2023-34453 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-34453](https://nvd.nist.gov/vuln/detail/CVE-2023-34453) |
| CVE-2023-34453 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-34453](https://nvd.nist.gov/vuln/detail/CVE-2023-34453) |
| CVE-2023-34453 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-34453](https://nvd.nist.gov/vuln/detail/CVE-2023-34453) |
| CVE-2023-34453 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-34453](https://nvd.nist.gov/vuln/detail/CVE-2023-34453) |
| CVE-2023-34453 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-34453](https://nvd.nist.gov/vuln/detail/CVE-2023-34453) |
| CVE-2023-34454 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-34454](https://nvd.nist.gov/vuln/detail/CVE-2023-34454) |
| CVE-2023-34454 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-34454](https://nvd.nist.gov/vuln/detail/CVE-2023-34454) |
| CVE-2023-34454 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-34454](https://nvd.nist.gov/vuln/detail/CVE-2023-34454) |
| CVE-2023-34454 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-34454](https://nvd.nist.gov/vuln/detail/CVE-2023-34454) |
| CVE-2023-34454 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-34454](https://nvd.nist.gov/vuln/detail/CVE-2023-34454) |
| CVE-2023-34455 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-34455](https://nvd.nist.gov/vuln/detail/CVE-2023-34455) |
| CVE-2023-34455 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-34455](https://nvd.nist.gov/vuln/detail/CVE-2023-34455) |
| CVE-2023-34455 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-34455](https://nvd.nist.gov/vuln/detail/CVE-2023-34455) |
| CVE-2023-34455 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-34455](https://nvd.nist.gov/vuln/detail/CVE-2023-34455) |
| CVE-2023-34455 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-34455](https://nvd.nist.gov/vuln/detail/CVE-2023-34455) |
| CVE-2023-34610 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-34610](https://nvd.nist.gov/vuln/detail/CVE-2023-34610) |
| CVE-2023-36053 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-36053](https://nvd.nist.gov/vuln/detail/CVE-2023-36053) |
| CVE-2023-3635 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-3635](https://nvd.nist.gov/vuln/detail/CVE-2023-3635) |
| CVE-2023-3635 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-3635](https://nvd.nist.gov/vuln/detail/CVE-2023-3635) |
| CVE-2023-3635 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-3635](https://nvd.nist.gov/vuln/detail/CVE-2023-3635) |
| CVE-2023-3635 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-3635](https://nvd.nist.gov/vuln/detail/CVE-2023-3635) |
| CVE-2023-3635 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-3635](https://nvd.nist.gov/vuln/detail/CVE-2023-3635) |
| CVE-2023-36478 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-36478](https://nvd.nist.gov/vuln/detail/CVE-2023-36478) |
| CVE-2023-36478 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-36478](https://nvd.nist.gov/vuln/detail/CVE-2023-36478) |
| CVE-2023-39410 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-39410](https://nvd.nist.gov/vuln/detail/CVE-2023-39410) |
| CVE-2023-39410 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-39410](https://nvd.nist.gov/vuln/detail/CVE-2023-39410) |
| CVE-2023-39410 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-39410](https://nvd.nist.gov/vuln/detail/CVE-2023-39410) |
| CVE-2023-39410 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-39410](https://nvd.nist.gov/vuln/detail/CVE-2023-39410) |
| CVE-2023-39410 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-39410](https://nvd.nist.gov/vuln/detail/CVE-2023-39410) |
| CVE-2023-39410 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-39410](https://nvd.nist.gov/vuln/detail/CVE-2023-39410) |
| CVE-2023-39410 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-39410](https://nvd.nist.gov/vuln/detail/CVE-2023-39410) |
| CVE-2023-41164 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-41164](https://nvd.nist.gov/vuln/detail/CVE-2023-41164) |
| CVE-2023-43642 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-43642](https://nvd.nist.gov/vuln/detail/CVE-2023-43642) |
| CVE-2023-43642 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-43642](https://nvd.nist.gov/vuln/detail/CVE-2023-43642) |
| CVE-2023-43642 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-43642](https://nvd.nist.gov/vuln/detail/CVE-2023-43642) |
| CVE-2023-43642 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-43642](https://nvd.nist.gov/vuln/detail/CVE-2023-43642) |
| CVE-2023-43642 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-43642](https://nvd.nist.gov/vuln/detail/CVE-2023-43642) |
| CVE-2023-43642 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-43642](https://nvd.nist.gov/vuln/detail/CVE-2023-43642) |
| CVE-2023-43642 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-43642](https://nvd.nist.gov/vuln/detail/CVE-2023-43642) |
| CVE-2023-43665 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-43665](https://nvd.nist.gov/vuln/detail/CVE-2023-43665) |
| CVE-2023-46120 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-46120](https://nvd.nist.gov/vuln/detail/CVE-2023-46120) |
| CVE-2023-46695 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-46695](https://nvd.nist.gov/vuln/detail/CVE-2023-46695) |
| CVE-2023-4759 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-4759](https://nvd.nist.gov/vuln/detail/CVE-2023-4759) |
| CVE-2023-5072 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-5072](https://nvd.nist.gov/vuln/detail/CVE-2023-5072) |
| CVE-2023-5072 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-5072](https://nvd.nist.gov/vuln/detail/CVE-2023-5072) |
| CVE-2023-5072 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-5072](https://nvd.nist.gov/vuln/detail/CVE-2023-5072) |
| CVE-2023-6378 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-6378](https://nvd.nist.gov/vuln/detail/CVE-2023-6378) |
| CVE-2023-6378 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-6378](https://nvd.nist.gov/vuln/detail/CVE-2023-6378) |
| CVE-2023-6378 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-6378](https://nvd.nist.gov/vuln/detail/CVE-2023-6378) |
| CVE-2023-6378 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-6378](https://nvd.nist.gov/vuln/detail/CVE-2023-6378) |
| CVE-2023-6481 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-6481](https://nvd.nist.gov/vuln/detail/CVE-2023-6481) |
| CVE-2023-6481 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-6481](https://nvd.nist.gov/vuln/detail/CVE-2023-6481) |
| CVE-2023-6481 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-6481](https://nvd.nist.gov/vuln/detail/CVE-2023-6481) |
| CVE-2023-6481 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2023-6481](https://nvd.nist.gov/vuln/detail/CVE-2023-6481) |
| CVE-2024-21634 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-21634](https://nvd.nist.gov/vuln/detail/CVE-2024-21634) |
| CVE-2024-24680 | 높음 | [https://nvd.nist.gov/vuln/detail/CVE-2024-24680](https://nvd.nist.gov/vuln/detail/CVE-2024-24680) |
## 7.2.0 릴리스 정보
다음 릴리스 정보에는 Amazon EMR 릴리스 7.2.0에 대한 정보가 포함됩니다. 변경 사항은 7.2.0에 관련됩니다.
**새로운 기능**
+ **애플리케이션 업그레이드** – Amazon EMR 7.2.0 application upgrades include Iceberg 1.5.0-amzn-0 and Delta 3.1.0.
+ Amazon EMR은 Amazon S3 Express One Zone 스토리지 클래스에서 HBase, Flink 및 Hive와 같은 다른 애플리케이션을 사용할 수 있도록 지원을 추가합니다.
+ 이 릴리스에서는 복원된 객체를 읽을 수 있는 기능을 추가하므로, `S3A` 프로토콜로 S3 위치에서 Glacier 객체를 읽을 수 있습니다. 이 기능은 Spark, Flink 및 Hive에서 작동합니다.
+ 관리형 조정을 사용하는 노드 레이블 - 시장 유형 또는 노드 유형에 따라 인스턴스에 노드 레이블을 사용하여 Amazon EMR에서 자동 조정을 개선합니다. 자세한 내용은 [Amazon EMR에서 관리형 조정 사용](https://docs.aws.amazon.com/emr/latest/ManagementGuide/emr-managed-scaling.html)을 참조하세요.
**알려진 문제**
+ Python 3.11은 EMR Studio에서 지원되지 않습니다.
**변경 사항, 향상된 기능 및 해결된 문제**
+ 이 릴리스에서는 노드에 스레드 수가 많거나 파일 핸들이 열려 있을 때 인스턴스의 상태를 모니터링하는 온클러스터 인스턴스 상태 스크립트에서 과도한 CPU 및 메모리 리소스를 명확하게 표시하지 않고 소비하는 문제가 수정되었습니다.
+ Spark 3.3.1(EMR 버전 6.10 이상에서 지원됨)부터 폐기 호스트의 모든 실행기는 *DECOMMISSIONING* 상태라는 새로운 `ExecutorState` 상태로 설정됩니다. Yarn은 폐기 중인 실행기를 사용하여 작업을 할당할 수 없으므로 필요한 경우 실행 중인 작업에 대해 새 실행기를 요청하세요. 따라서 EMR Managed Scaling, EMR Auto Scaling 또는 EMR-EC2 클러스터의 사용자 지정 조정 메커니즘을 사용하는 동안 Spark DRA를 비활성화하면 Yarn이 각 작업에 허용되는 최대 실행기를 요청할 수 있습니다. 이 문제를 방지하려면 위의 기능 조합을 사용할 때 `spark.dynamicAllocation.enabled` 속성을 `TRUE`(기본값)로 설정한 상태로 둡니다. 또한 Spark 작업의 `spark.dynamicAllocation.maxExecutors` 및 `spark.dynamicAllocation.minExecutors` 속성 값을 설정하여 작업 실행 중에 할당된 실행기 수를 제한하여 최소 및 최대 실행기 제약 조건을 설정할 수도 있습니다.
+ 이 릴리스는 내부 단계 정리 작업 중에 발생할 수 있는 교착 문제를 수정합니다. 이 작업은 EMR 클러스터에서 완료할 때 단계의 수명 주기를 관리합니다. 이 문제는 단계 작업 및 조정과 같은 중요한 Amazon EMR 작업에 영향을 미칩니다.
+ 이 릴리스는 특정 기존 로그 파일이 있는 사용자 지정 AMI를 사용하는 사용자 지정 클러스터로 인해 Amazon EMR 로그 관리 대몬이 실패할 수 있는 문제를 해결합니다.
+ Amazon EMR 7.2.0은 클러스터 관리 및 모니터링 활동을 담당하는 Amazon EMR 데몬을 AWS SDK v1에서 v2로 업그레이드합니다.
+ Amazon EMR 5.36 이상, 6.6 이상 또는 7.0 이상의 *최신 패치 릴리스*가 적용된 클러스터를 시작하는 경우 Amazon EMR은 기본 Amazon EMR AMI에 대한 최신 Amazon Linux 2023 or Amazon Linux 2 릴리스를 사용합니다. 자세한 내용은 [Amazon EMR에 대한 기본 Amazon Linux AMI 사용](https://docs.aws.amazon.com/emr/latest/ManagementGuide/emr-default-ami.html)을 참조하세요.
[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/ko_kr/emr/latest/ReleaseGuide/emr-720-release.html)
## 7.2.0 기본 Java 버전
Amazon EMR 릴리스 7.2 이상에서는 Apache Livy를 제외한 Corretto 17(JDK 17)을 지원하는 애플리케이션에 대해 기본적으로 Amazon Corretto 17(OpenJDK 기반)이 함께 제공됩니다.
다음 표에서는 Amazon EMR 7.2.0에 있는 애플리케이션의 기본 Java 버전을 확인할 수 있습니다. 클러스터의 기본 JVM을 변경하려면 클러스터에서 실행되는 각 애플리케이션에 대해 [특정 Java 가상 머신을 사용하도록 애플리케이션 구성](configuring-java8.md)의 지침을 따릅니다. 클러스터에서는 Java 런타임 버전 1개만 사용할 수 있습니다. Amazon EMR은 동일한 클러스터에서 다양한 런타임 버전을 사용해 서로 다른 노드 또는 애플리케이션을 실행하는 것을 지원하지 않습니다.
| 애플리케이션 | Java 및 Amazon Corretto 버전(기본값은 굵은체로 표시) |
| --- | --- |
| 델타 | 17, 11, 8 |
| Flink | 17, 11, 8 |
| HBase | 11, 8 |
| HCatalog | 17, 11, 8 |
| Hadoop | 17, 11, 8 |
| Hive | 17, 11, 8 |
| Hudi | 17, 11, 8 |
| Iceberg | 17, 11, 8 |
| Livy | 17, 11, 8 |
| Oozie | 17, 11, 8 |
| 피닉스 | 8 |
| PrestoDB | 8 |
| Spark | 17, 11, 8 |
| Spark RAPIDS | 17, 11, 8 |
| Sqoop | 8 |
| Tez의 Hive 실행 시간 비교 | 17, 11, 8 |
| Trino | 21, 17 |
| Zeppelin | 8 |
| Pig | 8 |
| Zookeeper | 8 |
## 7.2.0 구성 요소 버전
이 릴리스를 통해 Amazon EMR이 설치하는 구성 요소는 다음과 같습니다. 일부는 빅 데이터 애플리케이션 패키지의 일부로 설치됩니다. 나머지는 Amazon EMR에 고유하며 시스템 프로세스 및 기능을 위해 설치됩니다. 이는 일반적으로 `emr` 또는 `aws`로 시작됩니다. 최근 Amazon EMR 릴리스의 빅 데이터 애플리케이션 패키지는 일반적으로 커뮤니티에서 발견된 최신 버전입니다. 가능한 한 빨리 Amazon EMR에서 커뮤니티 릴리스를 제공합니다.
Amazon EMR의 일부 구성 요소는 커뮤니티 버전과 다릅니다. 이러한 구성 요소에는 `CommunityVersion-amzn-EmrVersion` 양식의 버전 레이블이 있습니다. `EmrVersion`은 0에서 시작합니다. 예를 들어, 버전 2.2의 `myapp-component`라는 오픈 소스 커뮤니티 구성 요소가 다른 Amazon EMR 릴리스에 포함되도록 세 번 수정된 경우 해당 릴리스 버전은 `2.2-amzn-2`로 나열됩니다.
| 구성 요소 | 버전 | 설명 |
| --- | --- | --- |
| adot-java-agent | 1.31.0 | 애플리케이션 대몬(daemon)에서 지표를 수집하는 Java 에이전트입니다. |
| delta | 3.1.0 | Delta Lake는 방대한 분석 데이터 세트를 위한 오픈 테이블 형식입니다. |
| emr-amazon-cloudwatch-agent | 1.300032.2-amzn-0 | Amazon EC2 인스턴스에서 내부 시스템 수준 지표와 사용자 지정 애플리케이션 지표를 수집하는 애플리케이션입니다. |
| emr-ddb | 5.4.0 | 하둡 에코시스템 애플리케이션용 Amazon DynamoDB 커넥터 |
| emr-goodies | 3.11.0 | 편리한 하둡 에코시스템용 추가 라이브러리 |
| emr-kinesis | 3.15.0 | 하둡 에코시스템 애플리케이션용 Amazon Kinesis 커넥터. |
| emr-notebook-env | 1.16.0 | Jupyter Enterprise Gateway가 포함된 EMR 노트북용 Conda 환경 |
| emr-s3-dist-cp | 2.32.0 | Amazon S3용으로 최적화된 분사 복사 애플리케이션. |
| emr-s3-select | 2.11.0 | EMR S3Select 커넥터 |
| emr-wal-cli | 1.2.2 | emrwal 목록/삭제에 사용되는 CLI입니다. |
| emrfs | 2.63.0 | 하둡 에코시스템 애플리케이션용 Amazon S3 커넥터. |
| flink-client | 1.18.1-amzn-1 | Apache Flink 명령줄 클라이언트 스크립트 및 애플리케이션 |
| flink-jobmanager-config | 1.18.1-amzn-1 | Apache Flink JobManager에 대한 EMR 노드에서 리소스를 관리합니다. |
| hadoop-client | 3.3.6-amzn-4 | 'hdfs', 'hadoop', 'yarn' 등과 같은 하둡 명령줄 클라이언트 |
| hadoop-hdfs-datanode | 3.3.6-amzn-4 | 블록을 저장하는 HDFS 노드 수준 서비스 |
| hadoop-hdfs-library | 3.3.6-amzn-4 | HDFS 명령줄 클라이언트 및 라이브러리 |
| hadoop-hdfs-namenode | 3.3.6-amzn-4 | 파일 이름 및 블록 위치를 추적하는 HDFS 서비스 |
| hadoop-hdfs-journalnode | 3.3.6-amzn-4 | HA 클러스터에서 하둡 파일 시스템 저널을 관리하기 위한 HDFS 서비스 |
| hadoop-httpfs-server | 3.3.6-amzn-4 | HDFS 작업에 대한 HTTP 엔드포인트 |
| hadoop-kms-server | 3.3.6-amzn-4 | 하둡의 KeyProvider API를 기반으로 하는 암호화 키 관리 서버 |
| hadoop-mapred | 3.3.6-amzn-4 | MapReduce 애플리케이션을 실행하는 MapReduce 실행 엔진 라이브러리 |
| hadoop-yarn-nodemanager | 3.3.6-amzn-4 | 개별 노드의 컨테이너를 관리하는 YARN 서비스 |
| hadoop-yarn-resourcemanager | 3.3.6-amzn-4 | 클러스터 리소스 및 분산 애플리케이션을 할당 및 관리하는 YARN 서비스 |
| hadoop-yarn-timeline-server | 3.3.6-amzn-4 | YARN 애플리케이션의 현재 및 기록 정보를 가져오는 서비스 |
| hbase-hmaster | 2.4.17-amzn-6 | 리전 조정 및 관리 명령의 실행을 담당하는 HBase 클러스터용 서비스 |
| hbase-region-server | 2.4.17-amzn-6 | 한 개 이상의 HBase 리전에 서비스를 제공하는 서비스 |
| hbase-client | 2.4.17-amzn-6 | HBase 명령줄 클라이언트 |
| hbase-rest-server | 2.4.17-amzn-6 | HBase용 RESTful HTTP 엔드포인트를 제공하는 서비스 |
| hbase-thrift-server | 2.4.17-amzn-6 | HBase에 Thrift 엔드포인트를 제공하는 서비스 |
| hbase-operator-tools | 2.4.17-amzn-6 | Apache HBase 클러스터용 복구 도구. |
| hcatalog-client | 3.1.3-amzn-11 | hcatalog-server를 조정하기 위한 'hcat' 명령줄 클라이언트 |
| hcatalog-server | 3.1.3-amzn-11 | 분산 애플리케이션용 스토리지 관리 계층, 테이블 및 HCatalog를 제공하는 서비스 |
| hcatalog-webhcat-server | 3.1.3-amzn-11 | HCatalog에 REST 인터페이스를 제공하는 HTTP 엔드포인트 |
| hive-client | 3.1.3-amzn-11 | Hive 명령줄 클라이언트 |
| hive-hbase | 3.1.3-amzn-11 | Hive-hbase 클라이언트 |
| hive-metastore-server | 3.1.3-amzn-11 | 하둡 작업에 대한 SQL용 메타데이터가 저장되는 시맨틱 리포지토리인 Hive 메타스토어에 액세스하기 위한 서비스 |
| hive-server2 | 3.1.3-amzn-11 | Hive 쿼리를 웹 요청으로 수락하기 위한 서비스 |
| hudi | 0.14.1-amzn-1 | 짧은 지연 시간 및 높은 효율성으로 데이터 파이프라인을 구동하는 증분 처리 프레임워크. |
| hudi-presto | 0.14.1-amzn-1 | Hudi로 Presto를 실행하기 위한 번들 라이브러리. |
| hudi-trino | 0.14.1-amzn-1 | Hudi와 함께 Trnio를 실행하기 위한 번들 라이브러리. |
| hudi-spark | 0.14.1-amzn-1 | Hudi와 함께 Spark를 실행하기 위한 번들 라이브러리. |
| hue-server | 4.11.0 | 하둡 에코시스템 애플리케이션을 사용하여 데이터를 분석하는 웹 애플리케이션. |
| iceberg | 1.5.0-amzn-0 | Apache Iceberg는 방대한 분석 데이터 세트를 위한 오픈 테이블 형식입니다. |
| jupyterhub | 1.5.0 | Jupyter Notebook용 다중 사용자 서버 |
| livy-server | 0.8.0-incubating | Apache Spark와 상호작용하기 위한 REST 인터페이스 |
| nginx | 1.12.1 | HTTP인 nginx [engine x] 및 역방향 프록시 서버 |
| mxnet | 1.9.1 | 유연성, 확장성 및 효율성이 뛰어난 딥 러닝용 라이브러리. |
| mariadb-server | 5.5.68 이상 | MariaDB 데이터베이스 서버. |
| nvidia-cuda | 11.8.0 | Nvidia 드라이버와 Cuda 도구 키트 |
| oozie-client | 5.2.1 | Oozie 명령줄 클라이언트 |
| oozie-server | 5.2.1 | Oozie 워크플로 요청을 수락하는 서비스 |
| opencv | 4.7.0 | 오픈 소스 컴퓨터 비전 라이브러리. |
| phoenix-library | 5.1.3 | 서버 및 클라이언트의 phoenix 라이브러리 |
| phoenix-connectors | 5.1.3 | Spark-3용 Apache Phoenix 커넥터 |
| phoenix-query-server | 6.0.0 | Avatica API에 대한 JSON 형식 액세스 및 프로토콜 버퍼 액세스를 비롯하여 JDBC 액세스를 제공하는 경량 서버 |
| presto-coordinator | 0.285-amzn-0 | presto-worker의 쿼리를 수락하고 쿼리 실행을 관리하는 서비스. |
| presto-worker | 0.285-amzn-0 | 여러 쿼리를 실행하는 서비스. |
| presto-client | 0.285-amzn-0 | Presto 서버가 시작되지 않은 HA 클러스터의 대기 마스터에 설치된 Presto 명령줄 클라이언트. |
| trino-coordinator | 436-amzn-0 | trino-workers의 쿼리를 수락하고 쿼리 실행을 관리하는 서비스. |
| trino-worker | 436-amzn-0 | 여러 쿼리를 실행하는 서비스. |
| trino-client | 436-amzn-0 | Trino 서버가 시작되지 않은 HA 클러스터의 대기 마스터에 설치된 Trino 명령줄 클라이언트. |
| pig-client | 0.17.0 | Pig 명령줄 클라이언트. |
| r | 4.3.2 | 통계 컴퓨팅용 R 프로젝트 |
| ranger-kms-server | 2.0.0 | Apache Ranger 키 관리 시스템 |
| spark-client | 3.5.1-amzn-0 | Spark 명령줄 클라이언트. |
| spark-history-server | 3.5.1-amzn-0 | 완료된 Spark 애플리케이션의 수명에 대해 기록된 이벤트를 조회하는 웹 UI. |
| spark-on-yarn | 3.5.1-amzn-0 | YARN용 인 메모리 실행 엔진. |
| spark-yarn-slave | 3.5.1-amzn-0 | YARN 슬레이브에서 필요한 Apache Spark 라이브러리. |
| spark-rapids | 24.02.0-amzn-0 | GPU로 Apache Spark를 가속화하는 Nvidia Spark RAPIDS 플러그인. |
| sqoop-client | 1.4.7 | Apache Sqoop 명령줄 클라이언트. |
| tensorflow | 2.11.0 | TensorFlow는 고성능 수치 계산용 오픈 소스 소프트웨어 라이브러리입니다. |
| tez-on-yarn | 0.10.2-amzn-9 | tez YARN 애플리케이션 및 라이브러리. |
| tez-on-worker | 0.10.2-amzn-9 | 워커 노드에 대한 tez YARN 애플리케이션 및 라이브러리. |
| zeppelin-server | 0.10.1 | 대화형 데이터 분석이 가능한 웹 기반 노트북 |
| zookeeper-server | 3.9.1-amzn-1 | 구성 정보 유지 관리, 이름 지정, 분산 동기화 제공 및 그룹 서비스 제공을 위한 중앙 집중식 서비스. |
| zookeeper-client | 3.9.1-amzn-1 | ZooKeeper 명령줄 클라이언트. |
## 7.2.0 구성 분류
구성 분류를 사용하면 애플리케이션을 사용자 지정할 수 있습니다. 이는 종종 `hive-site.xml`과 같이 애플리케이션의 구성 XML 파일에 해당합니다. 자세한 내용은 [애플리케이션 구성](emr-configure-apps.md) 단원을 참조하십시오.
재구성 작업은 실행 중인 클러스터의 인스턴스 그룹에 대한 구성을 지정할 때 수행됩니다. Amazon EMR은 사용자가 수정한 분류에 대한 재구성 작업만 시작합니다. 자세한 내용은 [실행 중인 클러스터에서 인스턴스 그룹 재구성](emr-configure-apps-running-cluster.md) 단원을 참조하십시오.
**emr-7.2.0 분류**
| 분류 | 설명 | 재구성 작업 |
| --- | --- | --- |
| capacity-scheduler | Hadoop capacity-scheduler.xml 파일에서 값을 변경합니다. | Restarts the ResourceManager service. |
| container-executor | Hadoop YARN container-executor.cfg 파일에서 값을 변경합니다. | Not available. |
| container-log4j | Hadoop YARN container-log4j.properties 파일에서 값을 변경합니다. | Not available. |
| core-site | Hadoop core-site.xml 파일에서 값을 변경합니다. | Restarts the Hadoop HDFS services Namenode, SecondaryNamenode, Datanode, ZKFC, and Journalnode. Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts Hadoop KMS, Ranger KMS, HiveServer2, Hive MetaStore, Hadoop Httpfs, and MapReduce-HistoryServer. |
| docker-conf | Docker 관련 설정을 변경합니다. | Not available. |
| emrfs-site | EMRFS 설정을 변경합니다. | Restarts the Hadoop HDFS services Namenode, SecondaryNamenode, Datanode, ZKFC, and Journalnode. Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts HBaseRegionserver, HBaseMaster, HBaseThrift, HBaseRest, HiveServer2, Hive MetaStore, Hadoop Httpfs, and MapReduce-HistoryServer. |
| flink-conf | flink-conf.yaml 설정을 변경합니다. | Restarts Flink history server. |
| flink-log4j | Flink log4j.properties 설정을 변경합니다. | Restarts Flink history server. |
| flink-log4j-session | Kubernetes 및 Yarn 세션에 대한 Flink log4j-session.properties 설정을 변경합니다. | Restarts Flink history server. |
| flink-log4j-cli | Flink log4j-cli.properties 설정을 변경합니다. | Restarts Flink history server. |
| hadoop-env | 모든 Hadoop 구성 요소에 대한 Hadoop 환경에서 값을 변경합니다. | Restarts the Hadoop HDFS services Namenode, SecondaryNamenode, Datanode, ZKFC, and Journalnode. Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts PhoenixQueryserver, HiveServer2, Hive MetaStore, and MapReduce-HistoryServer. |
| hadoop-log4j | Hadoop log4j.properties 파일에서 값을 변경합니다. | Restarts the Hadoop HDFS services SecondaryNamenode, Datanode, and Journalnode. Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts Hadoop KMS, Hadoop Httpfs, and MapReduce-HistoryServer. |
| hadoop-ssl-server | hadoop ssl 서버 구성을 변경합니다. | Not available. |
| hadoop-ssl-client | hadoop ssl 클라이언트 구성을 변경합니다. | Not available. |
| hbase | Apache HBase에 대한 Amazon EMR 큐레이트 설정입니다. | Custom EMR specific property. Sets emrfs-site and hbase-site configs. See those for their associated restarts. |
| hbase-env | HBase 환경에서 값을 변경합니다. | Restarts the HBase services RegionServer, HBaseMaster, ThriftServer, RestServer. |
| hbase-log4j | HBase hbase-log4j.properties 파일에서 값을 변경합니다. | Restarts the HBase services RegionServer, HBaseMaster, ThriftServer, RestServer. |
| hbase-metrics | HBase hadoop-metrics2-hbase.properties 파일에서 값을 변경합니다. | Restarts the HBase services RegionServer, HBaseMaster, ThriftServer, RestServer. |
| hbase-policy | HBase hbase-policy.xml 파일에서 값을 변경합니다. | Not available. |
| hbase-site | HBase hbase-site.xml 파일에서 값을 변경합니다. | Restarts the HBase services RegionServer, HBaseMaster, ThriftServer, RestServer. Additionally restarts Phoenix QueryServer. |
| hdfs-encryption-zones | HDFS 암호화 영역을 구성합니다. | This classification should not be reconfigured. |
| hdfs-env | HDFS 환경에서 값을 변경합니다. | Restarts Hadoop HDFS services Namenode, Datanode, and ZKFC. |
| hdfs-site | HDFS hdfs-site.xml에서 값을 변경합니다. | Restarts the Hadoop HDFS services Namenode, SecondaryNamenode, Datanode, ZKFC, and Journalnode. Additionally restarts Hadoop Httpfs. |
| hcatalog-env | HCatalog 환경에서 값을 변경합니다. | Restarts Hive HCatalog Server. |
| hcatalog-server-jndi | HCatalog jndi.properties 환경에서 값을 변경합니다. | Restarts Hive HCatalog Server. |
| hcatalog-server-proto-hive-site | HCatalog proto-hive-site.xml에서 값을 변경합니다. | Restarts Hive HCatalog Server. |
| hcatalog-webhcat-env | HCatalog WebHCat 환경에서 값을 변경합니다. | Restarts Hive WebHCat server. |
| hcatalog-webhcat-log4j2 | HCatalog WebHCat log4j2.properties에서 값을 변경합니다. | Restarts Hive WebHCat server. |
| hcatalog-webhcat-site | HCatalog WebHCat webhcat-site.xml 파일에서 값을 변경합니다. | Restarts Hive WebHCat server. |
| hive | Apache Hive에 대한 Amazon EMR 큐레이트 설정입니다. | Sets configurations to launch Hive LLAP service. |
| hive-beeline-log4j2 | Hive beeline-log4j2.properties 파일에서 값을 변경합니다. | Not available. |
| hive-parquet-logging | Hive parquet-logging.properties 파일에서 값을 변경합니다. | Not available. |
| hive-env | Hive 환경에서 값을 변경합니다. | Restarts HiveServer2, HiveMetastore, and Hive HCatalog-Server. Runs Hive schemaTool CLI commands to verify hive-metastore. |
| hive-exec-log4j2 | Hive hive-exec-log4j2.properties 파일에서 값을 변경합니다. | Not available. |
| hive-llap-daemon-log4j2 | Hive llap-daemon-log4j2.properties 파일에서 값을 변경합니다. | Not available. |
| hive-log4j2 | Hive hive-log4j2.properties 파일에서 값을 변경합니다. | Not available. |
| hive-site | Hive hive-site.xml 파일에서 값을 변경합니다. | Restarts HiveServer2, HiveMetastore, and Hive HCatalog-Server. Runs Hive schemaTool CLI commands to verify hive-metastore. Also restarts Oozie and Zeppelin. |
| hiveserver2-site | Hive Server2 hiveserver2-site.xml 파일에서 값을 변경합니다. | Not available. |
| hue-ini | Hue ini 파일에서 값을 변경합니다. | Restarts Hue. Also activates Hue config override CLI commands to pick up new configurations. |
| httpfs-env | HTTPFS 환경에서 값을 변경합니다. | Restarts Hadoop Httpfs service. |
| httpfs-site | Hadoop httpfs-site.xml 파일에서 값을 변경합니다. | Restarts Hadoop Httpfs service. |
| hadoop-kms-acls | Hadoop kms-acls.xml 파일에서 값을 변경합니다. | Not available. |
| hadoop-kms-env | Hadoop KMS 환경에서 값을 변경합니다. | Restarts Hadoop-KMS service. |
| hadoop-kms-java-home | Hadoop의 KMS java 홈 변경 | Not available. |
| hadoop-kms-log4j | Hadoop kms-log4j.properties 파일에서 값을 변경합니다. | Not available. |
| hadoop-kms-site | Hadoop kms-site.xml 파일에서 값을 변경합니다. | Restarts Hadoop-KMS and Ranger-KMS service. |
| hudi-env | Hudi 환경에서 값을 변경합니다. | Not available. |
| hudi-defaults | Hudi hudi-defaults.conf 파일에서 값을 변경합니다. | Not available. |
| iceberg-defaults | Iceberg iceberg-defaults.conf 파일에서 값을 변경합니다. | Not available. |
| delta-defaults | Delta delta-defaults.conf 파일에서 값을 변경합니다. | Not available. |
| jupyter-notebook-conf | Jupyter Notebook jupyter\$1notebook\$1config.py 파일에서 값을 변경합니다. | Not available. |
| jupyter-hub-conf | JupyterHubs jupyterhub\$1config.py 파일에서 값을 변경합니다. | Not available. |
| jupyter-s3-conf | Jupyter Notebook S3 지속성 구성 | Not available. |
| jupyter-sparkmagic-conf | Sparkmagic config.json 파일에서 값을 변경합니다. | Not available. |
| livy-conf | Livy livy.conf 파일에서 값을 변경합니다. | Restarts Livy Server. |
| livy-env | Livy 환경에서 값을 변경합니다. | Restarts Livy Server. |
| livy-log4j2 | Livy log4j2.properties 설정을 변경합니다. | Restarts Livy Server. |
| mapred-env | MapReduce 애플리케이션 환경에서 값을 변경합니다. | Restarts Hadoop MapReduce-HistoryServer. |
| mapred-site | MapReduce 애플리케이션 mapred-site.xml 파일에서 값을 변경합니다. | Restarts Hadoop MapReduce-HistoryServer. |
| oozie-env | Oozie 환경에서 값을 변경합니다. | Restarts Oozie. |
| oozie-log4j | Oozie oozie-log4j.properties 파일에서 값을 변경합니다. | Restarts Oozie. |
| oozie-site | Oozie oozie-site.xml 파일에서 값을 변경합니다. | Restarts Oozie. |
| phoenix-hbase-metrics | Phoenix hadoop-metrics2-hbase.properties 파일에서 값을 변경합니다. | Not available. |
| phoenix-hbase-site | Phoenix hbase-site.xml 파일에서 값을 변경합니다. | Not available. |
| phoenix-log4j | Phoenix log4j.properties 파일에서 값을 변경합니다. | Restarts Phoenix-QueryServer. |
| phoenix-metrics | Phoenix hadoop-metrics2-phoenix.properties 파일에서 값을 변경합니다. | Not available. |
| pig-env | Pig 환경에서 값을 변경합니다. | Not available. |
| pig-properties | Pig pig.properties 파일에서 값을 변경합니다. | Restarts Oozie. |
| pig-log4j | Pig log4j.properties 파일에서 값을 변경합니다. | Not available. |
| presto-log | Presto log.properties 파일에서 값을 변경합니다. | Restarts Presto-Server (for PrestoDB) |
| presto-config | Presto config.properties 파일에서 값을 변경합니다. | Restarts Presto-Server (for PrestoDB) |
| presto-password-authenticator | Presto password-authenticator.properties 파일에서 값을 변경합니다. | Not available. |
| presto-env | Presto presto-env.sh 파일에서 값을 변경합니다. | Restarts Presto-Server (for PrestoDB) |
| presto-node | Presto node.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-blackhole | Presto blackhole.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-cassandra | Presto cassandra.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-hive | Presto hive.properties 파일에서 값을 변경합니다. | Restarts Presto-Server (for PrestoDB) |
| presto-connector-jmx | Presto jmx.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-kafka | Presto kafka.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-lakeformation | Presto lakeformation.properties 파일에서 값을 변경합니다. | Restarts Presto-Server (for PrestoDB) |
| presto-connector-localfile | Presto localfile.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-memory | Presto memory.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-mongodb | Presto mongodb.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-mysql | Presto mysql.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-postgresql | Presto postgresql.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-raptor | Presto raptor.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-redis | Presto redis.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-redshift | Presto redshift.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-tpch | Presto tpch.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-tpcds | Presto tpcds.properties 파일에서 값을 변경합니다. | Not available. |
| trino-log | Trino log.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-config | Trino config.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-password-authenticator | Trino password-authenticator.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-env | Trino trino-env.sh 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-node | Trino node.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-blackhole | Trino blackhole.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-cassandra | Trino cassandra.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-delta | Trino delta.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-connector-hive | Trino hive.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-exchange-manager | Trino exchange-manager.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-connector-iceberg | Trino iceberg.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-connector-hudi | Trino hudi.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-connector-jmx | Trino jmx.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-kafka | Trino kafka.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-localfile | Trino localfile.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-memory | Trino memory.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-mongodb | Trino mongodb.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-mysql | Trino mysql.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-postgresql | Trino postgresql.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-raptor | Trino raptor.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-redis | Trino redis.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-redshift | Trino redshift.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-tpch | Trino tpch.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-tpcds | Trino tpcds.properties 파일에서 값을 변경합니다. | Not available. |
| ranger-kms-dbks-site | Ranger KMS dbks-site.xml 파일에서 값을 변경합니다. | Restarts Ranger KMS Server. |
| ranger-kms-site | Ranger KMS ranger-kms-site.xml 파일에서 값을 변경합니다. | Restarts Ranger KMS Server. |
| ranger-kms-env | Ranger KMS 환경에서 값을 변경합니다. | Restarts Ranger KMS Server. |
| ranger-kms-logback | Ranger KMS kms-logback.xml 파일에서 값을 변경합니다. | Not available. |
| ranger-kms-db-ca | Ranger KMS와의 MySQL SSL 연결에서 CA 파일의 값을 변경합니다. | Not available. |
| spark | Apache Spark에 대한 Amazon EMR 큐레이트 설정입니다. | This property modifies spark-defaults. See actions there. |
| spark-defaults | Spark spark-defaults.conf 파일에서 값을 변경합니다. | Restarts Spark history server and Spark thrift server. |
| spark-env | Spark 환경에서 값을 변경합니다. | Restarts Spark history server and Spark thrift server. |
| spark-hive-site | Spark hive-site.xml 파일에서 값을 변경합니다. | Not available. |
| spark-log4j2 | Spark log4j2.properties 파일에서 값을 변경합니다. | Restarts Spark history server and Spark thrift server. |
| spark-metrics | Spark metrics.properties 파일에서 값을 변경합니다. | Restarts Spark history server and Spark thrift server. |
| sqoop-env | Sqoop 환경에서 값을 변경합니다. | Not available. |
| sqoop-oraoop-site | Sqoop OraOop oraoop-site.xml 파일에서 값을 변경합니다. | Not available. |
| sqoop-site | Sqoop sqoop-site.xml 파일에서 값을 변경합니다. | Not available. |
| tez-site | Tez tez-site.xml 파일에서 값을 변경합니다. | Restart Oozie and HiveServer2. |
| yarn-env | YARN 환경에서 값을 변경합니다. | Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts MapReduce-HistoryServer. |
| yarn-site | YARN yarn-site.xml 파일에서 값을 변경합니다. | Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts Livy Server and MapReduce-HistoryServer. |
| zeppelin-env | Zeppelin 환경에서 값을 변경합니다. | Restarts Zeppelin. |
| zeppelin-site | zeppelin-site.xml에서 구성 설정을 변경합니다. | Restarts Zeppelin. |
| zookeeper-config | ZooKeeper zoo.cfg 파일에서 값을 변경합니다. | Restarts Zookeeper server. |
| zookeeper-logback | ZooKeeper logback.xml 파일에서 값을 변경합니다. | Restarts Zookeeper server. |
| emr-metrics | 이 노드에 대한 emr 지표 설정을 변경합니다. | Restarts the CloudWatchAgent service. |
## 7.2.0 변경 로그
**7.2.0 릴리스 및 릴리스 정보에 대한 변경 로그**
| Date | 이벤트 | 설명 |
| --- | --- | --- |
| 2025-09-03 | 문서 개정 | Amazon EMR 7.2.0 릴리스 정보 추가됨 |
| 2024-07-25 | 문서 게시 | Amazon EMR 7.2.0 릴리스 정보 최초 게시됨 |
| 2024-07-16 | 초기 릴리스 | 최초 상용 리전에 Amazon EMR 7.2.0 최초 배포됨 |
# Amazon EMR 릴리스 7.1.0
## 7.1.0 애플리케이션 버전
이 릴리스에서 지원되는 애플리케이션은 [https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Install-CloudWatch-Agent.html](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Install-CloudWatch-Agent.html), [https://delta.io/](https://delta.io/), [https://flink.apache.org/](https://flink.apache.org/), [http://hbase.apache.org/](http://hbase.apache.org/), [https://cwiki.apache.org/confluence/display/Hive/HCatalog](https://cwiki.apache.org/confluence/display/Hive/HCatalog), [http://hadoop.apache.org/docs/current/](http://hadoop.apache.org/docs/current/), [http://hive.apache.org/](http://hive.apache.org/), [https://hudi.apache.org](https://hudi.apache.org), [http://gethue.com/](http://gethue.com/), [https://iceberg.apache.org/](https://iceberg.apache.org/), [https://jupyter-enterprise-gateway.readthedocs.io/en/latest/](https://jupyter-enterprise-gateway.readthedocs.io/en/latest/), [https://jupyterhub.readthedocs.io/en/latest/#](https://jupyterhub.readthedocs.io/en/latest/#), [https://livy.incubator.apache.org/](https://livy.incubator.apache.org/), [https://mxnet.incubator.apache.org/](https://mxnet.incubator.apache.org/), [http://oozie.apache.org/](http://oozie.apache.org/), [https://phoenix.apache.org/](https://phoenix.apache.org/), [http://pig.apache.org/](http://pig.apache.org/), [https://prestodb.io/](https://prestodb.io/), [https://spark.apache.org/docs/latest/](https://spark.apache.org/docs/latest/), [http://sqoop.apache.org/](http://sqoop.apache.org/), [https://www.tensorflow.org/](https://www.tensorflow.org/), [https://tez.apache.org/](https://tez.apache.org/), [https://trino.io/](https://trino.io/), [https://zeppelin.incubator.apache.org/](https://zeppelin.incubator.apache.org/), [https://zookeeper.apache.org](https://zookeeper.apache.org)입니다.
아래 테이블에는 이번 Amazon EMR 릴리스에서 사용할 수 있는 애플리케이션 버전과 이전 세 가지 Amazon EMR 릴리스(해당하는 경우)의 애플리케이션 버전이 나와 있습니다.
각 Amazon EMR 릴리스에서 애플리케이션 버전의 전체 기록은 다음 주제를 참조하세요.
+ [Amazon EMR 7.x 릴리스의 애플리케이션 버전](emr-release-app-versions-7.x.md)
+ [Amazon EMR 6.x 릴리스의 애플리케이션 버전](emr-release-app-versions-6.x.md)
+ [Amazon EMR 5.x 릴리스의 애플리케이션 버전](emr-release-app-versions-5.x.md)
+ [Amazon EMR 4.x 릴리스의 애플리케이션 버전](emr-release-app-versions-4.x.md)
**애플리케이션 버전 정보**
| | emr-7.3.0 | emr-7.2.0 | emr-7.1.0 | emr-7.0.0 |
| --- | --- | --- | --- | --- |
| AWS Java용 SDK | 2.25.70, 1.12.747 | 2.23.18, 1.12.705 | 2.23.18, 1.12.656 | 2.20.160-amzn-0, 1.12.569 |
| Python | 3.9, 3.11 | 3.9, 3.11 | 3.9, 3.11 | 3.9 |
| Scala | 2.12.18 | 2.12.17 | 2.12.17 | 2.12.17 |
| AmazonCloudWatchAgent | 1.300032.2-amzn-0 | 1.300032.2-amzn-0 | 1.300032.2-amzn-0 | 1.300031.1-amzn-0 |
| Delta | 3.2.0-amzn-0 | 3.1.0 | 3.0.0 | 3.0.0 |
| Flink | 1.18.1-amzn-2 | 1.18.1-amzn-1 | 1.18.1-amzn-0 | 1.18.0-amzn-0 |
| Ganglia | - | - | - | - |
| HBase | 2.4.17-amzn-7 | 2.4.17-amzn-6 | 2.4.17-amzn-5 | 2.4.17-amzn-4 |
| HCatalog | 3.1.3-amzn-12 | 3.1.3-amzn-11 | 3.1.3-amzn-10 | 3.1.3-amzn-9 |
| Hadoop | 3.3.6-amzn-5 | 3.3.6-amzn-4 | 3.3.6-amzn-3 | 3.3.6-amzn-2 |
| Hive | 3.1.3-amzn-12 | 3.1.3-amzn-11 | 3.1.3-amzn-10 | 3.1.3-amzn-9 |
| Hudi | 0.15.0-amzn-0 | 0.14.1-amzn-1 | 0.14.1-amzn-0 | 0.14.0-amzn-1 |
| Hue | 4.11.0 | 4.11.0 | 4.11.0 | 4.11.0 |
| Iceberg | 1.5.2-amzn-0 | 1.5.0-amzn-0 | 1.4.3-amzn-0 | 1.4.2-amzn-0 |
| JupyterEnterpriseGateway | 2.6.0 | 2.6.0 | 2.6.0 | 2.6.0 |
| JupyterHub | 1.5.0 | 1.5.0 | 1.5.0 | 1.5.0 |
| Livy | 0.8.0-incubating | 0.8.0-incubating | 0.8.0-incubating | 0.7.1-incubating |
| MXNet | - | 1.9.1 | 1.9.1 | 1.9.1 |
| Mahout | - | - | - | - |
| Oozie | 5.2.1 | 5.2.1 | 5.2.1 | 5.2.1 |
| Phoenix | 5.1.3 | 5.1.3 | 5.1.3 | 5.1.3 |
| Pig | 0.17.0 | 0.17.0 | 0.17.0 | 0.17.0 |
| Presto | 0.285-amzn-1 | 0.285-amzn-0 | 0.284-amzn-0 | 0.283-amzn-1 |
| Spark | 3.5.1-amzn-1 | 3.5.1-amzn-0 | 3.5.0-amzn-1 | 3.5.0-amzn-0 |
| Sqoop | 1.4.7 | 1.4.7 | 1.4.7 | 1.4.7 |
| TensorFlow | 2.16.1 | 2.11.0 | 2.11.0 | 2.11.0 |
| Tez | 0.10.2-amzn-10 | 0.10.2-amzn-9 | 0.10.2-amzn-8 | 0.10.2-amzn-7 |
| Trino (PrestoSQL) | 442-amzn-0 | 436-amzn-0 | 435-amzn-0 | 426-amzn-1 |
| Zeppelin | 0.11.1 | 0.10.1 | 0.10.1 | 0.10.1 |
| ZooKeeper | 3.9.1-amzn-1 | 3.9.1-amzn-1 | 3.9.1-amzn-0 | 3.5.10 |
## 7.1.0 릴리스 정보
다음 릴리스 정보에는 Amazon EMR 릴리스 7.1.0에 대한 정보가 포함됩니다. 변경 사항은 7.1.0에 관련됩니다.
**새로운 기능**
+ **애플리케이션 업그레이드** – Amazon EMR 7.1.0 application upgrades include Livy 0.8.0, Trino 435, and ZooKeeper 3.9.1.
+ [https://docs.aws.amazon.com/emr/latest/ManagementGuide/emr-plan-node-replacement.html](https://docs.aws.amazon.com/emr/latest/ManagementGuide/emr-plan-node-replacement.html) - Amazon EMR 7.1.0 이상에서는 비정상 노드 교체가 기본적으로 활성화되므로 Amazon EMR이 비정상 노드를 정상적으로 교체합니다. Amazon EMR 릴리스 7.0.0 이하의 기존 워크플로에 영향을 주지 않도록 클러스터에서 종료 방지를 활성화한 경우 비정상 노드 교체는 비활성화됩니다.
+ [https://docs.aws.amazon.com/emr/latest/ReleaseGuide/emr-AmazonCloudWatchAgent.html](https://docs.aws.amazon.com/emr/latest/ReleaseGuide/emr-AmazonCloudWatchAgent.html) - Amazon EMR 구성 API를 사용하여 추가 시스템 지표를 사용하고, 애플리케이션 지표를 추가하며, 지표 대상을 변경하도록 CloudWatch 에이전트를 구성합니다.
**알려진 문제**
+ 이 릴리스에서는 애플리케이션 JupyterEnterpriseGateway(JEG)가 Python 3.11을 지원하지 않습니다.
+ 노드에 스레드 및/또는 열린 파일 핸들이 많은 경우 인스턴스의 상태를 모니터링하는 클러스터 내 인스턴스 상태 스크립트는 CPU 및 메모리 리소스를 과도하게 소비할 수 있습니다.
**변경 사항, 향상된 기능 및 해결된 문제**
+ Spark 3.3.1(EMR 버전 6.10 이상에서 지원됨)부터 폐기 호스트의 모든 실행기는 *DECOMMISSIONING* 상태라는 새로운 `ExecutorState` 상태로 설정됩니다. Yarn은 폐기 중인 실행기를 사용하여 작업을 할당할 수 없으므로 필요한 경우 실행 중인 작업에 대해 새 실행기를 요청하세요. 따라서 EMR Managed Scaling, EMR Auto Scaling 또는 EMR-EC2 클러스터의 사용자 지정 조정 메커니즘을 사용하는 동안 Spark DRA를 비활성화하면 Yarn이 각 작업에 허용되는 최대 실행기를 요청할 수 있습니다. 이 문제를 방지하려면 위의 기능 조합을 사용할 때 `spark.dynamicAllocation.enabled` 속성을 `TRUE`(기본값)로 설정한 상태로 둡니다. 또한 Spark 작업의 `spark.dynamicAllocation.maxExecutors` 및 `spark.dynamicAllocation.minExecutors` 속성 값을 설정하여 작업 실행 중에 할당된 실행기 수를 제한하여 최소 및 최대 실행기 제약 조건을 설정할 수도 있습니다.
+ Amazon EMR 7.1.0은 기본적으로 Python 3.9를 지원하지만 Amazon EMR 7.1.0의 Livy 0.8.0 및 Spark는 Python 3.11을 지원합니다.
+ 이 릴리스에서는 PySpark를 Python 버전 3.11과 함께 사용할 때 한 번에 하나씩 각 줄을 실행해야 하던 문제를 수정합니다.
+ **Zeppelin 업그레이드** - Amazon EMR 7.1.0에는 Java v2용 AWS SDK로 Zeppelin 업그레이드가 포함되어 있습니다. 이 업그레이드를 통해 Zeppelin S3 노트북은 사용자 지정 암호화 구성 요소 제공업체를 수락할 수 있습니다. Java v2용 AWS SDK는 EncryptionMaterialsProvider 인터페이스를 제거합니다. Amazon EMR 7.1.0으로 업그레이드하는 경우 사용자 지정 암호화를 사용하려면 [Keyring 인터페이스](https://github.com/aws/amazon-s3-encryption-client-java/blob/main/src/main/java/software/amazon/encryption/s3/materials/Keyring.java)를 구현해야 합니다. 키링 인터페이스를 구현하는 방법의 예제는 [KmsKeyring.java](https://github.com/aws/amazon-s3-encryption-client-java/blob/a5d714fe27f97793997e41745939ef7da8a22167/src/main/java/software/amazon/encryption/s3/materials/KmsKeyring.java#L36)를 참조하세요.
+ Amazon EMR 릴리스 7.1.0으로 업그레이드하는 경우 AES/GCM/NoPadding 의 AES 알고리즘을 사용하여 키를 생성하도록 로컬 디스크 암호화에 대한 사용자 지정 키 제공업체를 변경합니다. 알고리즘을 업데이트하지 않으면 `Local disk encryption failed on master instance (i-123456789) due to internal error.` 오류와 함께 클러스터 생성이 실패할 수 있습니다. 사용자 지정 키 제공업체 생성에 대한 자세한 내용은 [사용자 지정 키 제공업체 생성](https://docs.aws.amazon.com/emr/latest/ManagementGuide/emr-encryption-enable.html#emr-custom-keys)을 참조하세요.
+ Amazon EMR 7.1.0은 파일 핸들이 열려 있는 파일에 대한 로그 잘림 로직을 개선하여 디스크 공간 부족 조건에서 노드의 복원력을 개선합니다.
+ 이 릴리스는 인코딩 및 디코딩 로직을 개선하여 노드를 재시작할 때 Amazon EMR 대몬의 읽기 및 쓰기 파일을 사용하여 데이터 손상 및 노드 실패 위험을 최소화합니다.
+ Amazon EMR 5.36 이상, 6.6 이상 또는 7.0 이상의 *최신 패치 릴리스*가 적용된 클러스터를 시작하는 경우 Amazon EMR은 기본 Amazon EMR AMI에 대한 최신 Amazon Linux 2023 or Amazon Linux 2 릴리스를 사용합니다. 자세한 내용은 [Amazon EMR에 대한 기본 Amazon Linux AMI 사용](https://docs.aws.amazon.com/emr/latest/ManagementGuide/emr-default-ami.html)을 참조하세요.
[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/ko_kr/emr/latest/ReleaseGuide/emr-710-release.html)
## 7.1.0 기본 Java 버전
Amazon EMR 릴리스 7.1 이상에서는 Apache Livy를 제외한 Corretto 17(JDK 17)을 지원하는 애플리케이션에 대해 기본적으로 Amazon Corretto 17(OpenJDK 기반)이 함께 제공됩니다.
다음 표에서는 Amazon EMR 7.1.0에 있는 애플리케이션의 기본 Java 버전을 확인할 수 있습니다. 클러스터의 기본 JVM을 변경하려면 클러스터에서 실행되는 각 애플리케이션에 대해 [특정 Java 가상 머신을 사용하도록 애플리케이션 구성](configuring-java8.md)의 지침을 따릅니다. 클러스터에서는 Java 런타임 버전 1개만 사용할 수 있습니다. Amazon EMR은 동일한 클러스터에서 다양한 런타임 버전을 사용해 서로 다른 노드 또는 애플리케이션을 실행하는 것을 지원하지 않습니다.
| 애플리케이션 | Java 및 Amazon Corretto 버전(기본값은 굵은체로 표시) |
| --- | --- |
| 델타 | 17, 11, 8 |
| Flink | 17, 11, 8 |
| HBase | 11, 8 |
| HCatalog | 17, 11, 8 |
| Hadoop | 17, 11, 8 |
| Hive | 17, 11, 8 |
| Hudi | 17, 11, 8 |
| Iceberg | 17, 11, 8 |
| Livy | 17, 11, 8 |
| Oozie | 17, 11, 8 |
| 피닉스 | 8 |
| PrestoDB | 8 |
| Spark | 17, 11, 8 |
| Spark RAPIDS | 17, 11, 8 |
| Sqoop | 8 |
| Tez의 Hive 실행 시간 비교 | 17, 11, 8 |
| Trino | 17 |
| Zeppelin | 8 |
| Pig | 8 |
| Zookeeper | 8 |
## 7.1.0 구성 요소 버전
이 릴리스를 통해 Amazon EMR이 설치하는 구성 요소는 다음과 같습니다. 일부는 빅 데이터 애플리케이션 패키지의 일부로 설치됩니다. 나머지는 Amazon EMR에 고유하며 시스템 프로세스 및 기능을 위해 설치됩니다. 이는 일반적으로 `emr` 또는 `aws`로 시작됩니다. 최근 Amazon EMR 릴리스의 빅 데이터 애플리케이션 패키지는 일반적으로 커뮤니티에서 발견된 최신 버전입니다. 가능한 한 빨리 Amazon EMR에서 커뮤니티 릴리스를 제공합니다.
Amazon EMR의 일부 구성 요소는 커뮤니티 버전과 다릅니다. 이러한 구성 요소에는 `CommunityVersion-amzn-EmrVersion` 양식의 버전 레이블이 있습니다. `EmrVersion`은 0에서 시작합니다. 예를 들어, 버전 2.2의 `myapp-component`라는 오픈 소스 커뮤니티 구성 요소가 다른 Amazon EMR 릴리스에 포함되도록 세 번 수정된 경우 해당 릴리스 버전은 `2.2-amzn-2`로 나열됩니다.
| 구성 요소 | 버전 | 설명 |
| --- | --- | --- |
| adot-java-agent | 1.31.0 | 애플리케이션 대몬(daemon)에서 지표를 수집하는 Java 에이전트입니다. |
| delta | 3.0.0 | Delta Lake는 방대한 분석 데이터 세트를 위한 오픈 테이블 형식입니다. |
| emr-amazon-cloudwatch-agent | 1.300032.2-amzn-0 | Amazon EC2 인스턴스에서 내부 시스템 수준 지표와 사용자 지정 애플리케이션 지표를 수집하는 애플리케이션입니다. |
| emr-ddb | 5.3.0 | 하둡 에코시스템 애플리케이션용 Amazon DynamoDB 커넥터 |
| emr-goodies | 3.10.0 | 편리한 하둡 에코시스템용 추가 라이브러리 |
| emr-kinesis | 3.14.0 | 하둡 에코시스템 애플리케이션용 Amazon Kinesis 커넥터. |
| emr-notebook-env | 1.7.0 | Jupyter Enterprise Gateway가 포함된 EMR 노트북용 Conda 환경 |
| emr-s3-dist-cp | 2.31.0 | Amazon S3용으로 최적화된 분사 복사 애플리케이션. |
| emr-s3-select | 2.10.0 | EMR S3Select 커넥터 |
| emr-wal-cli | 1.2.2 | emrwal 목록/삭제에 사용되는 CLI입니다. |
| emrfs | 2.62.0 | 하둡 에코시스템 애플리케이션용 Amazon S3 커넥터. |
| flink-client | 1.18.1-amzn-0 | Apache Flink 명령줄 클라이언트 스크립트 및 애플리케이션 |
| flink-jobmanager-config | 1.18.1-amzn-0 | Apache Flink JobManager에 대한 EMR 노드에서 리소스를 관리합니다. |
| hadoop-client | 3.3.6-amzn-3 | 'hdfs', 'hadoop', 'yarn' 등과 같은 하둡 명령줄 클라이언트 |
| hadoop-hdfs-datanode | 3.3.6-amzn-3 | 블록을 저장하는 HDFS 노드 수준 서비스 |
| hadoop-hdfs-library | 3.3.6-amzn-3 | HDFS 명령줄 클라이언트 및 라이브러리 |
| hadoop-hdfs-namenode | 3.3.6-amzn-3 | 파일 이름 및 블록 위치를 추적하는 HDFS 서비스 |
| hadoop-hdfs-journalnode | 3.3.6-amzn-3 | HA 클러스터에서 하둡 파일 시스템 저널을 관리하기 위한 HDFS 서비스 |
| hadoop-httpfs-server | 3.3.6-amzn-3 | HDFS 작업에 대한 HTTP 엔드포인트 |
| hadoop-kms-server | 3.3.6-amzn-3 | 하둡의 KeyProvider API를 기반으로 하는 암호화 키 관리 서버 |
| hadoop-mapred | 3.3.6-amzn-3 | MapReduce 애플리케이션을 실행하는 MapReduce 실행 엔진 라이브러리 |
| hadoop-yarn-nodemanager | 3.3.6-amzn-3 | 개별 노드의 컨테이너를 관리하는 YARN 서비스 |
| hadoop-yarn-resourcemanager | 3.3.6-amzn-3 | 클러스터 리소스 및 분산 애플리케이션을 할당 및 관리하는 YARN 서비스 |
| hadoop-yarn-timeline-server | 3.3.6-amzn-3 | YARN 애플리케이션의 현재 및 기록 정보를 가져오는 서비스 |
| hbase-hmaster | 2.4.17-amzn-5 | 리전 조정 및 관리 명령의 실행을 담당하는 HBase 클러스터용 서비스 |
| hbase-region-server | 2.4.17-amzn-5 | 한 개 이상의 HBase 리전에 서비스를 제공하는 서비스 |
| hbase-client | 2.4.17-amzn-5 | HBase 명령줄 클라이언트 |
| hbase-rest-server | 2.4.17-amzn-5 | HBase용 RESTful HTTP 엔드포인트를 제공하는 서비스 |
| hbase-thrift-server | 2.4.17-amzn-5 | HBase에 Thrift 엔드포인트를 제공하는 서비스 |
| hbase-operator-tools | 2.4.17-amzn-5 | Apache HBase 클러스터용 복구 도구. |
| hcatalog-client | 3.1.3-amzn-10 | hcatalog-server를 조정하기 위한 'hcat' 명령줄 클라이언트 |
| hcatalog-server | 3.1.3-amzn-10 | 분산 애플리케이션용 스토리지 관리 계층, 테이블 및 HCatalog를 제공하는 서비스 |
| hcatalog-webhcat-server | 3.1.3-amzn-10 | HCatalog에 REST 인터페이스를 제공하는 HTTP 엔드포인트 |
| hive-client | 3.1.3-amzn-10 | Hive 명령줄 클라이언트 |
| hive-hbase | 3.1.3-amzn-10 | Hive-hbase 클라이언트 |
| hive-metastore-server | 3.1.3-amzn-10 | 하둡 작업에 대한 SQL용 메타데이터가 저장되는 시맨틱 리포지토리인 Hive 메타스토어에 액세스하기 위한 서비스 |
| hive-server2 | 3.1.3-amzn-10 | Hive 쿼리를 웹 요청으로 수락하기 위한 서비스 |
| hudi | 0.14.1-amzn-0 | 짧은 지연 시간 및 높은 효율성으로 데이터 파이프라인을 구동하는 증분 처리 프레임워크. |
| hudi-presto | 0.14.1-amzn-0 | Hudi로 Presto를 실행하기 위한 번들 라이브러리. |
| hudi-trino | 0.14.1-amzn-0 | Hudi와 함께 Trnio를 실행하기 위한 번들 라이브러리. |
| hudi-spark | 0.14.1-amzn-0 | Hudi와 함께 Spark를 실행하기 위한 번들 라이브러리. |
| hue-server | 4.11.0 | 하둡 에코시스템 애플리케이션을 사용하여 데이터를 분석하는 웹 애플리케이션. |
| iceberg | 1.4.3-amzn-0 | Apache Iceberg는 방대한 분석 데이터 세트를 위한 오픈 테이블 형식입니다. |
| jupyterhub | 1.5.0 | Jupyter Notebook용 다중 사용자 서버 |
| livy-server | 0.8.0-incubating | Apache Spark와 상호작용하기 위한 REST 인터페이스 |
| nginx | 1.12.1 | HTTP인 nginx [engine x] 및 역방향 프록시 서버 |
| mxnet | 1.9.1 | 유연성, 확장성 및 효율성이 뛰어난 딥 러닝용 라이브러리. |
| mariadb-server | 5.5.68 이상 | MariaDB 데이터베이스 서버. |
| nvidia-cuda | 11.8.0 | Nvidia 드라이버와 Cuda 도구 키트 |
| oozie-client | 5.2.1 | Oozie 명령줄 클라이언트 |
| oozie-server | 5.2.1 | Oozie 워크플로 요청을 수락하는 서비스 |
| opencv | 4.7.0 | 오픈 소스 컴퓨터 비전 라이브러리. |
| phoenix-library | 5.1.3 | 서버 및 클라이언트의 phoenix 라이브러리 |
| phoenix-connectors | 5.1.3 | Spark-3용 Apache Phoenix 커넥터 |
| phoenix-query-server | 6.0.0 | Avatica API에 대한 JSON 형식 액세스 및 프로토콜 버퍼 액세스를 비롯하여 JDBC 액세스를 제공하는 경량 서버 |
| presto-coordinator | 0.284-amzn-0 | presto-worker의 쿼리를 수락하고 쿼리 실행을 관리하는 서비스. |
| presto-worker | 0.284-amzn-0 | 여러 쿼리를 실행하는 서비스. |
| presto-client | 0.284-amzn-0 | Presto 서버가 시작되지 않은 HA 클러스터의 대기 마스터에 설치된 Presto 명령줄 클라이언트. |
| trino-coordinator | 435-amzn-0 | trino-workers의 쿼리를 수락하고 쿼리 실행을 관리하는 서비스. |
| trino-worker | 435-amzn-0 | 여러 쿼리를 실행하는 서비스. |
| trino-client | 435-amzn-0 | Trino 서버가 시작되지 않은 HA 클러스터의 대기 마스터에 설치된 Trino 명령줄 클라이언트. |
| pig-client | 0.17.0 | Pig 명령줄 클라이언트. |
| r | 4.3.2 | 통계 컴퓨팅용 R 프로젝트 |
| ranger-kms-server | 2.0.0 | Apache Ranger 키 관리 시스템 |
| spark-client | 3.5.0-amzn-1 | Spark 명령줄 클라이언트. |
| spark-history-server | 3.5.0-amzn-1 | 완료된 Spark 애플리케이션의 수명에 대해 기록된 이벤트를 조회하는 웹 UI. |
| spark-on-yarn | 3.5.0-amzn-1 | YARN용 인 메모리 실행 엔진. |
| spark-yarn-slave | 3.5.0-amzn-1 | YARN 슬레이브에서 필요한 Apache Spark 라이브러리. |
| spark-rapids | 23.10.0-amzn-1 | GPU로 Apache Spark를 가속화하는 Nvidia Spark RAPIDS 플러그인. |
| sqoop-client | 1.4.7 | Apache Sqoop 명령줄 클라이언트. |
| tensorflow | 2.11.0 | TensorFlow는 고성능 수치 계산용 오픈 소스 소프트웨어 라이브러리입니다. |
| tez-on-yarn | 0.10.2-amzn-8 | tez YARN 애플리케이션 및 라이브러리. |
| tez-on-worker | 0.10.2-amzn-8 | 워커 노드에 대한 tez YARN 애플리케이션 및 라이브러리. |
| zeppelin-server | 0.10.1 | 대화형 데이터 분석이 가능한 웹 기반 노트북 |
| zookeeper-server | 3.9.1-amzn-0 | 구성 정보 유지 관리, 이름 지정, 분산 동기화 제공 및 그룹 서비스 제공을 위한 중앙 집중식 서비스. |
| zookeeper-client | 3.9.1-amzn-0 | ZooKeeper 명령줄 클라이언트. |
## 7.1.0 구성 분류
구성 분류를 사용하면 애플리케이션을 사용자 지정할 수 있습니다. 이는 종종 `hive-site.xml`과 같이 애플리케이션의 구성 XML 파일에 해당합니다. 자세한 내용은 [애플리케이션 구성](emr-configure-apps.md) 단원을 참조하십시오.
재구성 작업은 실행 중인 클러스터의 인스턴스 그룹에 대한 구성을 지정할 때 수행됩니다. Amazon EMR은 사용자가 수정한 분류에 대한 재구성 작업만 시작합니다. 자세한 내용은 [실행 중인 클러스터에서 인스턴스 그룹 재구성](emr-configure-apps-running-cluster.md) 단원을 참조하십시오.
**emr-7.1.0 분류**
| 분류 | 설명 | 재구성 작업 |
| --- | --- | --- |
| capacity-scheduler | Hadoop capacity-scheduler.xml 파일에서 값을 변경합니다. | Restarts the ResourceManager service. |
| container-executor | Hadoop YARN container-executor.cfg 파일에서 값을 변경합니다. | Not available. |
| container-log4j | Hadoop YARN container-log4j.properties 파일에서 값을 변경합니다. | Not available. |
| core-site | Hadoop core-site.xml 파일에서 값을 변경합니다. | Restarts the Hadoop HDFS services Namenode, SecondaryNamenode, Datanode, ZKFC, and Journalnode. Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts Hadoop KMS, Ranger KMS, HiveServer2, Hive MetaStore, Hadoop Httpfs, and MapReduce-HistoryServer. |
| docker-conf | Docker 관련 설정을 변경합니다. | Not available. |
| emrfs-site | EMRFS 설정을 변경합니다. | Restarts the Hadoop HDFS services Namenode, SecondaryNamenode, Datanode, ZKFC, and Journalnode. Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts HBaseRegionserver, HBaseMaster, HBaseThrift, HBaseRest, HiveServer2, Hive MetaStore, Hadoop Httpfs, and MapReduce-HistoryServer. |
| flink-conf | flink-conf.yaml 설정을 변경합니다. | Restarts Flink history server. |
| flink-log4j | Flink log4j.properties 설정을 변경합니다. | Restarts Flink history server. |
| flink-log4j-session | Kubernetes 및 Yarn 세션에 대한 Flink log4j-session.properties 설정을 변경합니다. | Restarts Flink history server. |
| flink-log4j-cli | Flink log4j-cli.properties 설정을 변경합니다. | Restarts Flink history server. |
| hadoop-env | 모든 Hadoop 구성 요소에 대한 Hadoop 환경에서 값을 변경합니다. | Restarts the Hadoop HDFS services Namenode, SecondaryNamenode, Datanode, ZKFC, and Journalnode. Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts PhoenixQueryserver, HiveServer2, Hive MetaStore, and MapReduce-HistoryServer. |
| hadoop-log4j | Hadoop log4j.properties 파일에서 값을 변경합니다. | Restarts the Hadoop HDFS services SecondaryNamenode, Datanode, and Journalnode. Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts Hadoop KMS, Hadoop Httpfs, and MapReduce-HistoryServer. |
| hadoop-ssl-server | hadoop ssl 서버 구성을 변경합니다. | Not available. |
| hadoop-ssl-client | hadoop ssl 클라이언트 구성을 변경합니다. | Not available. |
| hbase | Apache HBase에 대한 Amazon EMR 큐레이트 설정입니다. | Custom EMR specific property. Sets emrfs-site and hbase-site configs. See those for their associated restarts. |
| hbase-env | HBase 환경에서 값을 변경합니다. | Restarts the HBase services RegionServer, HBaseMaster, ThriftServer, RestServer. |
| hbase-log4j | HBase hbase-log4j.properties 파일에서 값을 변경합니다. | Restarts the HBase services RegionServer, HBaseMaster, ThriftServer, RestServer. |
| hbase-metrics | HBase hadoop-metrics2-hbase.properties 파일에서 값을 변경합니다. | Restarts the HBase services RegionServer, HBaseMaster, ThriftServer, RestServer. |
| hbase-policy | HBase hbase-policy.xml 파일에서 값을 변경합니다. | Not available. |
| hbase-site | HBase hbase-site.xml 파일에서 값을 변경합니다. | Restarts the HBase services RegionServer, HBaseMaster, ThriftServer, RestServer. Additionally restarts Phoenix QueryServer. |
| hdfs-encryption-zones | HDFS 암호화 영역을 구성합니다. | This classification should not be reconfigured. |
| hdfs-env | HDFS 환경에서 값을 변경합니다. | Restarts Hadoop HDFS services Namenode, Datanode, and ZKFC. |
| hdfs-site | HDFS hdfs-site.xml에서 값을 변경합니다. | Restarts the Hadoop HDFS services Namenode, SecondaryNamenode, Datanode, ZKFC, and Journalnode. Additionally restarts Hadoop Httpfs. |
| hcatalog-env | HCatalog 환경에서 값을 변경합니다. | Restarts Hive HCatalog Server. |
| hcatalog-server-jndi | HCatalog jndi.properties 환경에서 값을 변경합니다. | Restarts Hive HCatalog Server. |
| hcatalog-server-proto-hive-site | HCatalog proto-hive-site.xml에서 값을 변경합니다. | Restarts Hive HCatalog Server. |
| hcatalog-webhcat-env | HCatalog WebHCat 환경에서 값을 변경합니다. | Restarts Hive WebHCat server. |
| hcatalog-webhcat-log4j2 | HCatalog WebHCat log4j2.properties에서 값을 변경합니다. | Restarts Hive WebHCat server. |
| hcatalog-webhcat-site | HCatalog WebHCat webhcat-site.xml 파일에서 값을 변경합니다. | Restarts Hive WebHCat server. |
| hive | Apache Hive에 대한 Amazon EMR 큐레이트 설정입니다. | Sets configurations to launch Hive LLAP service. |
| hive-beeline-log4j2 | Hive beeline-log4j2.properties 파일에서 값을 변경합니다. | Not available. |
| hive-parquet-logging | Hive parquet-logging.properties 파일에서 값을 변경합니다. | Not available. |
| hive-env | Hive 환경에서 값을 변경합니다. | Restarts HiveServer2, HiveMetastore, and Hive HCatalog-Server. Runs Hive schemaTool CLI commands to verify hive-metastore. |
| hive-exec-log4j2 | Hive hive-exec-log4j2.properties 파일에서 값을 변경합니다. | Not available. |
| hive-llap-daemon-log4j2 | Hive llap-daemon-log4j2.properties 파일에서 값을 변경합니다. | Not available. |
| hive-log4j2 | Hive hive-log4j2.properties 파일에서 값을 변경합니다. | Not available. |
| hive-site | Hive hive-site.xml 파일에서 값을 변경합니다. | Restarts HiveServer2, HiveMetastore, and Hive HCatalog-Server. Runs Hive schemaTool CLI commands to verify hive-metastore. Also restarts Oozie and Zeppelin. |
| hiveserver2-site | Hive Server2 hiveserver2-site.xml 파일에서 값을 변경합니다. | Not available. |
| hue-ini | Hue ini 파일에서 값을 변경합니다. | Restarts Hue. Also activates Hue config override CLI commands to pick up new configurations. |
| httpfs-env | HTTPFS 환경에서 값을 변경합니다. | Restarts Hadoop Httpfs service. |
| httpfs-site | Hadoop httpfs-site.xml 파일에서 값을 변경합니다. | Restarts Hadoop Httpfs service. |
| hadoop-kms-acls | Hadoop kms-acls.xml 파일에서 값을 변경합니다. | Not available. |
| hadoop-kms-env | Hadoop KMS 환경에서 값을 변경합니다. | Restarts Hadoop-KMS service. |
| hadoop-kms-java-home | Hadoop의 KMS java 홈 변경 | Not available. |
| hadoop-kms-log4j | Hadoop kms-log4j.properties 파일에서 값을 변경합니다. | Not available. |
| hadoop-kms-site | Hadoop kms-site.xml 파일에서 값을 변경합니다. | Restarts Hadoop-KMS and Ranger-KMS service. |
| hudi-env | Hudi 환경에서 값을 변경합니다. | Not available. |
| hudi-defaults | Hudi hudi-defaults.conf 파일에서 값을 변경합니다. | Not available. |
| iceberg-defaults | Iceberg iceberg-defaults.conf 파일에서 값을 변경합니다. | Not available. |
| delta-defaults | Delta delta-defaults.conf 파일에서 값을 변경합니다. | Not available. |
| jupyter-notebook-conf | Jupyter Notebook jupyter\$1notebook\$1config.py 파일에서 값을 변경합니다. | Not available. |
| jupyter-hub-conf | JupyterHubs jupyterhub\$1config.py 파일에서 값을 변경합니다. | Not available. |
| jupyter-s3-conf | Jupyter Notebook S3 지속성 구성 | Not available. |
| jupyter-sparkmagic-conf | Sparkmagic config.json 파일에서 값을 변경합니다. | Not available. |
| livy-conf | Livy livy.conf 파일에서 값을 변경합니다. | Restarts Livy Server. |
| livy-env | Livy 환경에서 값을 변경합니다. | Restarts Livy Server. |
| livy-log4j2 | Livy log4j2.properties 설정을 변경합니다. | Restarts Livy Server. |
| mapred-env | MapReduce 애플리케이션 환경에서 값을 변경합니다. | Restarts Hadoop MapReduce-HistoryServer. |
| mapred-site | MapReduce 애플리케이션 mapred-site.xml 파일에서 값을 변경합니다. | Restarts Hadoop MapReduce-HistoryServer. |
| oozie-env | Oozie 환경에서 값을 변경합니다. | Restarts Oozie. |
| oozie-log4j | Oozie oozie-log4j.properties 파일에서 값을 변경합니다. | Restarts Oozie. |
| oozie-site | Oozie oozie-site.xml 파일에서 값을 변경합니다. | Restarts Oozie. |
| phoenix-hbase-metrics | Phoenix hadoop-metrics2-hbase.properties 파일에서 값을 변경합니다. | Not available. |
| phoenix-hbase-site | Phoenix hbase-site.xml 파일에서 값을 변경합니다. | Not available. |
| phoenix-log4j | Phoenix log4j.properties 파일에서 값을 변경합니다. | Restarts Phoenix-QueryServer. |
| phoenix-metrics | Phoenix hadoop-metrics2-phoenix.properties 파일에서 값을 변경합니다. | Not available. |
| pig-env | Pig 환경에서 값을 변경합니다. | Not available. |
| pig-properties | Pig pig.properties 파일에서 값을 변경합니다. | Restarts Oozie. |
| pig-log4j | Pig log4j.properties 파일에서 값을 변경합니다. | Not available. |
| presto-log | Presto log.properties 파일에서 값을 변경합니다. | Restarts Presto-Server (for PrestoDB) |
| presto-config | Presto config.properties 파일에서 값을 변경합니다. | Restarts Presto-Server (for PrestoDB) |
| presto-password-authenticator | Presto password-authenticator.properties 파일에서 값을 변경합니다. | Not available. |
| presto-env | Presto presto-env.sh 파일에서 값을 변경합니다. | Restarts Presto-Server (for PrestoDB) |
| presto-node | Presto node.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-blackhole | Presto blackhole.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-cassandra | Presto cassandra.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-hive | Presto hive.properties 파일에서 값을 변경합니다. | Restarts Presto-Server (for PrestoDB) |
| presto-connector-jmx | Presto jmx.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-kafka | Presto kafka.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-lakeformation | Presto lakeformation.properties 파일에서 값을 변경합니다. | Restarts Presto-Server (for PrestoDB) |
| presto-connector-localfile | Presto localfile.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-memory | Presto memory.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-mongodb | Presto mongodb.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-mysql | Presto mysql.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-postgresql | Presto postgresql.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-raptor | Presto raptor.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-redis | Presto redis.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-redshift | Presto redshift.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-tpch | Presto tpch.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-tpcds | Presto tpcds.properties 파일에서 값을 변경합니다. | Not available. |
| trino-log | Trino log.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-config | Trino config.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-password-authenticator | Trino password-authenticator.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-env | Trino trino-env.sh 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-node | Trino node.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-blackhole | Trino blackhole.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-cassandra | Trino cassandra.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-delta | Trino delta.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-connector-hive | Trino hive.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-exchange-manager | Trino exchange-manager.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-connector-iceberg | Trino iceberg.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-connector-hudi | Trino hudi.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-connector-jmx | Trino jmx.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-kafka | Trino kafka.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-localfile | Trino localfile.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-memory | Trino memory.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-mongodb | Trino mongodb.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-mysql | Trino mysql.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-postgresql | Trino postgresql.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-raptor | Trino raptor.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-redis | Trino redis.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-redshift | Trino redshift.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-tpch | Trino tpch.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-tpcds | Trino tpcds.properties 파일에서 값을 변경합니다. | Not available. |
| ranger-kms-dbks-site | Ranger KMS dbks-site.xml 파일에서 값을 변경합니다. | Restarts Ranger KMS Server. |
| ranger-kms-site | Ranger KMS ranger-kms-site.xml 파일에서 값을 변경합니다. | Restarts Ranger KMS Server. |
| ranger-kms-env | Ranger KMS 환경에서 값을 변경합니다. | Restarts Ranger KMS Server. |
| ranger-kms-logback | Ranger KMS kms-logback.xml 파일에서 값을 변경합니다. | Not available. |
| ranger-kms-db-ca | Ranger KMS와의 MySQL SSL 연결에서 CA 파일의 값을 변경합니다. | Not available. |
| spark | Apache Spark에 대한 Amazon EMR 큐레이트 설정입니다. | This property modifies spark-defaults. See actions there. |
| spark-defaults | Spark spark-defaults.conf 파일에서 값을 변경합니다. | Restarts Spark history server and Spark thrift server. |
| spark-env | Spark 환경에서 값을 변경합니다. | Restarts Spark history server and Spark thrift server. |
| spark-hive-site | Spark hive-site.xml 파일에서 값을 변경합니다. | Not available. |
| spark-log4j2 | Spark log4j2.properties 파일에서 값을 변경합니다. | Restarts Spark history server and Spark thrift server. |
| spark-metrics | Spark metrics.properties 파일에서 값을 변경합니다. | Restarts Spark history server and Spark thrift server. |
| sqoop-env | Sqoop 환경에서 값을 변경합니다. | Not available. |
| sqoop-oraoop-site | Sqoop OraOop oraoop-site.xml 파일에서 값을 변경합니다. | Not available. |
| sqoop-site | Sqoop sqoop-site.xml 파일에서 값을 변경합니다. | Not available. |
| tez-site | Tez tez-site.xml 파일에서 값을 변경합니다. | Restart Oozie and HiveServer2. |
| yarn-env | YARN 환경에서 값을 변경합니다. | Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts MapReduce-HistoryServer. |
| yarn-site | YARN yarn-site.xml 파일에서 값을 변경합니다. | Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts Livy Server and MapReduce-HistoryServer. |
| zeppelin-env | Zeppelin 환경에서 값을 변경합니다. | Restarts Zeppelin. |
| zeppelin-site | zeppelin-site.xml에서 구성 설정을 변경합니다. | Restarts Zeppelin. |
| zookeeper-config | ZooKeeper zoo.cfg 파일에서 값을 변경합니다. | Restarts Zookeeper server. |
| zookeeper-logback | ZooKeeper logback.xml 파일에서 값을 변경합니다. | Restarts Zookeeper server. |
| emr-metrics | 이 노드에 대한 emr 지표 설정을 변경합니다. | Restarts the CloudWatchAgent service. |
## 7.1.0 변경 로그
**7.1.0 릴리스 및 릴리스 정보에 대한 변경 로그**
| Date | 이벤트 | 설명 |
| --- | --- | --- |
| 2025-09-03 | 문서 개정 | Amazon EMR 7.1.0 릴리스 정보에 알려진 문제 추가됨 |
| 2024-05-10 | 문서 게시 | Amazon EMR 7.1.0 릴리스 정보 최초 게시됨 |
| 2024-05-10 | 문서 게시 | Amazon EMR 7.1.0 릴리스 정보 최초 게시됨 |
| 2024-05-08 | 배포 완료 | 모든 [지원되는 리전](https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/)에 Amazon EMR 7.1.0 전체 배포됨 |
| 2024-04-23 | 초기 릴리스 | 최초 상용 리전에 Amazon EMR 7.1.0 최초 배포됨 |
# Amazon EMR 릴리스 7.0.0
## 7.0.0 애플리케이션 버전
이 릴리스에서 지원되는 애플리케이션은 [https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Install-CloudWatch-Agent.html](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Install-CloudWatch-Agent.html), [https://delta.io/](https://delta.io/), [https://flink.apache.org/](https://flink.apache.org/), [http://hbase.apache.org/](http://hbase.apache.org/), [https://cwiki.apache.org/confluence/display/Hive/HCatalog](https://cwiki.apache.org/confluence/display/Hive/HCatalog), [http://hadoop.apache.org/docs/current/](http://hadoop.apache.org/docs/current/), [http://hive.apache.org/](http://hive.apache.org/), [https://hudi.apache.org](https://hudi.apache.org), [http://gethue.com/](http://gethue.com/), [https://iceberg.apache.org/](https://iceberg.apache.org/), [https://jupyter-enterprise-gateway.readthedocs.io/en/latest/](https://jupyter-enterprise-gateway.readthedocs.io/en/latest/), [https://jupyterhub.readthedocs.io/en/latest/#](https://jupyterhub.readthedocs.io/en/latest/#), [https://livy.incubator.apache.org/](https://livy.incubator.apache.org/), [https://mxnet.incubator.apache.org/](https://mxnet.incubator.apache.org/), [http://oozie.apache.org/](http://oozie.apache.org/), [https://phoenix.apache.org/](https://phoenix.apache.org/), [http://pig.apache.org/](http://pig.apache.org/), [https://prestodb.io/](https://prestodb.io/), [https://spark.apache.org/docs/latest/](https://spark.apache.org/docs/latest/), [http://sqoop.apache.org/](http://sqoop.apache.org/), [https://www.tensorflow.org/](https://www.tensorflow.org/), [https://tez.apache.org/](https://tez.apache.org/), [https://trino.io/](https://trino.io/), [https://zeppelin.incubator.apache.org/](https://zeppelin.incubator.apache.org/), [https://zookeeper.apache.org](https://zookeeper.apache.org)입니다.
아래 테이블에는 이번 Amazon EMR 릴리스에서 사용할 수 있는 애플리케이션 버전과 이전 세 가지 Amazon EMR 릴리스(해당하는 경우)의 애플리케이션 버전이 나와 있습니다.
각 Amazon EMR 릴리스에서 애플리케이션 버전의 전체 기록은 다음 주제를 참조하세요.
+ [Amazon EMR 7.x 릴리스의 애플리케이션 버전](emr-release-app-versions-7.x.md)
+ [Amazon EMR 6.x 릴리스의 애플리케이션 버전](emr-release-app-versions-6.x.md)
+ [Amazon EMR 5.x 릴리스의 애플리케이션 버전](emr-release-app-versions-5.x.md)
+ [Amazon EMR 4.x 릴리스의 애플리케이션 버전](emr-release-app-versions-4.x.md)
**애플리케이션 버전 정보**
| | emr-7.3.0 | emr-7.2.0 | emr-7.1.0 | emr-7.0.0 |
| --- | --- | --- | --- | --- |
| AWS Java용 SDK | 2.25.70, 1.12.747 | 2.23.18, 1.12.705 | 2.23.18, 1.12.656 | 2.20.160-amzn-0, 1.12.569 |
| Python | 3.9, 3.11 | 3.9, 3.11 | 3.9, 3.11 | 3.9 |
| Scala | 2.12.18 | 2.12.17 | 2.12.17 | 2.12.17 |
| AmazonCloudWatchAgent | 1.300032.2-amzn-0 | 1.300032.2-amzn-0 | 1.300032.2-amzn-0 | 1.300031.1-amzn-0 |
| Delta | 3.2.0-amzn-0 | 3.1.0 | 3.0.0 | 3.0.0 |
| Flink | 1.18.1-amzn-2 | 1.18.1-amzn-1 | 1.18.1-amzn-0 | 1.18.0-amzn-0 |
| Ganglia | - | - | - | - |
| HBase | 2.4.17-amzn-7 | 2.4.17-amzn-6 | 2.4.17-amzn-5 | 2.4.17-amzn-4 |
| HCatalog | 3.1.3-amzn-12 | 3.1.3-amzn-11 | 3.1.3-amzn-10 | 3.1.3-amzn-9 |
| Hadoop | 3.3.6-amzn-5 | 3.3.6-amzn-4 | 3.3.6-amzn-3 | 3.3.6-amzn-2 |
| Hive | 3.1.3-amzn-12 | 3.1.3-amzn-11 | 3.1.3-amzn-10 | 3.1.3-amzn-9 |
| Hudi | 0.15.0-amzn-0 | 0.14.1-amzn-1 | 0.14.1-amzn-0 | 0.14.0-amzn-1 |
| Hue | 4.11.0 | 4.11.0 | 4.11.0 | 4.11.0 |
| Iceberg | 1.5.2-amzn-0 | 1.5.0-amzn-0 | 1.4.3-amzn-0 | 1.4.2-amzn-0 |
| JupyterEnterpriseGateway | 2.6.0 | 2.6.0 | 2.6.0 | 2.6.0 |
| JupyterHub | 1.5.0 | 1.5.0 | 1.5.0 | 1.5.0 |
| Livy | 0.8.0-incubating | 0.8.0-incubating | 0.8.0-incubating | 0.7.1-incubating |
| MXNet | - | 1.9.1 | 1.9.1 | 1.9.1 |
| Mahout | - | - | - | - |
| Oozie | 5.2.1 | 5.2.1 | 5.2.1 | 5.2.1 |
| Phoenix | 5.1.3 | 5.1.3 | 5.1.3 | 5.1.3 |
| Pig | 0.17.0 | 0.17.0 | 0.17.0 | 0.17.0 |
| Presto | 0.285-amzn-1 | 0.285-amzn-0 | 0.284-amzn-0 | 0.283-amzn-1 |
| Spark | 3.5.1-amzn-1 | 3.5.1-amzn-0 | 3.5.0-amzn-1 | 3.5.0-amzn-0 |
| Sqoop | 1.4.7 | 1.4.7 | 1.4.7 | 1.4.7 |
| TensorFlow | 2.16.1 | 2.11.0 | 2.11.0 | 2.11.0 |
| Tez | 0.10.2-amzn-10 | 0.10.2-amzn-9 | 0.10.2-amzn-8 | 0.10.2-amzn-7 |
| Trino (PrestoSQL) | 442-amzn-0 | 436-amzn-0 | 435-amzn-0 | 426-amzn-1 |
| Zeppelin | 0.11.1 | 0.10.1 | 0.10.1 | 0.10.1 |
| ZooKeeper | 3.9.1-amzn-1 | 3.9.1-amzn-1 | 3.9.1-amzn-0 | 3.5.10 |
## 7.0.0 릴리스 정보
다음 릴리스 정보에는 Amazon EMR 릴리스 7.0.0에 대한 정보가 포함됩니다. 변경 사항은 6.15.0에 관련됩니다.
**새로운 기능**
+ **애플리케이션 업그레이드** – Amazon EMR 7.0.0 application upgrades include Python 3.9, Spark 3.5, Flink 1.18, and Delta 3.0. 또한 이번 릴리스에서는 [Amazon CloudWatch 에이전트](emr-AmazonCloudWatchAgent.md) 애플리케이션에 대한 지원이 추가되고 Ganglia에 대한 지원이 제거됩니다.
+ **Amazon Corretto 17** - Amazon EMR 릴리스 7.0 이상에서는 Apache Livy를 제외한 Corretto 17(JDK 17)을 지원하는 애플리케이션에 대해 기본적으로 Amazon Corretto 17(OpenJDK 기반)이 함께 제공됩니다. 이번 릴리스에서 지원되는 애플리케이션의 JDK 버전에 대한 자세한 내용을 확인하려면 [7.0.0 기본 Java 버전](#emr-700-jdk) 섹션을 참조하세요.
+ **Amazon Linux 2023** – 7.0 릴리스를 사용하면 이제 Amazon EMR 클러스터가 기본적으로 AL2023에서 실행됩니다. 이러한 변경이 기본 AMI 버전에 어떤 영향을 미치는지에 대한 자세한 내용을 확인하려면 *Amazon EMR 관리 안내서*의 [소프트웨어 업데이트 고려 사항](https://docs.aws.amazon.com/emr/latest/ManagementGuide/emr-default-ami.html#emr-default-ami-managing)을 참조하세요. 또한 AL2023에서 Python 2.7이 제거되었으므로 이제 Python이 필요한 모든 구성 요소는 Python 3을 이용하여 작성해야 합니다.
+ **`s3a`가 포함된 S3 on Outpost** – 이제 Amazon EMR에서는 `s3a` 파일 시스템이 포함된 Amazon S3 on Outposts 버킷을 지원합니다. Outposts의 Amazon S3에 대한 자세한 내용은 *Amazon Simple Storage Service 사용 설명서*에서 [S3 on Outposts이란](https://docs.aws.amazon.com/AmazonS3/latest/userguide/S3onOutposts.html)을 참조하세요.
**알려진 문제**
+ PySpark를 Python 버전 3.10 이상과 함께 사용하는 경우 한 번에 두 개 이상의 줄을 실행할 수 없습니다. 한 번에 한 줄씩 실행해야 합니다.
+ 노드에 스레드 및/또는 열린 파일 핸들이 많은 경우 인스턴스의 상태를 모니터링하는 클러스터 내 인스턴스 상태 스크립트는 CPU 및 메모리 리소스를 과도하게 소비할 수 있습니다.
**변경 사항, 향상된 기능 및 해결된 문제**
+ Spark 3.3.1(EMR 버전 6.10 이상에서 지원됨)부터 폐기 호스트의 모든 실행기는 *DECOMMISSIONING* 상태라는 새로운 `ExecutorState` 상태로 설정됩니다. Yarn은 폐기 중인 실행기를 사용하여 작업을 할당할 수 없으므로 필요한 경우 실행 중인 작업에 대해 새 실행기를 요청하세요. 따라서 EMR Managed Scaling, EMR Auto Scaling 또는 EMR-EC2 클러스터의 사용자 지정 조정 메커니즘을 사용하는 동안 Spark DRA를 비활성화하면 Yarn이 각 작업에 허용되는 최대 실행기를 요청할 수 있습니다. 이 문제를 방지하려면 위의 기능 조합을 사용할 때 `spark.dynamicAllocation.enabled` 속성을 `TRUE`(기본값)로 설정한 상태로 둡니다. 또한 Spark 작업의 `spark.dynamicAllocation.maxExecutors` 및 `spark.dynamicAllocation.minExecutors` 속성 값을 설정하여 작업 실행 중에 할당된 실행기 수를 제한하여 최소 및 최대 실행기 제약 조건을 설정할 수도 있습니다.
+ 클러스터에 있는 모든 인스턴스의 상태를 유지하기 위해 Amazon EMR은 Apache YARN, Apache HDFS 및 Kerberos와 통합됩니다. 7.0에서는 이러한 통합 기능을 개선하여 확장 또는 기타 작업으로 인해 종료된 인스턴스의 상태를 안정적으로 제거할 수 있도록 했습니다. 이러한 노력은 관리형 확장이 활성화된 오래된 클러스터의 경우, 자주 규모를 조정하고 수명 기간 동안 종료된 인스턴스가 수천 개 누적되기 때문에 특히 중요합니다.
+ 이번 릴리스는 Kerberos 구성을 개선하여 AES 기반 암호만 지원하도록 했습니다. AES 기반이 아닌 암호를 사용하는 Kerberos KDC는 Amazon EMR 릴리스 7.0.0 이상에서 실행되는 EMR 클러스터에서 더 이상 지원되지 않습니다. AES 기반 암호는 클러스터에 가장 강력한 보안을 제공합니다.
+ AWS SDK 2.x 마이그레이션의 일환으로 Amazon EMR 7.0에는 호환성을 위해 Spark Kinesis 커넥터에 대한 업데이트가 포함되어 있습니다. 이 업데이트는 커뮤니티 버전의 Apache Spark에서는 이용할 수 없습니다. 7.0 미만의 Amazon EMR 릴리스에서 Spark Kinesis 커넥터를 사용하는 경우, 워크로드를 Amazon EMR 7.0으로 마이그레이션하기 전에 애플리케이션 코드를 마이그레이션하여 SDK 2.x에서 실행되도록 해야 합니다. 자세한 내용은 [Spark Kinesis 커넥터를 Amazon EMR 7.0용 SDK 2.x로 마이그레이션](migrating-spark-kinesis.md) 단원을 참조하십시오.
+ Amazon EMR 7.x 이상에서는 `aws-sagemaker-spark-sdk` 구성 요소를 사용할 수 없습니다.
+ Amazon EMR 5.36 이상, 6.6 이상 또는 7.0 이상의 *최신 패치 릴리스*가 적용된 클러스터를 시작하는 경우 Amazon EMR은 기본 Amazon EMR AMI에 대한 최신 Amazon Linux 2023 or Amazon Linux 2 릴리스를 사용합니다. 자세한 내용은 [Amazon EMR에 대한 기본 Amazon Linux AMI 사용](https://docs.aws.amazon.com/emr/latest/ManagementGuide/emr-default-ami.html)을 참조하세요.
[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/ko_kr/emr/latest/ReleaseGuide/emr-700-release.html)
## 7.0.0 기본 Java 버전
Amazon EMR 릴리스 7.0 이상에서는 Apache Livy를 제외한 Corretto 17(JDK 17)을 지원하는 애플리케이션에 대해 기본적으로 Amazon Corretto 17(OpenJDK 기반)이 함께 제공됩니다.
다음 표에서는 Amazon EMR 7.0.0에 있는 애플리케이션의 기본 Java 버전을 확인할 수 있습니다. 클러스터의 기본 JVM을 변경하려면 클러스터에서 실행되는 각 애플리케이션에 대해 [특정 Java 가상 머신을 사용하도록 애플리케이션 구성](configuring-java8.md)의 지침을 따릅니다. 클러스터에서는 Java 런타임 버전 1개만 사용할 수 있습니다. Amazon EMR은 동일한 클러스터에서 다양한 런타임 버전을 사용해 서로 다른 노드 또는 애플리케이션을 실행하는 것을 지원하지 않습니다.
| 애플리케이션 | Java 및 Amazon Corretto 버전(기본값은 굵은체로 표시) |
| --- | --- |
| 델타 | 17, 11, 8 |
| Flink | 11, 8 |
| HBase | 11, 8 |
| HCatalog | 17, 11, 8 |
| Hadoop | 17, 11, 8 |
| Hive | 17, 11, 8 |
| Hudi | 17, 11, 8 |
| Iceberg | 17, 11, 8 |
| Livy | 17, 11, 8 |
| Oozie | 17, 11, 8 |
| 피닉스 | 8 |
| PrestoDB | 8 |
| Spark | 17, 11, 8 |
| Spark RAPIDS | 17, 11, 8 |
| Sqoop | 8 |
| Tez의 Hive 실행 시간 비교 | 17, 11, 8 |
| Trino | 17 |
| Zeppelin | 8 |
| Pig | 8 |
| Zookeeper | 8 |
## 7.0.0 구성 요소 버전
이 릴리스를 통해 Amazon EMR이 설치하는 구성 요소는 다음과 같습니다. 일부는 빅 데이터 애플리케이션 패키지의 일부로 설치됩니다. 나머지는 Amazon EMR에 고유하며 시스템 프로세스 및 기능을 위해 설치됩니다. 이는 일반적으로 `emr` 또는 `aws`로 시작됩니다. 최근 Amazon EMR 릴리스의 빅 데이터 애플리케이션 패키지는 일반적으로 커뮤니티에서 발견된 최신 버전입니다. 가능한 한 빨리 Amazon EMR에서 커뮤니티 릴리스를 제공합니다.
Amazon EMR의 일부 구성 요소는 커뮤니티 버전과 다릅니다. 이러한 구성 요소에는 `CommunityVersion-amzn-EmrVersion` 양식의 버전 레이블이 있습니다. `EmrVersion`은 0에서 시작합니다. 예를 들어, 버전 2.2의 `myapp-component`라는 오픈 소스 커뮤니티 구성 요소가 다른 Amazon EMR 릴리스에 포함되도록 세 번 수정된 경우 해당 릴리스 버전은 `2.2-amzn-2`로 나열됩니다.
| 구성 요소 | 버전 | 설명 |
| --- | --- | --- |
| adot-java-agent | 1.31.0 | 애플리케이션 대몬(daemon)에서 지표를 수집하는 Java 에이전트입니다. |
| delta | 3.0.0 | Delta Lake는 방대한 분석 데이터 세트를 위한 오픈 테이블 형식입니다. |
| delta-standalone-connectors | 0.6.0 | Delta 커넥터는 Delta Lake를 Flink, Hive, Presto와 같은 엔진과 통합하기 위한 다양한 런타임을 제공합니다. |
| emr-amazon-cloudwatch-agent | 1.300031.1-amzn-0 | Amazon EC2 인스턴스에서 내부 시스템 수준 지표와 사용자 지정 애플리케이션 지표를 수집하는 애플리케이션입니다. |
| emr-ddb | 5.2.0 | 하둡 에코시스템 애플리케이션용 Amazon DynamoDB 커넥터 |
| emr-goodies | 3.9.0 | 편리한 하둡 에코시스템용 추가 라이브러리 |
| emr-kinesis | 3.13.0 | 하둡 에코시스템 애플리케이션용 Amazon Kinesis 커넥터. |
| emr-notebook-env | 1.7.0 | Jupyter Enterprise Gateway가 포함된 EMR 노트북용 Conda 환경 |
| emr-s3-dist-cp | 2.30.0 | Amazon S3용으로 최적화된 분사 복사 애플리케이션. |
| emr-s3-select | 2.9.0 | EMR S3Select 커넥터 |
| emr-wal-cli | 1.2.1 | emrwal 목록/삭제에 사용되는 CLI입니다. |
| emrfs | 2.61.0 | 하둡 에코시스템 애플리케이션용 Amazon S3 커넥터. |
| flink-client | 1.18.0-amzn-0 | Apache Flink 명령줄 클라이언트 스크립트 및 애플리케이션 |
| flink-jobmanager-config | 1.18.0-amzn-0 | Apache Flink JobManager에 대한 EMR 노드에서 리소스를 관리합니다. |
| hadoop-client | 3.3.6-amzn-2 | 'hdfs', 'hadoop', 'yarn' 등과 같은 하둡 명령줄 클라이언트 |
| hadoop-hdfs-datanode | 3.3.6-amzn-2 | 블록을 저장하는 HDFS 노드 수준 서비스 |
| hadoop-hdfs-library | 3.3.6-amzn-2 | HDFS 명령줄 클라이언트 및 라이브러리 |
| hadoop-hdfs-namenode | 3.3.6-amzn-2 | 파일 이름 및 블록 위치를 추적하는 HDFS 서비스 |
| hadoop-hdfs-journalnode | 3.3.6-amzn-2 | HA 클러스터에서 하둡 파일 시스템 저널을 관리하기 위한 HDFS 서비스 |
| hadoop-httpfs-server | 3.3.6-amzn-2 | HDFS 작업에 대한 HTTP 엔드포인트 |
| hadoop-kms-server | 3.3.6-amzn-2 | 하둡의 KeyProvider API를 기반으로 하는 암호화 키 관리 서버 |
| hadoop-mapred | 3.3.6-amzn-2 | MapReduce 애플리케이션을 실행하는 MapReduce 실행 엔진 라이브러리 |
| hadoop-yarn-nodemanager | 3.3.6-amzn-2 | 개별 노드의 컨테이너를 관리하는 YARN 서비스 |
| hadoop-yarn-resourcemanager | 3.3.6-amzn-2 | 클러스터 리소스 및 분산 애플리케이션을 할당 및 관리하는 YARN 서비스 |
| hadoop-yarn-timeline-server | 3.3.6-amzn-2 | YARN 애플리케이션의 현재 및 기록 정보를 가져오는 서비스 |
| hbase-hmaster | 2.4.17-amzn-4 | 리전 조정 및 관리 명령의 실행을 담당하는 HBase 클러스터용 서비스 |
| hbase-region-server | 2.4.17-amzn-4 | 한 개 이상의 HBase 리전에 서비스를 제공하는 서비스 |
| hbase-client | 2.4.17-amzn-4 | HBase 명령줄 클라이언트 |
| hbase-rest-server | 2.4.17-amzn-4 | HBase용 RESTful HTTP 엔드포인트를 제공하는 서비스 |
| hbase-thrift-server | 2.4.17-amzn-4 | HBase에 Thrift 엔드포인트를 제공하는 서비스 |
| hbase-operator-tools | 2.4.17-amzn-4 | Apache HBase 클러스터용 복구 도구. |
| hcatalog-client | 3.1.3-amzn-9 | hcatalog-server를 조정하기 위한 'hcat' 명령줄 클라이언트 |
| hcatalog-server | 3.1.3-amzn-9 | 분산 애플리케이션용 스토리지 관리 계층, 테이블 및 HCatalog를 제공하는 서비스 |
| hcatalog-webhcat-server | 3.1.3-amzn-9 | HCatalog에 REST 인터페이스를 제공하는 HTTP 엔드포인트 |
| hive-client | 3.1.3-amzn-9 | Hive 명령줄 클라이언트 |
| hive-hbase | 3.1.3-amzn-9 | Hive-hbase 클라이언트 |
| hive-metastore-server | 3.1.3-amzn-9 | 하둡 작업에 대한 SQL용 메타데이터가 저장되는 시맨틱 리포지토리인 Hive 메타스토어에 액세스하기 위한 서비스 |
| hive-server2 | 3.1.3-amzn-9 | Hive 쿼리를 웹 요청으로 수락하기 위한 서비스 |
| hudi | 0.14.0-amzn-1 | 짧은 지연 시간 및 높은 효율성으로 데이터 파이프라인을 구동하는 증분 처리 프레임워크. |
| hudi-presto | 0.14.0-amzn-1 | Hudi로 Presto를 실행하기 위한 번들 라이브러리. |
| hudi-trino | 0.14.0-amzn-1 | Hudi와 함께 Trnio를 실행하기 위한 번들 라이브러리. |
| hudi-spark | 0.14.0-amzn-1 | Hudi와 함께 Spark를 실행하기 위한 번들 라이브러리. |
| hue-server | 4.11.0 | 하둡 에코시스템 애플리케이션을 사용하여 데이터를 분석하는 웹 애플리케이션. |
| iceberg | 1.4.2-amzn-0 | Apache Iceberg는 방대한 분석 데이터 세트를 위한 오픈 테이블 형식입니다. |
| jupyterhub | 1.5.0 | Jupyter Notebook용 다중 사용자 서버 |
| livy-server | 0.7.1-incubating | Apache Spark와 상호작용하기 위한 REST 인터페이스 |
| nginx | 1.12.1 | HTTP인 nginx [engine x] 및 역방향 프록시 서버 |
| mxnet | 1.9.1 | 유연성, 확장성 및 효율성이 뛰어난 딥 러닝용 라이브러리. |
| mariadb-server | 5.5.68 이상 | MariaDB 데이터베이스 서버. |
| nvidia-cuda | 11.8.0 | Nvidia 드라이버와 Cuda 도구 키트 |
| oozie-client | 5.2.1 | Oozie 명령줄 클라이언트 |
| oozie-server | 5.2.1 | Oozie 워크플로 요청을 수락하는 서비스 |
| opencv | 4.7.0 | 오픈 소스 컴퓨터 비전 라이브러리. |
| phoenix-library | 5.1.3 | 서버 및 클라이언트의 phoenix 라이브러리 |
| phoenix-connectors | 5.1.3 | Spark-3용 Apache Phoenix 커넥터 |
| phoenix-query-server | 6.0.0 | Avatica API에 대한 JSON 형식 액세스 및 프로토콜 버퍼 액세스를 비롯하여 JDBC 액세스를 제공하는 경량 서버 |
| presto-coordinator | 0.283-amzn-1 | presto-worker의 쿼리를 수락하고 쿼리 실행을 관리하는 서비스. |
| presto-worker | 0.283-amzn-1 | 여러 쿼리를 실행하는 서비스. |
| presto-client | 0.283-amzn-1 | Presto 서버가 시작되지 않은 HA 클러스터의 대기 마스터에 설치된 Presto 명령줄 클라이언트. |
| trino-coordinator | 426-amzn-1 | trino-workers의 쿼리를 수락하고 쿼리 실행을 관리하는 서비스. |
| trino-worker | 426-amzn-1 | 여러 쿼리를 실행하는 서비스. |
| trino-client | 426-amzn-1 | Trino 서버가 시작되지 않은 HA 클러스터의 대기 마스터에 설치된 Trino 명령줄 클라이언트. |
| pig-client | 0.17.0 | Pig 명령줄 클라이언트. |
| r | 4.3.2 | 통계 컴퓨팅용 R 프로젝트 |
| ranger-kms-server | 2.0.0 | Apache Ranger 키 관리 시스템 |
| spark-client | 3.5.0-amzn-0 | Spark 명령줄 클라이언트. |
| spark-history-server | 3.5.0-amzn-0 | 완료된 Spark 애플리케이션의 수명에 대해 기록된 이벤트를 조회하는 웹 UI. |
| spark-on-yarn | 3.5.0-amzn-0 | YARN용 인 메모리 실행 엔진. |
| spark-yarn-slave | 3.5.0-amzn-0 | YARN 슬레이브에서 필요한 Apache Spark 라이브러리. |
| spark-rapids | 23.10.0-amzn-0 | GPU로 Apache Spark를 가속화하는 Nvidia Spark RAPIDS 플러그인. |
| sqoop-client | 1.4.7 | Apache Sqoop 명령줄 클라이언트. |
| tensorflow | 2.11.0 | TensorFlow는 고성능 수치 계산용 오픈 소스 소프트웨어 라이브러리입니다. |
| tez-on-yarn | 0.10.2-amzn-7 | tez YARN 애플리케이션 및 라이브러리. |
| tez-on-worker | 0.10.2-amzn-7 | 워커 노드에 대한 tez YARN 애플리케이션 및 라이브러리. |
| webserver | 2.4.58 | Apache HTTP 서버. |
| zeppelin-server | 0.10.1 | 대화형 데이터 분석이 가능한 웹 기반 노트북 |
| zookeeper-server | 3.5.10 | 구성 정보 유지 관리, 이름 지정, 분산 동기화 제공 및 그룹 서비스 제공을 위한 중앙 집중식 서비스. |
| zookeeper-client | 3.5.10 | ZooKeeper 명령줄 클라이언트. |
## 7.0.0 구성 분류
구성 분류를 사용하면 애플리케이션을 사용자 지정할 수 있습니다. 이는 종종 `hive-site.xml`과 같이 애플리케이션의 구성 XML 파일에 해당합니다. 자세한 내용은 [애플리케이션 구성](emr-configure-apps.md) 단원을 참조하십시오.
재구성 작업은 실행 중인 클러스터의 인스턴스 그룹에 대한 구성을 지정할 때 수행됩니다. Amazon EMR은 사용자가 수정한 분류에 대한 재구성 작업만 시작합니다. 자세한 내용은 [실행 중인 클러스터에서 인스턴스 그룹 재구성](emr-configure-apps-running-cluster.md) 단원을 참조하십시오.
**emr-7.0.0 분류**
| 분류 | 설명 | 재구성 작업 |
| --- | --- | --- |
| capacity-scheduler | Hadoop capacity-scheduler.xml 파일에서 값을 변경합니다. | Restarts the ResourceManager service. |
| container-executor | Hadoop YARN container-executor.cfg 파일에서 값을 변경합니다. | Not available. |
| container-log4j | Hadoop YARN container-log4j.properties 파일에서 값을 변경합니다. | Not available. |
| core-site | Hadoop core-site.xml 파일에서 값을 변경합니다. | Restarts the Hadoop HDFS services Namenode, SecondaryNamenode, Datanode, ZKFC, and Journalnode. Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts Hadoop KMS, Ranger KMS, HiveServer2, Hive MetaStore, Hadoop Httpfs, and MapReduce-HistoryServer. |
| docker-conf | Docker 관련 설정을 변경합니다. | Not available. |
| emrfs-site | EMRFS 설정을 변경합니다. | Restarts the Hadoop HDFS services Namenode, SecondaryNamenode, Datanode, ZKFC, and Journalnode. Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts HBaseRegionserver, HBaseMaster, HBaseThrift, HBaseRest, HiveServer2, Hive MetaStore, Hadoop Httpfs, and MapReduce-HistoryServer. |
| flink-conf | flink-conf.yaml 설정을 변경합니다. | Restarts Flink history server. |
| flink-log4j | Flink log4j.properties 설정을 변경합니다. | Restarts Flink history server. |
| flink-log4j-session | Kubernetes 및 Yarn 세션에 대한 Flink log4j-session.properties 설정을 변경합니다. | Restarts Flink history server. |
| flink-log4j-cli | Flink log4j-cli.properties 설정을 변경합니다. | Restarts Flink history server. |
| hadoop-env | 모든 Hadoop 구성 요소에 대한 Hadoop 환경에서 값을 변경합니다. | Restarts the Hadoop HDFS services Namenode, SecondaryNamenode, Datanode, ZKFC, and Journalnode. Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts PhoenixQueryserver, HiveServer2, Hive MetaStore, and MapReduce-HistoryServer. |
| hadoop-log4j | Hadoop log4j.properties 파일에서 값을 변경합니다. | Restarts the Hadoop HDFS services SecondaryNamenode, Datanode, and Journalnode. Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts Hadoop KMS, Hadoop Httpfs, and MapReduce-HistoryServer. |
| hadoop-ssl-server | hadoop ssl 서버 구성을 변경합니다. | Not available. |
| hadoop-ssl-client | hadoop ssl 클라이언트 구성을 변경합니다. | Not available. |
| hbase | Apache HBase에 대한 Amazon EMR 큐레이트 설정입니다. | Custom EMR specific property. Sets emrfs-site and hbase-site configs. See those for their associated restarts. |
| hbase-env | HBase 환경에서 값을 변경합니다. | Restarts the HBase services RegionServer, HBaseMaster, ThriftServer, RestServer. |
| hbase-log4j | HBase hbase-log4j.properties 파일에서 값을 변경합니다. | Restarts the HBase services RegionServer, HBaseMaster, ThriftServer, RestServer. |
| hbase-metrics | HBase hadoop-metrics2-hbase.properties 파일에서 값을 변경합니다. | Restarts the HBase services RegionServer, HBaseMaster, ThriftServer, RestServer. |
| hbase-policy | HBase hbase-policy.xml 파일에서 값을 변경합니다. | Not available. |
| hbase-site | HBase hbase-site.xml 파일에서 값을 변경합니다. | Restarts the HBase services RegionServer, HBaseMaster, ThriftServer, RestServer. Additionally restarts Phoenix QueryServer. |
| hdfs-encryption-zones | HDFS 암호화 영역을 구성합니다. | This classification should not be reconfigured. |
| hdfs-env | HDFS 환경에서 값을 변경합니다. | Restarts Hadoop HDFS services Namenode, Datanode, and ZKFC. |
| hdfs-site | HDFS hdfs-site.xml에서 값을 변경합니다. | Restarts the Hadoop HDFS services Namenode, SecondaryNamenode, Datanode, ZKFC, and Journalnode. Additionally restarts Hadoop Httpfs. |
| hcatalog-env | HCatalog 환경에서 값을 변경합니다. | Restarts Hive HCatalog Server. |
| hcatalog-server-jndi | HCatalog jndi.properties 환경에서 값을 변경합니다. | Restarts Hive HCatalog Server. |
| hcatalog-server-proto-hive-site | HCatalog proto-hive-site.xml에서 값을 변경합니다. | Restarts Hive HCatalog Server. |
| hcatalog-webhcat-env | HCatalog WebHCat 환경에서 값을 변경합니다. | Restarts Hive WebHCat server. |
| hcatalog-webhcat-log4j2 | HCatalog WebHCat log4j2.properties에서 값을 변경합니다. | Restarts Hive WebHCat server. |
| hcatalog-webhcat-site | HCatalog WebHCat webhcat-site.xml 파일에서 값을 변경합니다. | Restarts Hive WebHCat server. |
| hive | Apache Hive에 대한 Amazon EMR 큐레이트 설정입니다. | Sets configurations to launch Hive LLAP service. |
| hive-beeline-log4j2 | Hive beeline-log4j2.properties 파일에서 값을 변경합니다. | Not available. |
| hive-parquet-logging | Hive parquet-logging.properties 파일에서 값을 변경합니다. | Not available. |
| hive-env | Hive 환경에서 값을 변경합니다. | Restarts HiveServer2, HiveMetastore, and Hive HCatalog-Server. Runs Hive schemaTool CLI commands to verify hive-metastore. |
| hive-exec-log4j2 | Hive hive-exec-log4j2.properties 파일에서 값을 변경합니다. | Not available. |
| hive-llap-daemon-log4j2 | Hive llap-daemon-log4j2.properties 파일에서 값을 변경합니다. | Not available. |
| hive-log4j2 | Hive hive-log4j2.properties 파일에서 값을 변경합니다. | Not available. |
| hive-site | Hive hive-site.xml 파일에서 값을 변경합니다. | Restarts HiveServer2, HiveMetastore, and Hive HCatalog-Server. Runs Hive schemaTool CLI commands to verify hive-metastore. Also restarts Oozie and Zeppelin. |
| hiveserver2-site | Hive Server2 hiveserver2-site.xml 파일에서 값을 변경합니다. | Not available. |
| hue-ini | Hue ini 파일에서 값을 변경합니다. | Restarts Hue. Also activates Hue config override CLI commands to pick up new configurations. |
| httpfs-env | HTTPFS 환경에서 값을 변경합니다. | Restarts Hadoop Httpfs service. |
| httpfs-site | Hadoop httpfs-site.xml 파일에서 값을 변경합니다. | Restarts Hadoop Httpfs service. |
| hadoop-kms-acls | Hadoop kms-acls.xml 파일에서 값을 변경합니다. | Not available. |
| hadoop-kms-env | Hadoop KMS 환경에서 값을 변경합니다. | Restarts Hadoop-KMS service. |
| hadoop-kms-java-home | Hadoop의 KMS java 홈 변경 | Not available. |
| hadoop-kms-log4j | Hadoop kms-log4j.properties 파일에서 값을 변경합니다. | Not available. |
| hadoop-kms-site | Hadoop kms-site.xml 파일에서 값을 변경합니다. | Restarts Hadoop-KMS and Ranger-KMS service. |
| hudi-env | Hudi 환경에서 값을 변경합니다. | Not available. |
| hudi-defaults | Hudi hudi-defaults.conf 파일에서 값을 변경합니다. | Not available. |
| iceberg-defaults | Iceberg iceberg-defaults.conf 파일에서 값을 변경합니다. | Not available. |
| delta-defaults | Delta delta-defaults.conf 파일에서 값을 변경합니다. | Not available. |
| jupyter-notebook-conf | Jupyter Notebook jupyter\$1notebook\$1config.py 파일에서 값을 변경합니다. | Not available. |
| jupyter-hub-conf | JupyterHubs jupyterhub\$1config.py 파일에서 값을 변경합니다. | Not available. |
| jupyter-s3-conf | Jupyter Notebook S3 지속성 구성 | Not available. |
| jupyter-sparkmagic-conf | Sparkmagic config.json 파일에서 값을 변경합니다. | Not available. |
| livy-conf | Livy livy.conf 파일에서 값을 변경합니다. | Restarts Livy Server. |
| livy-env | Livy 환경에서 값을 변경합니다. | Restarts Livy Server. |
| livy-log4j2 | Livy log4j2.properties 설정을 변경합니다. | Restarts Livy Server. |
| mapred-env | MapReduce 애플리케이션 환경에서 값을 변경합니다. | Restarts Hadoop MapReduce-HistoryServer. |
| mapred-site | MapReduce 애플리케이션 mapred-site.xml 파일에서 값을 변경합니다. | Restarts Hadoop MapReduce-HistoryServer. |
| oozie-env | Oozie 환경에서 값을 변경합니다. | Restarts Oozie. |
| oozie-log4j | Oozie oozie-log4j.properties 파일에서 값을 변경합니다. | Restarts Oozie. |
| oozie-site | Oozie oozie-site.xml 파일에서 값을 변경합니다. | Restarts Oozie. |
| phoenix-hbase-metrics | Phoenix hadoop-metrics2-hbase.properties 파일에서 값을 변경합니다. | Not available. |
| phoenix-hbase-site | Phoenix hbase-site.xml 파일에서 값을 변경합니다. | Not available. |
| phoenix-log4j | Phoenix log4j.properties 파일에서 값을 변경합니다. | Restarts Phoenix-QueryServer. |
| phoenix-metrics | Phoenix hadoop-metrics2-phoenix.properties 파일에서 값을 변경합니다. | Not available. |
| pig-env | Pig 환경에서 값을 변경합니다. | Not available. |
| pig-properties | Pig pig.properties 파일에서 값을 변경합니다. | Restarts Oozie. |
| pig-log4j | Pig log4j.properties 파일에서 값을 변경합니다. | Not available. |
| presto-log | Presto log.properties 파일에서 값을 변경합니다. | Restarts Presto-Server (for PrestoDB) |
| presto-config | Presto config.properties 파일에서 값을 변경합니다. | Restarts Presto-Server (for PrestoDB) |
| presto-password-authenticator | Presto password-authenticator.properties 파일에서 값을 변경합니다. | Not available. |
| presto-env | Presto presto-env.sh 파일에서 값을 변경합니다. | Restarts Presto-Server (for PrestoDB) |
| presto-node | Presto node.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-blackhole | Presto blackhole.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-cassandra | Presto cassandra.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-hive | Presto hive.properties 파일에서 값을 변경합니다. | Restarts Presto-Server (for PrestoDB) |
| presto-connector-jmx | Presto jmx.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-kafka | Presto kafka.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-lakeformation | Presto lakeformation.properties 파일에서 값을 변경합니다. | Restarts Presto-Server (for PrestoDB) |
| presto-connector-localfile | Presto localfile.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-memory | Presto memory.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-mongodb | Presto mongodb.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-mysql | Presto mysql.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-postgresql | Presto postgresql.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-raptor | Presto raptor.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-redis | Presto redis.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-redshift | Presto redshift.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-tpch | Presto tpch.properties 파일에서 값을 변경합니다. | Not available. |
| presto-connector-tpcds | Presto tpcds.properties 파일에서 값을 변경합니다. | Not available. |
| trino-log | Trino log.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-config | Trino config.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-password-authenticator | Trino password-authenticator.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-env | Trino trino-env.sh 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-node | Trino node.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-blackhole | Trino blackhole.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-cassandra | Trino cassandra.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-delta | Trino delta.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-connector-hive | Trino hive.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-exchange-manager | Trino exchange-manager.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-connector-iceberg | Trino iceberg.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-connector-hudi | Trino hudi.properties 파일에서 값을 변경합니다. | Restarts Trino-Server (for Trino) |
| trino-connector-jmx | Trino jmx.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-kafka | Trino kafka.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-localfile | Trino localfile.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-memory | Trino memory.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-mongodb | Trino mongodb.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-mysql | Trino mysql.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-postgresql | Trino postgresql.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-raptor | Trino raptor.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-redis | Trino redis.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-redshift | Trino redshift.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-tpch | Trino tpch.properties 파일에서 값을 변경합니다. | Not available. |
| trino-connector-tpcds | Trino tpcds.properties 파일에서 값을 변경합니다. | Not available. |
| ranger-kms-dbks-site | Ranger KMS dbks-site.xml 파일에서 값을 변경합니다. | Restarts Ranger KMS Server. |
| ranger-kms-site | Ranger KMS ranger-kms-site.xml 파일에서 값을 변경합니다. | Restarts Ranger KMS Server. |
| ranger-kms-env | Ranger KMS 환경에서 값을 변경합니다. | Restarts Ranger KMS Server. |
| ranger-kms-logback | Ranger KMS kms-logback.xml 파일에서 값을 변경합니다. | Not available. |
| ranger-kms-db-ca | Ranger KMS와의 MySQL SSL 연결에서 CA 파일의 값을 변경합니다. | Not available. |
| spark | Apache Spark에 대한 Amazon EMR 큐레이트 설정입니다. | This property modifies spark-defaults. See actions there. |
| spark-defaults | Spark spark-defaults.conf 파일에서 값을 변경합니다. | Restarts Spark history server and Spark thrift server. |
| spark-env | Spark 환경에서 값을 변경합니다. | Restarts Spark history server and Spark thrift server. |
| spark-hive-site | Spark hive-site.xml 파일에서 값을 변경합니다. | Not available. |
| spark-log4j2 | Spark log4j2.properties 파일에서 값을 변경합니다. | Restarts Spark history server and Spark thrift server. |
| spark-metrics | Spark metrics.properties 파일에서 값을 변경합니다. | Restarts Spark history server and Spark thrift server. |
| sqoop-env | Sqoop 환경에서 값을 변경합니다. | Not available. |
| sqoop-oraoop-site | Sqoop OraOop oraoop-site.xml 파일에서 값을 변경합니다. | Not available. |
| sqoop-site | Sqoop sqoop-site.xml 파일에서 값을 변경합니다. | Not available. |
| tez-site | Tez tez-site.xml 파일에서 값을 변경합니다. | Restart Oozie and HiveServer2. |
| yarn-env | YARN 환경에서 값을 변경합니다. | Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts MapReduce-HistoryServer. |
| yarn-site | YARN yarn-site.xml 파일에서 값을 변경합니다. | Restarts the Hadoop YARN services ResourceManager, NodeManager, ProxyServer, and TimelineServer. Additionally restarts Livy Server and MapReduce-HistoryServer. |
| zeppelin-env | Zeppelin 환경에서 값을 변경합니다. | Restarts Zeppelin. |
| zeppelin-site | zeppelin-site.xml에서 구성 설정을 변경합니다. | Restarts Zeppelin. |
| zookeeper-config | ZooKeeper zoo.cfg 파일에서 값을 변경합니다. | Restarts Zookeeper server. |
| zookeeper-log4j | ZooKeeper log4j.properties 파일에서 값을 변경합니다. | Restarts Zookeeper server. |
## 7.0.0 변경 로그
**7.0.0 릴리스 및 릴리스 정보에 대한 변경 로그**
| Date | 이벤트 | 설명 |
| --- | --- | --- |
| 2025-09-03 | 문서 개정 | Amazon EMR 7.0.0 릴리스 정보에 알려진 문제 추가됨 |
| 2023-12-29 | 배포 완료 | 모든 [지원되는 리전](https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/)에 Amazon EMR 7.0.0 전체 배포됨 |
| 2023-12-28 | 문서 게시 | Amazon EMR 7.0.0 릴리스 정보 최초 게시됨 |
| 2023-12-19 | 초기 릴리스 | 최초 상용 리전에 Amazon EMR 7.0.0 최초 배포됨 |