{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-29927 exists.","fix":"No fix has been published for CVE-2023-29927 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-29927 is a medium-severity missing authorization vulnerability in n/a, published on 16 May 2023. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-29927 and fix it if it is affected.\n\nWhat it is: CVE-2023-29927 is a medium-severity missing authorization vulnerability in n/a, published on 16 May 2023. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-29927 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-29927/ (Markdown: https://insights.sbomify.com/CVE-2023-29927/index.md)","id":"CVE-2023-29927","markdown":"https://insights.sbomify.com/CVE-2023-29927/index.md","name":"CVE-2023-29927","record":{"aliases":["GHSA-qw6r-773c-w64h"],"analysis":{"component_type":"desktop_application","fix_type":"no_fix_stated","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":true,"product_category":"Sage 300 ERP","requires_auth":"low_privilege","summary":"Low-privileged users can bypass client-side access controls to directly modify database records in specific Sage 300 network configurations.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"sage_300","vendor":"sage"}],"cvss":{"score":4.3,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"Versions of Sage 300 through 2022 implement role-based access controls that are only enforced client-side. Low-privileged Sage users, particularly those on a workstation setup in the \"Windows Peer-to-Peer Network\" or \"Client Server Network\" Sage 300 configurations, could recover the SQL connection strings being used by Sage 300 and interact directly with the underlying database(s) to create, update, and delete all company records, bypassing the program’s role-based access controls.","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":"Missing authorization in n/a","id":"CVE-2023-29927","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in n/a","id":"CVE-2023-29929"},"packages":[],"prev":{"headline":"PowerJob vulnerable to remote code execution","id":"CVE-2023-29926"},"products":["n/a"],"published":"2023-05-16","related":[{"cvss_score":9.8,"headline":"Hardcoded credentials in n/a","id":"CVE-2022-41397","kev_date_added":null,"published":"2023-04-28"},{"cvss_score":9.8,"headline":"Hardcoded credentials in n/a","id":"CVE-2022-41400","kev_date_added":null,"published":"2023-04-28"},{"cvss_score":7.8,"headline":"Missing authorization in n/a","id":"CVE-2022-38583","kev_date_added":null,"published":"2023-04-28"},{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2021-45492","kev_date_added":null,"published":"2022-07-14"},{"cvss_score":7.5,"headline":"Hardcoded credentials in n/a","id":"CVE-2022-41398","kev_date_added":null,"published":"2023-04-28"},{"cvss_score":7.5,"headline":"Hardcoded credentials in n/a","id":"CVE-2022-41399","kev_date_added":null,"published":"2023-04-28"}],"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-01-23","vendors":["n/a"]},"summary":"Low-privileged users can bypass client-side access controls to directly modify database records in specific Sage 300 network configurations.","url":"https://insights.sbomify.com/CVE-2023-29927/"}