{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-2125 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-2125 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-2125 is a high-severity vulnerability in Allied Telesis K.K. CentreCOM, published on 28 Apr 2017. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-2125 and fix it if it is affected.\n\nWhat it is: CVE-2017-2125 is a high-severity vulnerability in Allied Telesis K.K. CentreCOM, published on 28 Apr 2017. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2017-2125 in the wild and no public exploit code.\n\nAffected product: Allied Telesis K.K. CentreCOM. 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-2017-2125/ (Markdown: https://insights.sbomify.com/CVE-2017-2125/index.md)","id":"CVE-2017-2125","markdown":"https://insights.sbomify.com/CVE-2017-2125/index.md","name":"CVE-2017-2125","record":{"aliases":["GHSA-r22m-g7h4-h52r"],"analysis":{"component_type":"network_device","fix_type":"patch","impacts":["privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"CentreCOM router","requires_auth":"low_privilege","summary":"Authenticated attackers can escalate privileges via the guest account on Allied Telesis CentreCOM AR260S V2 routers.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jpcert","cpe":[{"product":"centrecom_ar260s_v2_firmware","vendor":"allied_telesis_k.k."}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[],"description":"Privilege escalation vulnerability in CentreCOM AR260S V2 remote authenticated attackers to gain privileges via the guest account.","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":"Privilege escalation in CentreCOM","id":"CVE-2017-2125","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2017"},"n_packages":0,"n_references":3,"next":{"headline":"Auth bypass in WAPM-1166D","id":"CVE-2017-2126"},"packages":[],"prev":{"headline":"Cross-site scripting in OneThird CMS","id":"CVE-2017-2124"},"products":["CentreCOM"],"published":"2017-04-28","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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["Allied Telesis K.K."]},"summary":"Authenticated attackers can escalate privileges via the guest account on Allied Telesis CentreCOM AR260S V2 routers.","url":"https://insights.sbomify.com/CVE-2017-2125/"}