{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-10825 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-10825 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-10825 is a medium-severity missing authorization vulnerability in n/a, published on 15 May 2018. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-10825 and fix it if it is affected.\n\nWhat it is: CVE-2018-10825 is a medium-severity missing authorization vulnerability in n/a, published on 15 May 2018. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-10825 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-10825/ (Markdown: https://insights.sbomify.com/CVE-2018-10825/index.md)","id":"CVE-2018-10825","markdown":"https://insights.sbomify.com/CVE-2018-10825/index.md","name":"CVE-2018-10825","record":{"aliases":["GHSA-c7h4-vhw8-gq22"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["data_modify","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Baby monitoring device","requires_auth":"none","summary":"Attackers can inject fake position and temperature data into Mimo Baby 2 devices via unauthenticated Bluetooth Low Energy communication.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"mimo_baby_2_firmware","vendor":"mimobaby"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.0"},"cwes":[{"id":"CWE-311","name":"Missing Encryption of Sensitive Data"},{"id":"CWE-287","name":"Improper Authentication"}],"description":"Mimo Baby 2 devices do not use authentication or encryption for the Bluetooth Low Energy (BLE) communication from a Turtle to a Lilypad, which allows attackers to inject fake information about the position and temperature of a baby via a replay or spoofing attack.","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-10825","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"Denial of service in n/a","id":"CVE-2018-10827"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2018-10824"},"products":["n/a"],"published":"2018-05-15","related":[],"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 inject fake position and temperature data into Mimo Baby 2 devices via unauthenticated Bluetooth Low Energy communication.","url":"https://insights.sbomify.com/CVE-2018-10825/"}