cve-2023-46842
Vulnerability from cvelistv5
Published
2024-05-16 13:39
Modified
2024-12-04 16:57
EPSS score ?
0.10% (0.24414)
Summary
Unlike 32-bit PV guests, HVM guests may switch freely between 64-bit and other modes. This in particular means that they may set registers used to pass 32-bit-mode hypercall arguments to values outside of the range 32-bit code would be able to set them to. When processing of hypercalls takes a considerable amount of time, the hypervisor may choose to invoke a hypercall continuation. Doing so involves putting (perhaps updated) hypercall arguments in respective registers. For guests not running in 64-bit mode this further involves a certain amount of translation of the values. Unfortunately internal sanity checking of these translated values assumes high halves of registers to always be clear when invoking a hypercall. When this is found not to be the case, it triggers a consistency check in the hypervisor and causes a crash.
Impacted products
Show details on NVD website


{
   containers: {
      adp: [
         {
            metrics: [
               {
                  cvssV3_1: {
                     attackComplexity: "LOW",
                     attackVector: "LOCAL",
                     availabilityImpact: "HIGH",
                     baseScore: 6.5,
                     baseSeverity: "MEDIUM",
                     confidentialityImpact: "NONE",
                     integrityImpact: "NONE",
                     privilegesRequired: "LOW",
                     scope: "CHANGED",
                     userInteraction: "NONE",
                     vectorString: "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H",
                     version: "3.1",
                  },
               },
               {
                  other: {
                     content: {
                        id: "CVE-2023-46842",
                        options: [
                           {
                              Exploitation: "none",
                           },
                           {
                              Automatable: "no",
                           },
                           {
                              "Technical Impact": "partial",
                           },
                        ],
                        role: "CISA Coordinator",
                        timestamp: "2024-05-24T18:23:20.820059Z",
                        version: "2.0.3",
                     },
                     type: "ssvc",
                  },
               },
            ],
            problemTypes: [
               {
                  descriptions: [
                     {
                        cweId: "CWE-843",
                        description: "CWE-843 Access of Resource Using Incompatible Type ('Type Confusion')",
                        lang: "en",
                        type: "CWE",
                     },
                  ],
               },
            ],
            providerMetadata: {
               dateUpdated: "2024-12-04T16:57:56.599Z",
               orgId: "134c704f-9b21-4f2e-91b3-4a467353bcc0",
               shortName: "CISA-ADP",
            },
            title: "CISA ADP Vulnrichment",
         },
         {
            providerMetadata: {
               dateUpdated: "2024-08-02T20:53:21.979Z",
               orgId: "af854a3a-2127-422b-91ae-364da2661108",
               shortName: "CVE",
            },
            references: [
               {
                  tags: [
                     "x_transferred",
                  ],
                  url: "https://xenbits.xenproject.org/xsa/advisory-454.html",
               },
            ],
            title: "CVE Program Container",
         },
      ],
      cna: {
         affected: [
            {
               defaultStatus: "unknown",
               product: "Xen",
               vendor: "Xen",
               versions: [
                  {
                     status: "unknown",
                     version: "consult Xen advisory XSA-454",
                  },
               ],
            },
         ],
         configurations: [
            {
               lang: "en",
               value: "All Xen versions from at least 3.2 onwards are vulnerable.  Earlier\nversions have not been inspected.\n\nOnly x86 systems are vulnerable.  Arm systems are not vulnerable.\n\nOnly HVM or PVH guests can leverage the vulnerability.  PV guests cannot\nleverage the vulnerability.\n",
            },
         ],
         credits: [
            {
               lang: "en",
               type: "finder",
               value: "This issue was discovered by Manuel Andreas of Technical University of\nMunich.\n",
            },
         ],
         datePublic: "2024-04-09T11:50:00Z",
         descriptions: [
            {
               lang: "en",
               value: "Unlike 32-bit PV guests, HVM guests may switch freely between 64-bit and\nother modes.  This in particular means that they may set registers used\nto pass 32-bit-mode hypercall arguments to values outside of the range\n32-bit code would be able to set them to.\n\nWhen processing of hypercalls takes a considerable amount of time,\nthe hypervisor may choose to invoke a hypercall continuation.  Doing so\ninvolves putting (perhaps updated) hypercall arguments in respective\nregisters.  For guests not running in 64-bit mode this further involves\na certain amount of translation of the values.\n\nUnfortunately internal sanity checking of these translated values\nassumes high halves of registers to always be clear when invoking a\nhypercall.  When this is found not to be the case, it triggers a\nconsistency check in the hypervisor and causes a crash.\n",
            },
         ],
         impacts: [
            {
               descriptions: [
                  {
                     lang: "en",
                     value: "A HVM or PVH guest can cause a hypervisor crash, causing a Denial of\nService (DoS) of the entire host.\n",
                  },
               ],
            },
         ],
         providerMetadata: {
            dateUpdated: "2024-05-16T13:39:26.183Z",
            orgId: "23aa2041-22e1-471f-9209-9b7396fa234f",
            shortName: "XEN",
         },
         references: [
            {
               url: "https://xenbits.xenproject.org/xsa/advisory-454.html",
            },
         ],
         title: "x86 HVM hypercalls may trigger Xen bug check",
         workarounds: [
            {
               lang: "en",
               value: "Not using HVM / PVH guests will avoid the vulnerability.\n",
            },
         ],
      },
   },
   cveMetadata: {
      assignerOrgId: "23aa2041-22e1-471f-9209-9b7396fa234f",
      assignerShortName: "XEN",
      cveId: "CVE-2023-46842",
      datePublished: "2024-05-16T13:39:26.183Z",
      dateReserved: "2023-10-27T07:55:35.333Z",
      dateUpdated: "2024-12-04T16:57:56.599Z",
      state: "PUBLISHED",
   },
   dataType: "CVE_RECORD",
   dataVersion: "5.1",
   "vulnerability-lookup:meta": {
      fkie_nvd: {
         descriptions: "[{\"lang\": \"en\", \"value\": \"Unlike 32-bit PV guests, HVM guests may switch freely between 64-bit and\\nother modes.  This in particular means that they may set registers used\\nto pass 32-bit-mode hypercall arguments to values outside of the range\\n32-bit code would be able to set them to.\\n\\nWhen processing of hypercalls takes a considerable amount of time,\\nthe hypervisor may choose to invoke a hypercall continuation.  Doing so\\ninvolves putting (perhaps updated) hypercall arguments in respective\\nregisters.  For guests not running in 64-bit mode this further involves\\na certain amount of translation of the values.\\n\\nUnfortunately internal sanity checking of these translated values\\nassumes high halves of registers to always be clear when invoking a\\nhypercall.  When this is found not to be the case, it triggers a\\nconsistency check in the hypervisor and causes a crash.\\n\"}, {\"lang\": \"es\", \"value\": \"A diferencia de los hu\\u00e9spedes PV de 32 bits, los hu\\u00e9spedes HVM pueden cambiar libremente entre 64 bits y otros modos. Esto significa en particular que pueden configurar los registros utilizados para pasar argumentos de hiperllamada en modo de 32 bits a valores fuera del rango en el que el c\\u00f3digo de 32 bits podr\\u00eda configurarlos. Cuando el procesamiento de hiperllamadas toma una cantidad considerable de tiempo, el hipervisor puede optar por invocar una continuaci\\u00f3n de hiperllamada. Hacerlo implica colocar argumentos de hiperllamada (quiz\\u00e1s actualizados) en los registros respectivos. Para los hu\\u00e9spedes que no se ejecutan en modo de 64 bits, esto implica adem\\u00e1s una cierta cantidad de traducci\\u00f3n de los valores. Desafortunadamente, la comprobaci\\u00f3n de cordura interna de estos valores traducidos supone que las mitades altas de los registros siempre est\\u00e1n limpias al invocar una hiperllamada. Cuando se descubre que este no es el caso, se activa una comprobaci\\u00f3n de coherencia en el hipervisor y se produce un bloqueo.\"}]",
         id: "CVE-2023-46842",
         lastModified: "2024-12-04T17:15:11.343",
         metrics: "{\"cvssMetricV31\": [{\"source\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"type\": \"Secondary\", \"cvssData\": {\"version\": \"3.1\", \"vectorString\": \"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H\", \"baseScore\": 6.5, \"baseSeverity\": \"MEDIUM\", \"attackVector\": \"LOCAL\", \"attackComplexity\": \"LOW\", \"privilegesRequired\": \"LOW\", \"userInteraction\": \"NONE\", \"scope\": \"CHANGED\", \"confidentialityImpact\": \"NONE\", \"integrityImpact\": \"NONE\", \"availabilityImpact\": \"HIGH\"}, \"exploitabilityScore\": 2.0, \"impactScore\": 4.0}]}",
         published: "2024-05-16T14:15:08.317",
         references: "[{\"url\": \"https://xenbits.xenproject.org/xsa/advisory-454.html\", \"source\": \"security@xen.org\"}, {\"url\": \"https://xenbits.xenproject.org/xsa/advisory-454.html\", \"source\": \"af854a3a-2127-422b-91ae-364da2661108\"}]",
         sourceIdentifier: "security@xen.org",
         vulnStatus: "Awaiting Analysis",
         weaknesses: "[{\"source\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"type\": \"Secondary\", \"description\": [{\"lang\": \"en\", \"value\": \"CWE-843\"}]}]",
      },
      nvd: "{\"cve\":{\"id\":\"CVE-2023-46842\",\"sourceIdentifier\":\"security@xen.org\",\"published\":\"2024-05-16T14:15:08.317\",\"lastModified\":\"2024-12-04T17:15:11.343\",\"vulnStatus\":\"Awaiting Analysis\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"Unlike 32-bit PV guests, HVM guests may switch freely between 64-bit and\\nother modes.  This in particular means that they may set registers used\\nto pass 32-bit-mode hypercall arguments to values outside of the range\\n32-bit code would be able to set them to.\\n\\nWhen processing of hypercalls takes a considerable amount of time,\\nthe hypervisor may choose to invoke a hypercall continuation.  Doing so\\ninvolves putting (perhaps updated) hypercall arguments in respective\\nregisters.  For guests not running in 64-bit mode this further involves\\na certain amount of translation of the values.\\n\\nUnfortunately internal sanity checking of these translated values\\nassumes high halves of registers to always be clear when invoking a\\nhypercall.  When this is found not to be the case, it triggers a\\nconsistency check in the hypervisor and causes a crash.\\n\"},{\"lang\":\"es\",\"value\":\"A diferencia de los huéspedes PV de 32 bits, los huéspedes HVM pueden cambiar libremente entre 64 bits y otros modos. Esto significa en particular que pueden configurar los registros utilizados para pasar argumentos de hiperllamada en modo de 32 bits a valores fuera del rango en el que el código de 32 bits podría configurarlos. Cuando el procesamiento de hiperllamadas toma una cantidad considerable de tiempo, el hipervisor puede optar por invocar una continuación de hiperllamada. Hacerlo implica colocar argumentos de hiperllamada (quizás actualizados) en los registros respectivos. Para los huéspedes que no se ejecutan en modo de 64 bits, esto implica además una cierta cantidad de traducción de los valores. Desafortunadamente, la comprobación de cordura interna de estos valores traducidos supone que las mitades altas de los registros siempre están limpias al invocar una hiperllamada. Cuando se descubre que este no es el caso, se activa una comprobación de coherencia en el hipervisor y se produce un bloqueo.\"}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"134c704f-9b21-4f2e-91b3-4a467353bcc0\",\"type\":\"Secondary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H\",\"baseScore\":6.5,\"baseSeverity\":\"MEDIUM\",\"attackVector\":\"LOCAL\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"LOW\",\"userInteraction\":\"NONE\",\"scope\":\"CHANGED\",\"confidentialityImpact\":\"NONE\",\"integrityImpact\":\"NONE\",\"availabilityImpact\":\"HIGH\"},\"exploitabilityScore\":2.0,\"impactScore\":4.0}]},\"weaknesses\":[{\"source\":\"134c704f-9b21-4f2e-91b3-4a467353bcc0\",\"type\":\"Secondary\",\"description\":[{\"lang\":\"en\",\"value\":\"CWE-843\"}]}],\"references\":[{\"url\":\"https://xenbits.xenproject.org/xsa/advisory-454.html\",\"source\":\"security@xen.org\"},{\"url\":\"https://xenbits.xenproject.org/xsa/advisory-454.html\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\"}]}}",
      vulnrichment: {
         containers: "{\"adp\": [{\"title\": \"CVE Program Container\", \"references\": [{\"url\": \"https://xenbits.xenproject.org/xsa/advisory-454.html\", \"tags\": [\"x_transferred\"]}], \"providerMetadata\": {\"orgId\": \"af854a3a-2127-422b-91ae-364da2661108\", \"shortName\": \"CVE\", \"dateUpdated\": \"2024-08-02T20:53:21.979Z\"}}, {\"title\": \"CISA ADP Vulnrichment\", \"metrics\": [{\"cvssV3_1\": {\"scope\": \"CHANGED\", \"version\": \"3.1\", \"baseScore\": 6.5, \"attackVector\": \"LOCAL\", \"baseSeverity\": \"MEDIUM\", \"vectorString\": \"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H\", \"integrityImpact\": \"NONE\", \"userInteraction\": \"NONE\", \"attackComplexity\": \"LOW\", \"availabilityImpact\": \"HIGH\", \"privilegesRequired\": \"LOW\", \"confidentialityImpact\": \"NONE\"}}, {\"other\": {\"type\": \"ssvc\", \"content\": {\"id\": \"CVE-2023-46842\", \"role\": \"CISA Coordinator\", \"options\": [{\"Exploitation\": \"none\"}, {\"Automatable\": \"no\"}, {\"Technical Impact\": \"partial\"}], \"version\": \"2.0.3\", \"timestamp\": \"2024-05-24T18:23:20.820059Z\"}}}], \"problemTypes\": [{\"descriptions\": [{\"lang\": \"en\", \"type\": \"CWE\", \"cweId\": \"CWE-843\", \"description\": \"CWE-843 Access of Resource Using Incompatible Type ('Type Confusion')\"}]}], \"providerMetadata\": {\"orgId\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"shortName\": \"CISA-ADP\", \"dateUpdated\": \"2024-05-24T18:23:34.392Z\"}}], \"cna\": {\"title\": \"x86 HVM hypercalls may trigger Xen bug check\", \"credits\": [{\"lang\": \"en\", \"type\": \"finder\", \"value\": \"This issue was discovered by Manuel Andreas of Technical University of\\nMunich.\\n\"}], \"impacts\": [{\"descriptions\": [{\"lang\": \"en\", \"value\": \"A HVM or PVH guest can cause a hypervisor crash, causing a Denial of\\nService (DoS) of the entire host.\\n\"}]}], \"affected\": [{\"vendor\": \"Xen\", \"product\": \"Xen\", \"versions\": [{\"status\": \"unknown\", \"version\": \"consult Xen advisory XSA-454\"}], \"defaultStatus\": \"unknown\"}], \"datePublic\": \"2024-04-09T11:50:00Z\", \"references\": [{\"url\": \"https://xenbits.xenproject.org/xsa/advisory-454.html\"}], \"workarounds\": [{\"lang\": \"en\", \"value\": \"Not using HVM / PVH guests will avoid the vulnerability.\\n\"}], \"descriptions\": [{\"lang\": \"en\", \"value\": \"Unlike 32-bit PV guests, HVM guests may switch freely between 64-bit and\\nother modes.  This in particular means that they may set registers used\\nto pass 32-bit-mode hypercall arguments to values outside of the range\\n32-bit code would be able to set them to.\\n\\nWhen processing of hypercalls takes a considerable amount of time,\\nthe hypervisor may choose to invoke a hypercall continuation.  Doing so\\ninvolves putting (perhaps updated) hypercall arguments in respective\\nregisters.  For guests not running in 64-bit mode this further involves\\na certain amount of translation of the values.\\n\\nUnfortunately internal sanity checking of these translated values\\nassumes high halves of registers to always be clear when invoking a\\nhypercall.  When this is found not to be the case, it triggers a\\nconsistency check in the hypervisor and causes a crash.\\n\"}], \"configurations\": [{\"lang\": \"en\", \"value\": \"All Xen versions from at least 3.2 onwards are vulnerable.  Earlier\\nversions have not been inspected.\\n\\nOnly x86 systems are vulnerable.  Arm systems are not vulnerable.\\n\\nOnly HVM or PVH guests can leverage the vulnerability.  PV guests cannot\\nleverage the vulnerability.\\n\"}], \"providerMetadata\": {\"orgId\": \"23aa2041-22e1-471f-9209-9b7396fa234f\", \"shortName\": \"XEN\", \"dateUpdated\": \"2024-05-16T13:39:26.183Z\"}}}",
         cveMetadata: "{\"cveId\": \"CVE-2023-46842\", \"state\": \"PUBLISHED\", \"dateUpdated\": \"2024-12-04T16:57:56.599Z\", \"dateReserved\": \"2023-10-27T07:55:35.333Z\", \"assignerOrgId\": \"23aa2041-22e1-471f-9209-9b7396fa234f\", \"datePublished\": \"2024-05-16T13:39:26.183Z\", \"assignerShortName\": \"XEN\"}",
         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.