{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-25187 exists.","fix":"No fix has been published for CVE-2023-25187 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-25187 is a medium-severity vulnerability in n/a, published on 16 Jun 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2023-25187 and fix it if it is affected.\n\nWhat it is: CVE-2023-25187 is a medium-severity vulnerability in n/a, published on 16 Jun 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-25187 exists.\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-2023-25187/ (Markdown: https://insights.sbomify.com/CVE-2023-25187/index.md)","id":"CVE-2023-25187","markdown":"https://insights.sbomify.com/CVE-2023-25187/index.md","name":"CVE-2023-25187","record":{"aliases":["GHSA-cmvf-q3f2-554c"],"analysis":{"component_type":"network_device","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Nokia Airscale RAN","requires_auth":"high_privilege","summary":"Malicious insiders can perform MITM attacks on BTS SSH connections due to unchanged factory default SSH keys during troubleshooting.","user_interaction":"required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"asika_airscale_firmware","vendor":"nokia"}],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AC:H/AV:L/A:H/C:H/I:H/PR:H/S:U/UI:R","version":"3.1"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"}],"description":"An issue was discovered on NOKIA Airscale ASIKA Single RAN devices before 21B. Nokia Single RAN commissioning procedures do not change (factory-time installed) default SSH public/private key values that are specific to a network operator. As a result, the CSP internal BTS network SSH server (disabled by default) continues to apply the default SSH public/private key values. These keys don't give access to BTS, because service user authentication is username/password-based on top of SSH. Nokia factory installed default SSH keys are meant to be changed from operator-specific values during the BTS deployment commissioning phase. However, before the 21B release, BTS commissioning manuals did not provide instructions to change default SSH keys (to BTS operator-specific values). This leads to a possibility for malicious operations staff (inside a CSP network) to attempt MITM exploitation of BTS service user access, during the moments that SSH is enabled for Nokia service personnel to perform troubleshooting activities.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2023-06-20","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2023-06-20","kind":"exploitdb","ref":"51535","stars":null,"title":"Nokia ASIKA 7.13.52 - Hard-coded private key disclosure"}],"tier":"weaponised"},"has_fix":null,"headline":"Hardcoded credentials in n/a","id":"CVE-2023-25187","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2023"},"n_packages":0,"n_references":3,"next":{"headline":"Auth bypass in n/a","id":"CVE-2023-25188"},"packages":[],"prev":{"headline":"Path traversal in n/a","id":"CVE-2023-25186"},"products":["n/a"],"published":"2023-06-16","related":[{"cvss_score":5.1,"headline":"Path traversal in n/a","id":"CVE-2023-25186","kev_date_added":null,"published":"2023-06-16"},{"cvss_score":5.1,"headline":"Auth bypass in n/a","id":"CVE-2023-25188","kev_date_added":null,"published":"2023-06-16"},{"cvss_score":3.8,"headline":"Privilege escalation in n/a","id":"CVE-2023-25185","kev_date_added":null,"published":"2023-06-16"}],"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":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-12-12","vendors":["n/a"]},"summary":"Malicious insiders can perform MITM attacks on BTS SSH connections due to unchanged factory default SSH keys during troubleshooting.","url":"https://insights.sbomify.com/CVE-2023-25187/"}