{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-3183 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-3183 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-3183 is a high-severity missing authorization vulnerability in Sage XRT Treasury, published on 24 Jul 2018. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-3183 and fix it if it is affected.\n\nWhat it is: CVE-2017-3183 is a high-severity missing authorization vulnerability in Sage XRT Treasury, published on 24 Jul 2018. 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-3183 in the wild and no public exploit code.\n\nAffected product: Sage XRT Treasury. 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-3183/ (Markdown: https://insights.sbomify.com/CVE-2017-3183/index.md)","id":"CVE-2017-3183","markdown":"https://insights.sbomify.com/CVE-2017-3183/index.md","name":"CVE-2017-3183","record":{"aliases":["GHSA-pvcf-3v6c-7ppw"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["privilege_escalation","data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Treasury management software","requires_auth":"low_privilege","summary":"Authenticated users can escalate privileges by modifying USER_CODE to access privileged database functions in Sage XRT Treasury.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"certcc","cpe":[{"product":"xrt_treasury","vendor":"sage"}],"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":[{"id":"CWE-863","name":"Incorrect Authorization"},{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"}],"description":"Sage XRT Treasury, version 3, fails to properly restrict database access to authorized users, which may enable any authenticated user to gain full access to privileged database functions. Sage XRT Treasury is a business finance management application. Database user access privileges are determined by the USER_CODE field associated with the querying user. By modifying the USER_CODE value to match that of a privileged user, a low-privileged, authenticated user may gain privileged access to the SQL database. A remote, authenticated user can submit specially crafted SQL queries to gain privileged access to the application database.","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 XRT Treasury","id":"CVE-2017-3183","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2017"},"n_packages":0,"n_references":2,"next":{"headline":"Missing authorization in ACTi D, B, I, and E series cameras","id":"CVE-2017-3184"},"packages":[],"prev":{"headline":"Weak cryptography in SDK","id":"CVE-2017-3182"},"products":["XRT Treasury"],"published":"2018-07-24","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":["Sage"]},"summary":"Authenticated users can escalate privileges by modifying USER_CODE to access privileged database functions in Sage XRT Treasury.","url":"https://insights.sbomify.com/CVE-2017-3183/"}