cve-2023-26031
Vulnerability from cvelistv5
Published
2023-11-16 08:15
Modified
2025-02-13 16:44
Severity ?
EPSS score ?
5.59% (0.89396)
Summary
Relative library resolution in linux container-executor binary in Apache Hadoop 3.3.1-3.3.4 on Linux allows local user to gain root privileges. If the YARN cluster is accepting work from remote (authenticated) users, this MAY permit remote users to gain root privileges. Hadoop 3.3.0 updated the " YARN Secure Containers https://hadoop.apache.org/docs/stable/hadoop-yarn/hadoop-yarn-site/SecureContainer.html " to add a feature for executing user-submitted applications in isolated linux containers. The native binary HADOOP_HOME/bin/container-executor is used to launch these containers; it must be owned by root and have the suid bit set in order for the YARN processes to run the containers as the specific users submitting the jobs. The patch " YARN-10495 https://issues.apache.org/jira/browse/YARN-10495 . make the rpath of container-executor configurable" modified the library loading path for loading .so files from "$ORIGIN/" to ""$ORIGIN/:../lib/native/". This is the a path through which libcrypto.so is located. Thus it is is possible for a user with reduced privileges to install a malicious libcrypto library into a path to which they have write access, invoke the container-executor command, and have their modified library executed as root. If the YARN cluster is accepting work from remote (authenticated) users, and these users' submitted job are executed in the physical host, rather than a container, then the CVE permits remote users to gain root privileges. The fix for the vulnerability is to revert the change, which is done in YARN-11441 https://issues.apache.org/jira/browse/YARN-11441 , "Revert YARN-10495". This patch is in hadoop-3.3.5. To determine whether a version of container-executor is vulnerable, use the readelf command. If the RUNPATH or RPATH value contains the relative path "./lib/native/" then it is at risk $ readelf -d container-executor|grep 'RUNPATH\|RPATH' 0x000000000000001d (RUNPATH)           Library runpath: [$ORIGIN/:../lib/native/] If it does not, then it is safe: $ readelf -d container-executor|grep 'RUNPATH\|RPATH' 0x000000000000001d (RUNPATH)           Library runpath: [$ORIGIN/] For an at-risk version of container-executor to enable privilege escalation, the owner must be root and the suid bit must be set $ ls -laF /opt/hadoop/bin/container-executor ---Sr-s---. 1 root hadoop 802968 May 9 20:21 /opt/hadoop/bin/container-executor A safe installation lacks the suid bit; ideally is also not owned by root. $ ls -laF /opt/hadoop/bin/container-executor -rwxr-xr-x. 1 yarn hadoop 802968 May 9 20:21 /opt/hadoop/bin/container-executor This configuration does not support Yarn Secure Containers, but all other hadoop services, including YARN job execution outside secure containers continue to work.
Impacted products
Show details on NVD website


{
   containers: {
      adp: [
         {
            affected: [
               {
                  cpes: [
                     "cpe:2.3:a:apache:hadoop:3.3.1:*:*:*:*:*:*:*",
                  ],
                  defaultStatus: "unaffected",
                  product: "hadoop",
                  vendor: "apache",
                  versions: [
                     {
                        lessThan: "3.3.5",
                        status: "affected",
                        version: "3.3.1",
                        versionType: "semver",
                     },
                  ],
               },
            ],
            metrics: [
               {
                  cvssV3_1: {
                     attackComplexity: "HIGH",
                     attackVector: "NETWORK",
                     availabilityImpact: "HIGH",
                     baseScore: 7.5,
                     baseSeverity: "HIGH",
                     confidentialityImpact: "HIGH",
                     integrityImpact: "HIGH",
                     privilegesRequired: "LOW",
                     scope: "UNCHANGED",
                     userInteraction: "NONE",
                     vectorString: "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H",
                     version: "3.1",
                  },
               },
               {
                  other: {
                     content: {
                        id: "CVE-2023-26031",
                        options: [
                           {
                              Exploitation: "none",
                           },
                           {
                              Automatable: "no",
                           },
                           {
                              "Technical Impact": "total",
                           },
                        ],
                        role: "CISA Coordinator",
                        timestamp: "2024-07-19T03:55:27.490258Z",
                        version: "2.0.3",
                     },
                     type: "ssvc",
                  },
               },
            ],
            providerMetadata: {
               dateUpdated: "2024-07-29T13:09:24.015Z",
               orgId: "134c704f-9b21-4f2e-91b3-4a467353bcc0",
               shortName: "CISA-ADP",
            },
            title: "CISA ADP Vulnrichment",
         },
         {
            providerMetadata: {
               dateUpdated: "2024-08-02T11:39:06.596Z",
               orgId: "af854a3a-2127-422b-91ae-364da2661108",
               shortName: "CVE",
            },
            references: [
               {
                  tags: [
                     "issue-tracking",
                     "x_transferred",
                  ],
                  url: "https://issues.apache.org/jira/browse/YARN-11441",
               },
               {
                  tags: [
                     "vendor-advisory",
                     "x_transferred",
                  ],
                  url: "https://hadoop.apache.org/cve_list.html",
               },
               {
                  tags: [
                     "vendor-advisory",
                     "x_transferred",
                  ],
                  url: "https://lists.apache.org/thread/q9qpdlv952gb4kphpndd5phvl7fkh71r",
               },
               {
                  tags: [
                     "x_transferred",
                  ],
                  url: "https://security.netapp.com/advisory/ntap-20240112-0001/",
               },
            ],
            title: "CVE Program Container",
         },
      ],
      cna: {
         affected: [
            {
               defaultStatus: "unaffected",
               product: "Apache Hadoop",
               vendor: "Apache Software Foundation",
               versions: [
                  {
                     lessThan: "3.3.5",
                     status: "affected",
                     version: "3.3.1",
                     versionType: "semver",
                  },
               ],
            },
         ],
         configurations: [
            {
               lang: "en",
               supportingMedia: [
                  {
                     base64: false,
                     type: "text/html",
                     value: "The owner of the&nbsp;container-executor binary must be set to \"root\" and suid set bit such that callers would execute the binary as root. These operations are a requirement for \"YARN Secure Containers\".<br> <br>In an installation using the hadoop.tar.gz file the binary's owner is that of the installing user, and without the suid permission is not at risk. <br><br>However, Apache BIgtop installations set the owner and permissions such that installations may be vulnerable<br><br>The container-executor&nbsp;binary is only vulnerable on some Hadoop/Bigtop releases. It is possible to verify whether a version is vulnerable using the readelf command.",
                  },
               ],
               value: "The owner of the container-executor binary must be set to \"root\" and suid set bit such that callers would execute the binary as root. These operations are a requirement for \"YARN Secure Containers\".\n \nIn an installation using the hadoop.tar.gz file the binary's owner is that of the installing user, and without the suid permission is not at risk. \n\nHowever, Apache BIgtop installations set the owner and permissions such that installations may be vulnerable\n\nThe container-executor binary is only vulnerable on some Hadoop/Bigtop releases. It is possible to verify whether a version is vulnerable using the readelf command.",
            },
         ],
         credits: [
            {
               lang: "en",
               type: "finder",
               value: "Esa Hiltunen",
            },
            {
               lang: "en",
               type: "finder",
               value: "Mikko Kortelainen",
            },
            {
               lang: "en",
               type: "sponsor",
               value: "The Teragrep Project",
            },
         ],
         descriptions: [
            {
               lang: "en",
               supportingMedia: [
                  {
                     base64: false,
                     type: "text/html",
                     value: "<br>Relative library resolution in linux container-executor binary in Apache Hadoop 3.3.1-3.3.4 on Linux allows local user to gain root privileges. If the YARN cluster is accepting work from remote (authenticated) users, this MAY permit remote users to gain root privileges.<br><br>Hadoop 3.3.0 updated the \"<a target=\"_blank\" rel=\"nofollow\" href=\"https://hadoop.apache.org/docs/stable/hadoop-yarn/hadoop-yarn-site/SecureContainer.html\">YARN Secure Containers</a>\" to add a feature for executing user-submitted applications in isolated linux containers.<br><br>The native binary HADOOP_HOME/bin/container-executor is used to launch these containers; it must be owned by root and have the suid bit set in order for the YARN processes to run the containers as the specific users submitting the jobs.<br><br>The patch \"<a target=\"_blank\" rel=\"nofollow\" href=\"https://issues.apache.org/jira/browse/YARN-10495\">YARN-10495</a>. make the rpath of container-executor configurable\" modified the library loading path for loading .so files from \"$ORIGIN/\" to \"\"$ORIGIN/:../lib/native/\". This is the a path through which libcrypto.so is located. Thus it is is possible for a user with reduced privileges to install a malicious libcrypto library into a path to which they have write access, invoke the container-executor command, and have their modified library executed as root.<br>If the YARN cluster is accepting work from remote (authenticated) users, and these users' submitted job are executed in the physical host, rather than a container, then the CVE permits remote users to gain root privileges.<br><br>The fix for the vulnerability is to revert the change, which is done in <a target=\"_blank\" rel=\"nofollow\" href=\"https://issues.apache.org/jira/browse/YARN-11441\">YARN-11441</a>, \"Revert YARN-10495\". This patch is in hadoop-3.3.5.<br><br>To determine whether a version of container-executor is vulnerable, use the readelf command. If the RUNPATH or RPATH value contains the relative path \"./lib/native/\" then it  is at risk<br><br><tt>$ readelf -d container-executor|grep <span style=\"background-color: rgb(255, 255, 255);\">'RUNPATH\\|RPATH'</span> <br>0x000000000000001d (RUNPATH)  &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Library runpath: [$ORIGIN/:../lib/native/]</tt><br><br>If it does not, then it is safe:<br><br><tt>$ readelf -d container-executor|grep <span style=\"background-color: rgb(255, 255, 255);\">'RUNPATH\\|RPATH'</span> <br>0x000000000000001d (RUNPATH)  &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Library runpath: [$ORIGIN/]</tt><br><br>For an at-risk version of container-executor to enable privilege escalation, the owner must be root and the suid bit must be set<br><tt><br>$ ls -laF /opt/hadoop/bin/container-executor<br>---Sr-s---. 1 root hadoop 802968 May 9 20:21 /opt/hadoop/bin/container-executor</tt><br><br>A safe installation lacks the suid bit; ideally is also not owned by root.<br><br><tt>$ ls -laF /opt/hadoop/bin/container-executor<br>-rwxr-xr-x. 1 yarn hadoop 802968 May 9 20:21 /opt/hadoop/bin/container-executor</tt><br><br>This configuration does not support Yarn Secure Containers, but all other hadoop services, including YARN job execution outside secure containers continue to work.<br><br><br><br><br>",
                  },
               ],
               value: "Relative library resolution in linux container-executor binary in Apache Hadoop 3.3.1-3.3.4 on Linux allows local user to gain root privileges. If the YARN cluster is accepting work from remote (authenticated) users, this MAY permit remote users to gain root privileges.\n\nHadoop 3.3.0 updated the \" YARN Secure Containers https://hadoop.apache.org/docs/stable/hadoop-yarn/hadoop-yarn-site/SecureContainer.html \" to add a feature for executing user-submitted applications in isolated linux containers.\n\nThe native binary HADOOP_HOME/bin/container-executor is used to launch these containers; it must be owned by root and have the suid bit set in order for the YARN processes to run the containers as the specific users submitting the jobs.\n\nThe patch \" YARN-10495 https://issues.apache.org/jira/browse/YARN-10495 . make the rpath of container-executor configurable\" modified the library loading path for loading .so files from \"$ORIGIN/\" to \"\"$ORIGIN/:../lib/native/\". This is the a path through which libcrypto.so is located. Thus it is is possible for a user with reduced privileges to install a malicious libcrypto library into a path to which they have write access, invoke the container-executor command, and have their modified library executed as root.\nIf the YARN cluster is accepting work from remote (authenticated) users, and these users' submitted job are executed in the physical host, rather than a container, then the CVE permits remote users to gain root privileges.\n\nThe fix for the vulnerability is to revert the change, which is done in  YARN-11441 https://issues.apache.org/jira/browse/YARN-11441 , \"Revert YARN-10495\". This patch is in hadoop-3.3.5.\n\nTo determine whether a version of container-executor is vulnerable, use the readelf command. If the RUNPATH or RPATH value contains the relative path \"./lib/native/\" then it  is at risk\n\n$ readelf -d container-executor|grep 'RUNPATH\\|RPATH' \n0x000000000000001d (RUNPATH)            Library runpath: [$ORIGIN/:../lib/native/]\n\nIf it does not, then it is safe:\n\n$ readelf -d container-executor|grep 'RUNPATH\\|RPATH' \n0x000000000000001d (RUNPATH)            Library runpath: [$ORIGIN/]\n\nFor an at-risk version of container-executor to enable privilege escalation, the owner must be root and the suid bit must be set\n\n$ ls -laF /opt/hadoop/bin/container-executor\n---Sr-s---. 1 root hadoop 802968 May 9 20:21 /opt/hadoop/bin/container-executor\n\nA safe installation lacks the suid bit; ideally is also not owned by root.\n\n$ ls -laF /opt/hadoop/bin/container-executor\n-rwxr-xr-x. 1 yarn hadoop 802968 May 9 20:21 /opt/hadoop/bin/container-executor\n\nThis configuration does not support Yarn Secure Containers, but all other hadoop services, including YARN job execution outside secure containers continue to work.",
            },
         ],
         metrics: [
            {
               other: {
                  content: {
                     text: "critical",
                  },
                  type: "Textual description of severity",
               },
            },
         ],
         problemTypes: [
            {
               descriptions: [
                  {
                     cweId: "CWE-426",
                     description: "CWE-426 Untrusted Search Path",
                     lang: "en",
                     type: "CWE",
                  },
               ],
            },
         ],
         providerMetadata: {
            dateUpdated: "2024-01-12T14:06:17.973Z",
            orgId: "f0158376-9dc2-43b6-827c-5f631a4d8d09",
            shortName: "apache",
         },
         references: [
            {
               tags: [
                  "issue-tracking",
               ],
               url: "https://issues.apache.org/jira/browse/YARN-11441",
            },
            {
               tags: [
                  "vendor-advisory",
               ],
               url: "https://hadoop.apache.org/cve_list.html",
            },
            {
               tags: [
                  "vendor-advisory",
               ],
               url: "https://lists.apache.org/thread/q9qpdlv952gb4kphpndd5phvl7fkh71r",
            },
            {
               url: "https://security.netapp.com/advisory/ntap-20240112-0001/",
            },
         ],
         source: {
            defect: [
               "YARN-11441",
            ],
            discovery: "EXTERNAL",
         },
         title: "Privilege escalation in Apache Hadoop Yarn container-executor binary on Linux systems",
         workarounds: [
            {
               lang: "en",
               supportingMedia: [
                  {
                     base64: false,
                     type: "text/html",
                     value: "<ol><li><span style=\"background-color: var(--wht);\">Upgrade to Apache Hadoop 3.3.5</span></li><li><span style=\"background-color: var(--wht);\">If&nbsp;Yarn Secure Containers are not required, remove all execute permissions on bin/container-executor ; change its owner from root, or simply delete it.</span></li><li><span style=\"background-color: var(--wht);\">If Yarn Secure Containers are required on a vulnerable release and upgrade is not possible, replace the container-executor&nbsp;binary with that of the 3.3.5 release.</span><br></li></ol>As most Hadoop installations do not use Yarn Secure Containers, removing execute permissions from the container-executor binary a is sufficient to secure the systems; deletion ensures that no security scanners will report the issue.",
                  },
               ],
               value: "*  Upgrade to Apache Hadoop 3.3.5\n  *  If Yarn Secure Containers are not required, remove all execute permissions on bin/container-executor ; change its owner from root, or simply delete it.\n  *  If Yarn Secure Containers are required on a vulnerable release and upgrade is not possible, replace the container-executor binary with that of the 3.3.5 release.\n\nAs most Hadoop installations do not use Yarn Secure Containers, removing execute permissions from the container-executor binary a is sufficient to secure the systems; deletion ensures that no security scanners will report the issue.",
            },
         ],
         x_generator: {
            engine: "Vulnogram 0.1.0-dev",
         },
      },
   },
   cveMetadata: {
      assignerOrgId: "f0158376-9dc2-43b6-827c-5f631a4d8d09",
      assignerShortName: "apache",
      cveId: "CVE-2023-26031",
      datePublished: "2023-11-16T08:15:50.808Z",
      dateReserved: "2023-02-17T19:39:48.891Z",
      dateUpdated: "2025-02-13T16:44:42.474Z",
      state: "PUBLISHED",
   },
   dataType: "CVE_RECORD",
   dataVersion: "5.1",
   "vulnerability-lookup:meta": {
      nvd: "{\"cve\":{\"id\":\"CVE-2023-26031\",\"sourceIdentifier\":\"security@apache.org\",\"published\":\"2023-11-16T09:15:06.920\",\"lastModified\":\"2025-02-13T17:16:10.793\",\"vulnStatus\":\"Modified\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"Relative library resolution in linux container-executor binary in Apache Hadoop 3.3.1-3.3.4 on Linux allows local user to gain root privileges. If the YARN cluster is accepting work from remote (authenticated) users, this MAY permit remote users to gain root privileges.\\n\\nHadoop 3.3.0 updated the \\\" YARN Secure Containers https://hadoop.apache.org/docs/stable/hadoop-yarn/hadoop-yarn-site/SecureContainer.html \\\" to add a feature for executing user-submitted applications in isolated linux containers.\\n\\nThe native binary HADOOP_HOME/bin/container-executor is used to launch these containers; it must be owned by root and have the suid bit set in order for the YARN processes to run the containers as the specific users submitting the jobs.\\n\\nThe patch \\\" YARN-10495 https://issues.apache.org/jira/browse/YARN-10495 . make the rpath of container-executor configurable\\\" modified the library loading path for loading .so files from \\\"$ORIGIN/\\\" to \\\"\\\"$ORIGIN/:../lib/native/\\\". This is the a path through which libcrypto.so is located. Thus it is is possible for a user with reduced privileges to install a malicious libcrypto library into a path to which they have write access, invoke the container-executor command, and have their modified library executed as root.\\nIf the YARN cluster is accepting work from remote (authenticated) users, and these users' submitted job are executed in the physical host, rather than a container, then the CVE permits remote users to gain root privileges.\\n\\nThe fix for the vulnerability is to revert the change, which is done in  YARN-11441 https://issues.apache.org/jira/browse/YARN-11441 , \\\"Revert YARN-10495\\\". This patch is in hadoop-3.3.5.\\n\\nTo determine whether a version of container-executor is vulnerable, use the readelf command. If the RUNPATH or RPATH value contains the relative path \\\"./lib/native/\\\" then it  is at risk\\n\\n$ readelf -d container-executor|grep 'RUNPATH\\\\|RPATH' \\n0x000000000000001d (RUNPATH)            Library runpath: [$ORIGIN/:../lib/native/]\\n\\nIf it does not, then it is safe:\\n\\n$ readelf -d container-executor|grep 'RUNPATH\\\\|RPATH' \\n0x000000000000001d (RUNPATH)            Library runpath: [$ORIGIN/]\\n\\nFor an at-risk version of container-executor to enable privilege escalation, the owner must be root and the suid bit must be set\\n\\n$ ls -laF /opt/hadoop/bin/container-executor\\n---Sr-s---. 1 root hadoop 802968 May 9 20:21 /opt/hadoop/bin/container-executor\\n\\nA safe installation lacks the suid bit; ideally is also not owned by root.\\n\\n$ ls -laF /opt/hadoop/bin/container-executor\\n-rwxr-xr-x. 1 yarn hadoop 802968 May 9 20:21 /opt/hadoop/bin/container-executor\\n\\nThis configuration does not support Yarn Secure Containers, but all other hadoop services, including YARN job execution outside secure containers continue to work.\"},{\"lang\":\"es\",\"value\":\"La resolución relativa de la librería en el binario contenedor-ejecutor de Linux en Apache Hadoop 3.3.1-3.3.4 en Linux permite al usuario local obtener privilegios de root. Si el clúster YARN acepta trabajo de usuarios remotos (autenticados), esto PUEDE permitir que los usuarios remotos obtengan privilegios de root. Hadoop 3.3.0 actualizó \\\" YARN Secure Containers https://hadoop.apache.org/docs/stable/hadoop-yarn/hadoop-yarn-site/SecureContainer.html \\\" para agregar una función para ejecutar aplicaciones enviadas por el usuario de forma aislada contenedores de Linux. El binario nativo HADOOP_HOME/bin/container-executor se utiliza para lanzar estos contenedores; debe ser propiedad de root y tener el bit suid configurado para que los procesos YARN ejecuten los contenedores como los usuarios específicos que envían los trabajos. El parche \\\"YARN-10495 https://issues.apache.org/jira/browse/YARN-10495. make the rpath of container-executor configurable\\\" modificó la ruta de carga de la librería para cargar archivos .so de \\\"$ORIGIN/\\\" a \\\"\\\"$ORIGIN/:../lib/native/\\\". Esta es la ruta a través de la cual se encuentra libcrypto.so. Por lo tanto, es posible que un usuario con privilegios reducidos instale una librería libcrypto maliciosa en una ruta a la que tienen acceso de escritura, invocan el comando contenedor-ejecutor y ejecutan su librería modificada como root. Si el clúster YARN acepta trabajo de usuarios remotos (autenticados) y el trabajo enviado por estos usuarios se ejecuta en el host físico, en lugar de un contenedor, entonces el CVE permite a los usuarios remotos obtener privilegios de root. La solución para la vulnerabilidad es revertir el cambio, lo cual se realiza en YARN-11441 https://issues.apache.org/jira/browse/YARN-11441, \\\"Revertir YARN-10495\\\". Este parche está en hadoop-3.3.5. Para determinar si una versión de container-executor es vulnerable, utilice el comando readelf. Si el valor RUNPATH o RPATH contiene la ruta relativa \\\"./lib/native/\\\", entonces está en riesgo $ readelf -d container-executor|grep 'RUNPATH\\\\|RPATH' 0x0000000000000001d (RUNPATH) Ruta de ejecución de la librería: [$ORIGIN/: ../lib/native/] Si no es así, entonces es seguro: $ readelf -d container-executor|grep 'RUNPATH\\\\|RPATH' 0x000000000000001d (RUNPATH) Ruta de ejecución de la librería: [$ORIGIN/] Para un sitio en riesgo versión de container-executor para habilitar la escalada de privilegios, el propietario debe ser root y el bit suid debe estar configurado $ ls -laF /opt/hadoop/bin/container-executor ---Sr-s---. 1 root hadoop 802968 9 de mayo 20:21 /opt/hadoop/bin/container-executor Una instalación segura carece del bit suid; Lo ideal es que tampoco sea propiedad de root. $ ls -laF /opt/hadoop/bin/container-executor -rwxr-xr-x. 1 hilo hadoop 802968 9 de mayo 20:21 /opt/hadoop/bin/container-executor Esta configuración no admite Contenedores Seguros Yarn, pero todos los demás servicios de hadoop, incluida la ejecución de trabajos YARN fuera de contenedores seguros, continúan funcionando.\"}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H\",\"baseScore\":7.5,\"baseSeverity\":\"HIGH\",\"attackVector\":\"NETWORK\",\"attackComplexity\":\"HIGH\",\"privilegesRequired\":\"LOW\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"HIGH\",\"integrityImpact\":\"HIGH\",\"availabilityImpact\":\"HIGH\"},\"exploitabilityScore\":1.6,\"impactScore\":5.9},{\"source\":\"134c704f-9b21-4f2e-91b3-4a467353bcc0\",\"type\":\"Secondary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H\",\"baseScore\":7.5,\"baseSeverity\":\"HIGH\",\"attackVector\":\"NETWORK\",\"attackComplexity\":\"HIGH\",\"privilegesRequired\":\"LOW\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"HIGH\",\"integrityImpact\":\"HIGH\",\"availabilityImpact\":\"HIGH\"},\"exploitabilityScore\":1.6,\"impactScore\":5.9}]},\"weaknesses\":[{\"source\":\"security@apache.org\",\"type\":\"Secondary\",\"description\":[{\"lang\":\"en\",\"value\":\"CWE-426\"}]},{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"description\":[{\"lang\":\"en\",\"value\":\"CWE-426\"}]}],\"configurations\":[{\"nodes\":[{\"operator\":\"OR\",\"negate\":false,\"cpeMatch\":[{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:apache:hadoop:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"3.3.1\",\"versionEndIncluding\":\"3.3.4\",\"matchCriteriaId\":\"D701B179-FF46-4C12-8258-350936106618\"}]}]}],\"references\":[{\"url\":\"https://hadoop.apache.org/cve_list.html\",\"source\":\"security@apache.org\",\"tags\":[\"Vendor Advisory\"]},{\"url\":\"https://issues.apache.org/jira/browse/YARN-11441\",\"source\":\"security@apache.org\",\"tags\":[\"Issue Tracking\",\"Vendor Advisory\"]},{\"url\":\"https://lists.apache.org/thread/q9qpdlv952gb4kphpndd5phvl7fkh71r\",\"source\":\"security@apache.org\",\"tags\":[\"Mailing List\",\"Vendor Advisory\"]},{\"url\":\"https://security.netapp.com/advisory/ntap-20240112-0001/\",\"source\":\"security@apache.org\"},{\"url\":\"https://hadoop.apache.org/cve_list.html\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\",\"tags\":[\"Vendor Advisory\"]},{\"url\":\"https://issues.apache.org/jira/browse/YARN-11441\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\",\"tags\":[\"Issue Tracking\",\"Vendor Advisory\"]},{\"url\":\"https://lists.apache.org/thread/q9qpdlv952gb4kphpndd5phvl7fkh71r\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\",\"tags\":[\"Mailing List\",\"Vendor Advisory\"]},{\"url\":\"https://security.netapp.com/advisory/ntap-20240112-0001/\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\"}]}}",
      vulnrichment: {
         containers: "{\"adp\": [{\"title\": \"CVE Program Container\", \"references\": [{\"url\": \"https://issues.apache.org/jira/browse/YARN-11441\", \"tags\": [\"issue-tracking\", \"x_transferred\"]}, {\"url\": \"https://hadoop.apache.org/cve_list.html\", \"tags\": [\"vendor-advisory\", \"x_transferred\"]}, {\"url\": \"https://lists.apache.org/thread/q9qpdlv952gb4kphpndd5phvl7fkh71r\", \"tags\": [\"vendor-advisory\", \"x_transferred\"]}, {\"url\": \"https://security.netapp.com/advisory/ntap-20240112-0001/\", \"tags\": [\"x_transferred\"]}], \"providerMetadata\": {\"orgId\": \"af854a3a-2127-422b-91ae-364da2661108\", \"shortName\": \"CVE\", \"dateUpdated\": \"2024-08-02T11:39:06.596Z\"}}, {\"title\": \"CISA ADP Vulnrichment\", \"metrics\": [{\"cvssV3_1\": {\"scope\": \"UNCHANGED\", \"version\": \"3.1\", \"baseScore\": 7.5, \"attackVector\": \"NETWORK\", \"baseSeverity\": \"HIGH\", \"vectorString\": \"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H\", \"integrityImpact\": \"HIGH\", \"userInteraction\": \"NONE\", \"attackComplexity\": \"HIGH\", \"availabilityImpact\": \"HIGH\", \"privilegesRequired\": \"LOW\", \"confidentialityImpact\": \"HIGH\"}}, {\"other\": {\"type\": \"ssvc\", \"content\": {\"id\": \"CVE-2023-26031\", \"role\": \"CISA Coordinator\", \"options\": [{\"Exploitation\": \"none\"}, {\"Automatable\": \"no\"}, {\"Technical Impact\": \"total\"}], \"version\": \"2.0.3\", \"timestamp\": \"2024-07-19T03:55:27.490258Z\"}}}], \"affected\": [{\"cpes\": [\"cpe:2.3:a:apache:hadoop:3.3.1:*:*:*:*:*:*:*\"], \"vendor\": \"apache\", \"product\": \"hadoop\", \"versions\": [{\"status\": \"affected\", \"version\": \"3.3.1\", \"lessThan\": \"3.3.5\", \"versionType\": \"semver\"}], \"defaultStatus\": \"unaffected\"}], \"providerMetadata\": {\"orgId\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"shortName\": \"CISA-ADP\", \"dateUpdated\": \"2024-07-29T13:09:19.834Z\"}}], \"cna\": {\"title\": \"Privilege escalation in Apache Hadoop Yarn container-executor binary on Linux systems\", \"source\": {\"defect\": [\"YARN-11441\"], \"discovery\": \"EXTERNAL\"}, \"credits\": [{\"lang\": \"en\", \"type\": \"finder\", \"value\": \"Esa Hiltunen\"}, {\"lang\": \"en\", \"type\": \"finder\", \"value\": \"Mikko Kortelainen\"}, {\"lang\": \"en\", \"type\": \"sponsor\", \"value\": \"The Teragrep Project\"}], \"metrics\": [{\"other\": {\"type\": \"Textual description of severity\", \"content\": {\"text\": \"critical\"}}}], \"affected\": [{\"vendor\": \"Apache Software Foundation\", \"product\": \"Apache Hadoop\", \"versions\": [{\"status\": \"affected\", \"version\": \"3.3.1\", \"lessThan\": \"3.3.5\", \"versionType\": \"semver\"}], \"defaultStatus\": \"unaffected\"}], \"references\": [{\"url\": \"https://issues.apache.org/jira/browse/YARN-11441\", \"tags\": [\"issue-tracking\"]}, {\"url\": \"https://hadoop.apache.org/cve_list.html\", \"tags\": [\"vendor-advisory\"]}, {\"url\": \"https://lists.apache.org/thread/q9qpdlv952gb4kphpndd5phvl7fkh71r\", \"tags\": [\"vendor-advisory\"]}, {\"url\": \"https://security.netapp.com/advisory/ntap-20240112-0001/\"}], \"workarounds\": [{\"lang\": \"en\", \"value\": \"*  Upgrade to Apache Hadoop 3.3.5\\n  *  If\\u00a0Yarn Secure Containers are not required, remove all execute permissions on bin/container-executor ; change its owner from root, or simply delete it.\\n  *  If Yarn Secure Containers are required on a vulnerable release and upgrade is not possible, replace the container-executor\\u00a0binary with that of the 3.3.5 release.\\n\\nAs most Hadoop installations do not use Yarn Secure Containers, removing execute permissions from the container-executor binary a is sufficient to secure the systems; deletion ensures that no security scanners will report the issue.\", \"supportingMedia\": [{\"type\": \"text/html\", \"value\": \"<ol><li><span style=\\\"background-color: var(--wht);\\\">Upgrade to Apache Hadoop 3.3.5</span></li><li><span style=\\\"background-color: var(--wht);\\\">If&nbsp;Yarn Secure Containers are not required, remove all execute permissions on bin/container-executor ; change its owner from root, or simply delete it.</span></li><li><span style=\\\"background-color: var(--wht);\\\">If Yarn Secure Containers are required on a vulnerable release and upgrade is not possible, replace the container-executor&nbsp;binary with that of the 3.3.5 release.</span><br></li></ol>As most Hadoop installations do not use Yarn Secure Containers, removing execute permissions from the container-executor binary a is sufficient to secure the systems; deletion ensures that no security scanners will report the issue.\", \"base64\": false}]}], \"x_generator\": {\"engine\": \"Vulnogram 0.1.0-dev\"}, \"descriptions\": [{\"lang\": \"en\", \"value\": \"Relative library resolution in linux container-executor binary in Apache Hadoop 3.3.1-3.3.4 on Linux allows local user to gain root privileges. If the YARN cluster is accepting work from remote (authenticated) users, this MAY permit remote users to gain root privileges.\\n\\nHadoop 3.3.0 updated the \\\" YARN Secure Containers https://hadoop.apache.org/docs/stable/hadoop-yarn/hadoop-yarn-site/SecureContainer.html \\\" to add a feature for executing user-submitted applications in isolated linux containers.\\n\\nThe native binary HADOOP_HOME/bin/container-executor is used to launch these containers; it must be owned by root and have the suid bit set in order for the YARN processes to run the containers as the specific users submitting the jobs.\\n\\nThe patch \\\" YARN-10495 https://issues.apache.org/jira/browse/YARN-10495 . make the rpath of container-executor configurable\\\" modified the library loading path for loading .so files from \\\"$ORIGIN/\\\" to \\\"\\\"$ORIGIN/:../lib/native/\\\". This is the a path through which libcrypto.so is located. Thus it is is possible for a user with reduced privileges to install a malicious libcrypto library into a path to which they have write access, invoke the container-executor command, and have their modified library executed as root.\\nIf the YARN cluster is accepting work from remote (authenticated) users, and these users' submitted job are executed in the physical host, rather than a container, then the CVE permits remote users to gain root privileges.\\n\\nThe fix for the vulnerability is to revert the change, which is done in  YARN-11441 https://issues.apache.org/jira/browse/YARN-11441 , \\\"Revert YARN-10495\\\". This patch is in hadoop-3.3.5.\\n\\nTo determine whether a version of container-executor is vulnerable, use the readelf command. If the RUNPATH or RPATH value contains the relative path \\\"./lib/native/\\\" then it  is at risk\\n\\n$ readelf -d container-executor|grep 'RUNPATH\\\\|RPATH' \\n0x000000000000001d (RUNPATH)  \\u00a0 \\u00a0 \\u00a0 \\u00a0 \\u00a0 Library runpath: [$ORIGIN/:../lib/native/]\\n\\nIf it does not, then it is safe:\\n\\n$ readelf -d container-executor|grep 'RUNPATH\\\\|RPATH' \\n0x000000000000001d (RUNPATH)  \\u00a0 \\u00a0 \\u00a0 \\u00a0 \\u00a0 Library runpath: [$ORIGIN/]\\n\\nFor an at-risk version of container-executor to enable privilege escalation, the owner must be root and the suid bit must be set\\n\\n$ ls -laF /opt/hadoop/bin/container-executor\\n---Sr-s---. 1 root hadoop 802968 May 9 20:21 /opt/hadoop/bin/container-executor\\n\\nA safe installation lacks the suid bit; ideally is also not owned by root.\\n\\n$ ls -laF /opt/hadoop/bin/container-executor\\n-rwxr-xr-x. 1 yarn hadoop 802968 May 9 20:21 /opt/hadoop/bin/container-executor\\n\\nThis configuration does not support Yarn Secure Containers, but all other hadoop services, including YARN job execution outside secure containers continue to work.\", \"supportingMedia\": [{\"type\": \"text/html\", \"value\": \"<br>Relative library resolution in linux container-executor binary in Apache Hadoop 3.3.1-3.3.4 on Linux allows local user to gain root privileges. If the YARN cluster is accepting work from remote (authenticated) users, this MAY permit remote users to gain root privileges.<br><br>Hadoop 3.3.0 updated the \\\"<a target=\\\"_blank\\\" rel=\\\"nofollow\\\" href=\\\"https://hadoop.apache.org/docs/stable/hadoop-yarn/hadoop-yarn-site/SecureContainer.html\\\">YARN Secure Containers</a>\\\" to add a feature for executing user-submitted applications in isolated linux containers.<br><br>The native binary HADOOP_HOME/bin/container-executor is used to launch these containers; it must be owned by root and have the suid bit set in order for the YARN processes to run the containers as the specific users submitting the jobs.<br><br>The patch \\\"<a target=\\\"_blank\\\" rel=\\\"nofollow\\\" href=\\\"https://issues.apache.org/jira/browse/YARN-10495\\\">YARN-10495</a>. make the rpath of container-executor configurable\\\" modified the library loading path for loading .so files from \\\"$ORIGIN/\\\" to \\\"\\\"$ORIGIN/:../lib/native/\\\". This is the a path through which libcrypto.so is located. Thus it is is possible for a user with reduced privileges to install a malicious libcrypto library into a path to which they have write access, invoke the container-executor command, and have their modified library executed as root.<br>If the YARN cluster is accepting work from remote (authenticated) users, and these users' submitted job are executed in the physical host, rather than a container, then the CVE permits remote users to gain root privileges.<br><br>The fix for the vulnerability is to revert the change, which is done in <a target=\\\"_blank\\\" rel=\\\"nofollow\\\" href=\\\"https://issues.apache.org/jira/browse/YARN-11441\\\">YARN-11441</a>, \\\"Revert YARN-10495\\\". This patch is in hadoop-3.3.5.<br><br>To determine whether a version of container-executor is vulnerable, use the readelf command. If the RUNPATH or RPATH value contains the relative path \\\"./lib/native/\\\" then it  is at risk<br><br><tt>$ readelf -d container-executor|grep <span style=\\\"background-color: rgb(255, 255, 255);\\\">'RUNPATH\\\\|RPATH'</span> <br>0x000000000000001d (RUNPATH)  &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Library runpath: [$ORIGIN/:../lib/native/]</tt><br><br>If it does not, then it is safe:<br><br><tt>$ readelf -d container-executor|grep <span style=\\\"background-color: rgb(255, 255, 255);\\\">'RUNPATH\\\\|RPATH'</span> <br>0x000000000000001d (RUNPATH)  &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Library runpath: [$ORIGIN/]</tt><br><br>For an at-risk version of container-executor to enable privilege escalation, the owner must be root and the suid bit must be set<br><tt><br>$ ls -laF /opt/hadoop/bin/container-executor<br>---Sr-s---. 1 root hadoop 802968 May 9 20:21 /opt/hadoop/bin/container-executor</tt><br><br>A safe installation lacks the suid bit; ideally is also not owned by root.<br><br><tt>$ ls -laF /opt/hadoop/bin/container-executor<br>-rwxr-xr-x. 1 yarn hadoop 802968 May 9 20:21 /opt/hadoop/bin/container-executor</tt><br><br>This configuration does not support Yarn Secure Containers, but all other hadoop services, including YARN job execution outside secure containers continue to work.<br><br><br><br><br>\", \"base64\": false}]}], \"problemTypes\": [{\"descriptions\": [{\"lang\": \"en\", \"type\": \"CWE\", \"cweId\": \"CWE-426\", \"description\": \"CWE-426 Untrusted Search Path\"}]}], \"configurations\": [{\"lang\": \"en\", \"value\": \"The owner of the\\u00a0container-executor binary must be set to \\\"root\\\" and suid set bit such that callers would execute the binary as root. These operations are a requirement for \\\"YARN Secure Containers\\\".\\n \\nIn an installation using the hadoop.tar.gz file the binary's owner is that of the installing user, and without the suid permission is not at risk. \\n\\nHowever, Apache BIgtop installations set the owner and permissions such that installations may be vulnerable\\n\\nThe container-executor\\u00a0binary is only vulnerable on some Hadoop/Bigtop releases. It is possible to verify whether a version is vulnerable using the readelf command.\", \"supportingMedia\": [{\"type\": \"text/html\", \"value\": \"The owner of the&nbsp;container-executor binary must be set to \\\"root\\\" and suid set bit such that callers would execute the binary as root. These operations are a requirement for \\\"YARN Secure Containers\\\".<br> <br>In an installation using the hadoop.tar.gz file the binary's owner is that of the installing user, and without the suid permission is not at risk. <br><br>However, Apache BIgtop installations set the owner and permissions such that installations may be vulnerable<br><br>The container-executor&nbsp;binary is only vulnerable on some Hadoop/Bigtop releases. It is possible to verify whether a version is vulnerable using the readelf command.\", \"base64\": false}]}], \"providerMetadata\": {\"orgId\": \"f0158376-9dc2-43b6-827c-5f631a4d8d09\", \"shortName\": \"apache\", \"dateUpdated\": \"2024-01-12T14:06:17.973Z\"}}}",
         cveMetadata: "{\"cveId\": \"CVE-2023-26031\", \"state\": \"PUBLISHED\", \"dateUpdated\": \"2025-02-13T16:44:42.474Z\", \"dateReserved\": \"2023-02-17T19:39:48.891Z\", \"assignerOrgId\": \"f0158376-9dc2-43b6-827c-5f631a4d8d09\", \"datePublished\": \"2023-11-16T08:15:50.808Z\", \"assignerShortName\": \"apache\"}",
         dataType: "CVE_RECORD",
         dataVersion: "5.1",
      },
   },
}


Log in or create an account to share your comment.

Security Advisory comment format.

This schema specifies the format of a comment related to a security advisory.

UUIDv4 of the comment
UUIDv4 of the Vulnerability-Lookup instance
When the comment was created originally
When the comment was last updated
Title of the comment
Description of the comment
The identifier of the vulnerability (CVE ID, GHSA-ID, PYSEC ID, etc.).



Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.