{"answers":{"affected":"It affects 3 products.","exploited":"There is no known exploitation of CVE-2018-20219 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-20219 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-20219 is a high-severity vulnerability in n/a, published on 17 Mar 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-20219 and fix it if it is affected.\n\nWhat it is: CVE-2018-20219 is a high-severity vulnerability in n/a, published on 17 Mar 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-20219 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2018-20219/ (Markdown: https://insights.sbomify.com/CVE-2018-20219/index.md)","id":"CVE-2018-20219","markdown":"https://insights.sbomify.com/CVE-2018-20219/index.md","name":"CVE-2018-20219","record":{"aliases":["GHSA-3529-j6rq-qh67"],"analysis":{"component_type":"iot_embedded","fix_type":"patch","impacts":["security_bypass","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"video encoder device","requires_auth":"none","summary":"Attackers can bypass authentication on Teracue ENC-400 devices by using a hard-coded cookie, gaining unauthorized access to the web administration panel.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"enc-400_hdmi2_firmware","vendor":"teracue"},{"product":"enc-400_hdmi_firmware","vendor":"teracue"},{"product":"enc-400_hdsdi_firmware","vendor":"teracue"}],"cvss":{"score":8.1,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"}],"description":"An issue was discovered on Teracue ENC-400 devices with firmware 2.56 and below. After successful authentication, the device sends an authentication cookie to the end user such that they can access the devices web administration panel. This token is hard-coded to a string in the source code (/usr/share/www/check.lp file). By setting this cookie in a browser, an attacker is able to maintain access to every ENC-400 device without knowing the password, which results in authentication bypass. Even if a user changes the password on the device, this token is static and unchanged.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2019-02-22","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2019-02-22","kind":"exploitdb","ref":"46451","stars":null,"title":"Teracue ENC-400 - Command Injection / Missing Authentication"}],"tier":"poc_unverified"},"has_fix":null,"headline":"Hardcoded credentials in n/a","id":"CVE-2018-20219","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2018"},"n_packages":0,"n_references":3,"next":{"headline":"Missing authorization in n/a","id":"CVE-2018-20220"},"packages":[],"prev":{"headline":"Command injection in n/a","id":"CVE-2018-20218"},"products":["n/a"],"published":"2019-03-17","related":[{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2018-20218","kev_date_added":null,"published":"2019-03-17"},{"cvss_score":7.5,"headline":"Missing authorization in n/a","id":"CVE-2018-20220","kev_date_added":null,"published":"2019-03-17"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Attackers can bypass authentication on Teracue ENC-400 devices by using a hard-coded cookie, gaining unauthorized access to the web administration panel.","url":"https://insights.sbomify.com/CVE-2018-20219/"}