# CVE-2016-6338: Security feature bypass in n/a > Physically proximate attackers can bypass webadmin session timeouts by triggering repeating queries via UI selections in RHEV-M. - **Severity:** Medium 6.8 (`CVSS:3.0/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 20 Apr 2017 - **Updated:** 6 Aug 2024 - **Also known as:** GHSA-w4h4-7mqm-9j6c, RHSA-2017:3427 ## What is CVE-2016-6338? CVE-2016-6338 is a medium-severity vulnerability in n/a, published on 20 Apr 2017. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description ovirt-engine-webadmin, as used in Red Hat Enterprise Virtualization Manager (aka RHEV-M) for Servers and RHEV-M 4.0, allows physically proximate attackers to bypass a webadmin session timeout restriction via vectors related to UI selections, which trigger repeating queries. Weakness: CWE-284 (Improper Access Control) ## Which versions are affected by CVE-2016-6338? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `ovirt-engine` | Red Hat:rhev_manager:4 | All versions | 0:4.1.8.2-0.1.el7 | | `ovirt-engine-backend` | Red Hat:rhev_manager:4 | All versions | 0:4.1.8.2-0.1.el7 | | `ovirt-engine-dbscripts` | Red Hat:rhev_manager:4 | All versions | 0:4.1.8.2-0.1.el7 | | `ovirt-engine-extensions-api-impl` | Red Hat:rhev_manager:4 | All versions | 0:4.1.8.2-0.1.el7 | | `ovirt-engine-extensions-api-impl-javadoc` | Red Hat:rhev_manager:4 | All versions | 0:4.1.8.2-0.1.el7 | | `ovirt-engine-lib` | Red Hat:rhev_manager:4 | All versions | 0:4.1.8.2-0.1.el7 | | `ovirt-engine-restapi` | Red Hat:rhev_manager:4 | All versions | 0:4.1.8.2-0.1.el7 | | `ovirt-engine-setup` | Red Hat:rhev_manager:4 | All versions | 0:4.1.8.2-0.1.el7 | | `ovirt-engine-setup-base` | Red Hat:rhev_manager:4 | All versions | 0:4.1.8.2-0.1.el7 | | `ovirt-engine-setup-plugin-ovirt-engine` | Red Hat:rhev_manager:4 | All versions | 0:4.1.8.2-0.1.el7 | | `ovirt-engine-setup-plugin-ovirt-engine-common` | Red Hat:rhev_manager:4 | All versions | 0:4.1.8.2-0.1.el7 | | `ovirt-engine-setup-plugin-vmconsole-proxy-helper` | Red Hat:rhev_manager:4 | All versions | 0:4.1.8.2-0.1.el7 | | `ovirt-engine-setup-plugin-websocket-proxy` | Red Hat:rhev_manager:4 | All versions | 0:4.1.8.2-0.1.el7 | | `ovirt-engine-tools` | Red Hat:rhev_manager:4 | All versions | 0:4.1.8.2-0.1.el7 | | `ovirt-engine-tools-backup` | Red Hat:rhev_manager:4 | All versions | 0:4.1.8.2-0.1.el7 | | `ovirt-engine-userportal` | Red Hat:rhev_manager:4 | All versions | 0:4.1.8.2-0.1.el7 | | `ovirt-engine-vmconsole-proxy-helper` | Red Hat:rhev_manager:4 | All versions | 0:4.1.8.2-0.1.el7 | | `ovirt-engine-webadmin-portal` | Red Hat:rhev_manager:4 | All versions | 0:4.1.8.2-0.1.el7 | | `ovirt-engine-websocket-proxy` | Red Hat:rhev_manager:4 | All versions | 0:4.1.8.2-0.1.el7 | | `rhevm` | Red Hat:rhev_manager:4 | All versions | 0:4.1.8.2-0.1.el7 | Products: Redhat Enterprise Virtualization. ## How do I fix CVE-2016-6338? Apply the vendor's patch. ## Is CVE-2016-6338 being exploited? There is no known exploitation of CVE-2016-6338 in the wild and no public exploit code. ## Other vulnerabilities in n/a - [CVE-2015-5201](https://insights.sbomify.com/CVE-2015-5201/): Auth bypass in Enterprise Virtualization Hypervisor (aka RHEV-H) (high 7.5) - [CVE-2013-2151](https://insights.sbomify.com/CVE-2013-2151/): Privilege escalation in n/a (high 7.2) - [CVE-2013-2152](https://insights.sbomify.com/CVE-2013-2152/): Privilege escalation in n/a (high 7.2) - [CVE-2013-2176](https://insights.sbomify.com/CVE-2013-2176/): Privilege escalation in n/a (high 7.2) - [CVE-2017-2614](https://insights.sbomify.com/CVE-2017-2614/): Auth bypass in ovirt-engine-extension-aaa-jdbc (medium 6.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2016-6338 and fix it if it is affected. What it is: CVE-2016-6338 is a medium-severity vulnerability in n/a, published on 20 Apr 2017. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2016-6338 in the wild and no public exploit code. Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2016-6338/ (Markdown: https://insights.sbomify.com/CVE-2016-6338/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2016-6338 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2016-6338 - OSV: https://osv.dev/vulnerability/CVE-2016-6338 --- From sbomify Insights: https://insights.sbomify.com/CVE-2016-6338/ Summaries are generated and may contain mistakes; the official description above is the record.