{"answers":{"affected":"It affects 2 products.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-3403 exists.","fix":"No fix has been published for CVE-2019-3403 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-3403 is a medium-severity missing authorization vulnerability in Atlassian Jira, published on 22 May 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-3403 and fix it if it is affected.\n\nWhat it is: CVE-2019-3403 is a medium-severity missing authorization vulnerability in Atlassian Jira, published on 22 May 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-3403 exists.\n\nAffected product: Atlassian Jira. 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-2019-3403/ (Markdown: https://insights.sbomify.com/CVE-2019-3403/index.md)","id":"CVE-2019-3403","markdown":"https://insights.sbomify.com/CVE-2019-3403/index.md","name":"CVE-2019-3403","record":{"aliases":["GHSA-6jvq-7cj3-36wh"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Jira issue tracker","requires_auth":"none","summary":"Remote attackers can enumerate usernames in Jira due to an incorrect authorization check in the user picker API.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"atlassian","cpe":[{"product":"jira","vendor":"atlassian"},{"product":"jira_server","vendor":"atlassian"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"The /rest/api/2/user/picker rest resource in Jira before version 7.13.3, from version 8.0.0 before version 8.0.4, and from version 8.1.0 before version 8.1.1 allows remote attackers to enumerate usernames via an incorrect authorisation check.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2020-09-15","github_poc":2,"max_poc_stars":2,"metasploit":0,"nuclei":1,"refs":[{"date":"2021-03-18T22:36:58Z","kind":"github_poc","ref":"https://github.com/davidmckennirey/CVE-2019-3403","stars":2,"title":"A simple python3 exploit for CVE-2019-3403"},{"date":"2020-09-15T23:00:03Z","kind":"github_poc","ref":"https://github.com/und3sc0n0c1d0/UserEnumJira","stars":1,"title":"Serie de scripts para enumerar nombres de usuarios de JIRA a partir de vulnerabilidades conocidas (CVE-2020-14181, CVE-2019-3403, CVE-2019-8449...)"},{"date":null,"kind":"nuclei","ref":"http/cves/2019/CVE-2019-3403.yaml","stars":null,"title":"Jira - Incorrect Authorization"}],"tier":"weaponised"},"has_fix":null,"headline":"Missing authorization in Jira","id":"CVE-2019-3403","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"atlassian:jira","products":["atlassian:jira","atlassian:jira_server"],"type":"missing_authorization","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Auth bypass in 360 Router F5C","id":"CVE-2019-3404"},"packages":[],"prev":{"headline":"Cross-site scripting in Jira","id":"CVE-2019-3402"},"products":["Jira"],"published":"2019-05-22","related":[{"cvss_score":9.8,"headline":"Deserialization in Jira Server","id":"CVE-2020-14172","kev_date_added":null,"published":"2020-07-03"},{"cvss_score":9.8,"headline":"Code injection in Jira Server","id":"CVE-2019-20409","kev_date_added":null,"published":"2020-06-23"},{"cvss_score":9.8,"headline":"Deserialization in n/a","id":"CVE-2017-5983","kev_date_added":null,"published":"2017-04-10"},{"cvss_score":9,"headline":"Code injection in n/a","id":"CVE-2010-1165","kev_date_added":null,"published":"2010-04-20"},{"cvss_score":8.8,"headline":"Cross-site request forgery in Atlassian JIRA Server before 7.1.9","id":"CVE-2016-4319","kev_date_added":null,"published":"2017-04-10"},{"cvss_score":8.1,"headline":"Auth bypass in Jira","id":"CVE-2019-8443","kev_date_added":null,"published":"2019-05-22"},{"cvss_score":7.5,"headline":"Information disclosure in Jira Data Center","id":"CVE-2021-41305","kev_date_added":null,"published":"2021-10-26"}],"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)"},{"class":"attribution","licence":"MIT","name":"Nuclei templates"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-17","vendors":["Atlassian"]},"summary":"Remote attackers can enumerate usernames in Jira due to an incorrect authorization check in the user picker API.","url":"https://insights.sbomify.com/CVE-2019-3403/"}