# CVE-2019-5995: Missing authorization in EOS series digital cameras, PowerShot SX740 HS, PowerShot SX70 HS, and PowerShot G5XmarkⅡ > Attackers can bypass authorization checks on Canon EOS cameras, potentially accessing restricted features or data without proper credentials. - **Severity:** Medium 6.5 (`CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** No - **Published:** 6 Aug 2019 - **Updated:** 4 Aug 2024 - **Also known as:** GHSA-384c-q74f-g7hv ## What is CVE-2019-5995? CVE-2019-5995 is a medium-severity missing authorization vulnerability in Canon, Inc. EOS series digital cameras, PowerShot SX740 HS, PowerShot SX70 HS, and PowerShot G5XmarkⅡ, published on 6 Aug 2019. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description Missing authorization vulnerability exists in EOS series digital cameras (EOS-1D X firmware version 2.1.0 and earlier, EOS-1D X MKII firmware version 1.1.6 and earlier, EOS-1D C firmware version 1.4.1 and earlier, EOS 5D MARK III firmware version 1.3.5 and earlier, EOS 5D MARK IV firmware version 1.2.0 and earlier, EOS 5DS firmware version 1.1.2 and earlier, EOS 5DS R firmware version 1.1.2 and earlier, EOS 6D firmware version 1.1.8 and earlier, EOS 6D MARK II firmware version 1.0.4 and earlier, EOS 7D MARK II firmware version 1.1.2 and earlier, EOS 70 D firmware version 1.1.2 and earlier, EOS 80 D firmware version 1.0.2 and earlier, EOS KISS X7I / EOS D REBEL T5I / EOS 700D firmware version 1.1.5 and earlier, EOS KISS X8I / EOS D REBEL T6I / EOS 750D firmware version 1.0.0 and earlier, EOS KISS X9I / EOS D REBEL T7I / EOS 800D firmware version 1.0.1 and earlier, EOS KISS X7 / EOS D REBEL SL1 / EOS 100D firmware version 1.0.1 and earlier, EOS KISS X9 / EOS D REBEL SL2 / EOS 200D firmware version 1.0.1 and earlier, EOS KISS X10 / EOS D REBEL SL3 / EOS 200D / EOS 250D firmware version 1.0.1 and earlier, EOS 8000D / EOS D REBEL T6S / EOS 760D firmware version 1.0.0 and earlier, EOS 9000D / EOS 77D firmware version 1.0.2 and earlier, EOS KISS X70 / EOS D REBEL T5 / EOS 1200D firmware version 1.0.2 and earlier, EOS D REBEL T5 RE / EOS 1200D MG / EOS HI firmware version 1.0.2 and earlier, EOS KISS X80 / EOS D REBEL T6 / EOS 1300D firmware version 1.1.0 and earlier, EOS KISS X90 / EOS D REBEL T7 / EOS 1500D / EOS 2000D firmware version 1.0.0 and earlier, EOS D REBEL T100 / EOS 3000D / EOS 4000D firmware version 1.0.0 and earlier, EOS R firmware version 1.3.0 and earlier, EOS RP firmware version 1.2.0 and earlier, EOS RP GOLD firmware version 1.2.0 and earlier, EOS M2 firmware version 1.0.3 and earlier, EOS M3 firmware version 1.2.0 and earlier, EOS M5 firmware version 1.0.1 and earlier, EOS M6 firmware version 1.0.1 and earlier, EOS M6(China) firmware version 5.0.0 and earlier, EOS M10 firmware version 1.1.0 and earlier, EOS M100 firmware version 1.0.0 and earlier, EOS KISS M / EOS M50 firmware version 1.0.2 and earlier) and PowerShot SX740 HS firmware version 1.0.1 and earlier, PowerShot SX70 HS firmware version 1.1.0 and earlier, and PowerShot G5Xmark II firmware version 1.0.1 and earlier. A successful exploitation may result in a specially crafted firmware update or unofficial firmware update being applied without user's consent via unspecified vector. Weakness: CWE-862 (Missing Authorization) ## Which versions are affected by CVE-2019-5995? It affects 66 products. Products: Canon Eos-1d C Firmware, Canon Eos-1d X Firmware, Canon Eos-1d X Mkii Firmware, Canon Eos 100d Firmware, Canon Eos 1200d Firmware, Canon Eos 1200d Mg Firmware, Canon Eos 1300d Firmware, Canon Eos 1500d Firmware, Canon Eos 2000d Firmware, Canon Eos 200d Firmware, Canon Eos 250d Firmware, Canon Eos 3000d Firmware, Canon Eos 4000d Firmware, Canon Eos 5d Mark Iii Firmware, Canon Eos 5d Mark Iv Firmware, Canon Eos 5ds Firmware, Canon Eos 5ds R Firmware, Canon Eos 6d Firmware, Canon Eos 6d Mark Ii Firmware, Canon Eos 700d Firmware and 46 more. ## How do I fix CVE-2019-5995? No fix has been published for CVE-2019-5995 yet. Limit exposure of the affected software until one is available. ## Is CVE-2019-5995 being exploited? There is no known exploitation of CVE-2019-5995 in the wild and no public exploit code. ## Other vulnerabilities in Canon, Inc. EOS series digital cameras, PowerShot SX740 HS, PowerShot SX70 HS, and PowerShot G5XmarkⅡ - [CVE-2019-5994](https://insights.sbomify.com/CVE-2019-5994/): Memory corruption in EOS series digital cameras, PowerShot SX740 HS, PowerShot SX70 HS, and PowerShot G5XmarkⅡ (high 8.8) - [CVE-2019-5998](https://insights.sbomify.com/CVE-2019-5998/): Memory corruption in EOS series digital cameras, PowerShot SX740 HS, PowerShot SX70 HS, and PowerShot G5XmarkⅡ (high 8.8) - [CVE-2019-5999](https://insights.sbomify.com/CVE-2019-5999/): Memory corruption in EOS series digital cameras, PowerShot SX740 HS, PowerShot SX70 HS, and PowerShot G5XmarkⅡ (high 8.8) - [CVE-2019-6000](https://insights.sbomify.com/CVE-2019-6000/): Memory corruption in EOS series digital cameras, PowerShot SX740 HS, PowerShot SX70 HS, and PowerShot G5XmarkⅡ (high 8.8) - [CVE-2019-6001](https://insights.sbomify.com/CVE-2019-6001/): Memory corruption in EOS series digital cameras, PowerShot SX740 HS, PowerShot SX70 HS, and PowerShot G5XmarkⅡ (medium 6.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2019-5995 and fix it if it is affected. What it is: CVE-2019-5995 is a medium-severity missing authorization vulnerability in Canon, Inc. EOS series digital cameras, PowerShot SX740 HS, PowerShot SX70 HS, and PowerShot G5XmarkⅡ, published on 6 Aug 2019. 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-2019-5995 in the wild and no public exploit code. Affected product: Canon, Inc. EOS series digital cameras, PowerShot SX740 HS, PowerShot SX70 HS, and PowerShot G5XmarkⅡ. 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-2019-5995/ (Markdown: https://insights.sbomify.com/CVE-2019-5995/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2019-5995 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-5995 - OSV: https://osv.dev/vulnerability/CVE-2019-5995 --- From sbomify Insights: https://insights.sbomify.com/CVE-2019-5995/ Summaries are generated and may contain mistakes; the official description above is the record.