{"answers":{"affected":"It affects 12 products.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-50920 exists.","fix":"No fix has been published for CVE-2023-50920 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-50920 is a medium-severity authentication bypass vulnerability in n/a, published on 12 Jan 2024. 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-2023-50920 and fix it if it is affected.\n\nWhat it is: CVE-2023-50920 is a medium-severity authentication bypass vulnerability in n/a, published on 12 Jan 2024. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-50920 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-50920/ (Markdown: https://insights.sbomify.com/CVE-2023-50920/index.md)","id":"CVE-2023-50920","markdown":"https://insights.sbomify.com/CVE-2023-50920/index.md","name":"CVE-2023-50920","record":{"aliases":["GHSA-pxmv-x94g-j48f"],"analysis":{"component_type":"network_device","fix_type":"upgrade","impacts":["account_takeover","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"GL.iNet router","requires_auth":"low_privilege","summary":"Attackers can hijack sessions and bypass authentication on GL.iNet routers due to predictable session IDs after reboots.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"gl-a1300_firmware","vendor":"gl-inet"},{"product":"gl-ar300m_firmware","vendor":"gl-inet"},{"product":"gl-ar750_firmware","vendor":"gl-inet"},{"product":"gl-ar750s_firmware","vendor":"gl-inet"},{"product":"gl-ax1800_firmware","vendor":"gl-inet"},{"product":"gl-axt1800_firmware","vendor":"gl-inet"},{"product":"gl-b1300_firmware","vendor":"gl-inet"},{"product":"gl-mt1300_firmware","vendor":"gl-inet"},{"product":"gl-mt2500_firmware","vendor":"gl-inet"},{"product":"gl-mt3000_firmware","vendor":"gl-inet"},{"product":"gl-mt300n-v2_firmware","vendor":"gl-inet"},{"product":"gl-mt6000_firmware","vendor":"gl-inet"}],"cvss":{"score":5.5,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-384","name":"Session Fixation"}],"description":"An issue was discovered on GL.iNet devices before version 4.5.0. They assign the same session ID after each user reboot, allowing attackers to share session identifiers between different sessions and bypass authentication or access control measures. Attackers can impersonate legitimate users or perform unauthorized actions. This affects A1300 4.4.6, AX1800 4.4.6, AXT1800 4.4.6, MT3000 4.4.6, MT2500 4.4.6, MT6000 4.5.0, MT1300 4.3.7, MT300N-V2 4.3.7, AR750S 4.3.7, AR750 4.3.7, AR300M 4.3.7, and B1300 4.3.7.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Auth bypass in n/a","id":"CVE-2023-50920","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"Privilege escalation in n/a","id":"CVE-2023-50921"},"packages":[],"prev":{"headline":"Auth bypass in n/a","id":"CVE-2023-50919"},"products":["n/a"],"published":"2024-01-12","related":[{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2023-50919","kev_date_added":null,"published":"2024-01-12"},{"cvss_score":9.8,"headline":"Privilege escalation in n/a","id":"CVE-2023-50921","kev_date_added":null,"published":"2024-01-03"},{"cvss_score":9.8,"headline":"Security feature bypass in n/a","id":"CVE-2023-31471","kev_date_added":null,"published":"2023-05-10"},{"cvss_score":9,"headline":"Memory corruption in n/a","id":"CVE-2023-31475","kev_date_added":null,"published":"2023-05-11"},{"cvss_score":7.8,"headline":"Command injection in n/a","id":"CVE-2023-50445","kev_date_added":null,"published":"2023-12-28"},{"cvss_score":7.5,"headline":"Path traversal in n/a","id":"CVE-2023-31477","kev_date_added":null,"published":"2023-05-11"},{"cvss_score":7.5,"headline":"Command injection in n/a","id":"CVE-2023-31472","kev_date_added":null,"published":"2023-05-09"}],"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":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-06-17","vendors":["n/a"]},"summary":"Attackers can hijack sessions and bypass authentication on GL.iNet routers due to predictable session IDs after reboots.","url":"https://insights.sbomify.com/CVE-2023-50920/"}