{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-44840 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-44840 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-44840 is a low-severity missing authorization vulnerability in n/a, published on 18 Jan 2022. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-44840 and fix it if it is affected.\n\nWhat it is: CVE-2021-44840 is a low-severity missing authorization vulnerability in n/a, published on 18 Jan 2022. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-44840 in the wild and no public exploit code.\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-2021-44840/ (Markdown: https://insights.sbomify.com/CVE-2021-44840/index.md)","id":"CVE-2021-44840","markdown":"https://insights.sbomify.com/CVE-2021-44840/index.md","name":"CVE-2021-44840","record":{"aliases":["GHSA-39jq-m7cq-x5wg"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_modify","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Delta RM","requires_auth":"high_privilege","summary":"Privileged users can modify risk labels, while unprivileged users can export criticality labels due to missing authorization checks.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"delta_rm","vendor":"deltarm"}],"cvss":{"score":2.7,"severity":"low","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"An issue was discovered in Delta RM 1.2. Using an privileged account, it is possible to edit, create, and delete risk labels, such as Criticality and Priority Indication labels. By using the /core/table/query endpoint, and by using a POST request and indicating the affected label with tableUid parameter and the operation with datas[query], it is possible to edit, create, and delete the following labels: Priority Indication, Quality Evaluation, Progress Margin and Priority. Furthermore, it is also possible to export Criticality labels with an unprivileged user.","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 n/a","id":"CVE-2021-44840","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2021"},"n_packages":0,"n_references":2,"next":{"headline":"Memory corruption in n/a","id":"CVE-2021-44847"},"packages":[],"prev":{"headline":"Business logic in n/a","id":"CVE-2021-44839"},"products":["n/a"],"published":"2022-01-18","related":[{"cvss_score":6.5,"headline":"Business logic in n/a","id":"CVE-2021-44839","kev_date_added":null,"published":"2022-01-18"},{"cvss_score":4.3,"headline":"Missing authorization in n/a","id":"CVE-2021-44837","kev_date_added":null,"published":"2022-01-19"},{"cvss_score":4.3,"headline":"Missing authorization in n/a","id":"CVE-2021-44836","kev_date_added":null,"published":"2022-01-18"},{"cvss_score":4.3,"headline":"Missing authorization in n/a","id":"CVE-2021-44838","kev_date_added":null,"published":"2022-01-18"}],"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-04","vendors":["n/a"]},"summary":"Privileged users can modify risk labels, while unprivileged users can export criticality labels due to missing authorization checks.","url":"https://insights.sbomify.com/CVE-2021-44840/"}