{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2018-19393 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-19393 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-19393 is a high-severity missing authorization vulnerability in n/a, published on 15 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-19393 and fix it if it is affected.\n\nWhat it is: CVE-2018-19393 is a high-severity missing authorization vulnerability in n/a, published on 15 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-19393 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-19393/ (Markdown: https://insights.sbomify.com/CVE-2018-19393/index.md)","id":"CVE-2018-19393","markdown":"https://insights.sbomify.com/CVE-2018-19393/index.md","name":"CVE-2018-19393","record":{"aliases":["GHSA-fvr7-9mcc-7r67"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["data_modify","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Satcom maritime device","requires_auth":"none","summary":"Attackers can arbitrarily write to configuration files and cause denial of service on Cobham Satcom Sailor devices, requiring factory reset.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"satcom_sailor_800_firmware","vendor":"cobham"},{"product":"satcom_sailor_900_firmware","vendor":"cobham"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.0"},"cwes":[{"id":"CWE-732","name":"Incorrect Permission Assignment for Critical Resource"}],"description":"Cobham Satcom Sailor 800 and 900 devices contained a vulnerability that allowed for arbitrary writing of content to the system's configuration file. This was exploitable via multiple attack vectors depending on the device's configuration. Further analysis also indicated this vulnerability could be leveraged to achieve a Denial of Service (DoS) condition, where the device would require a factory reset to return to normal operation.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Missing authorization in n/a","id":"CVE-2018-19393","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2018"},"n_packages":0,"n_references":2,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2018-19394"},"packages":[],"prev":{"headline":"Auth bypass in n/a","id":"CVE-2018-19392"},"products":["n/a"],"published":"2019-03-15","related":[{"cvss_score":4.8,"headline":"Cross-site scripting in n/a","id":"CVE-2018-19394","kev_date_added":null,"published":"2019-03-15"}],"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)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Attackers can arbitrarily write to configuration files and cause denial of service on Cobham Satcom Sailor devices, requiring factory reset.","url":"https://insights.sbomify.com/CVE-2018-19393/"}