{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-8448 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-8448 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-8448 is a medium-severity vulnerability in Atlassian Jira Server, published on 13 Aug 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-8448 and fix it if it is affected.\n\nWhat it is: CVE-2019-8448 is a medium-severity vulnerability in Atlassian Jira Server, published on 13 Aug 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-8448 in the wild and no public exploit code.\n\nAffected product: Atlassian Jira Server. 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-8448/ (Markdown: https://insights.sbomify.com/CVE-2019-8448/index.md)","id":"CVE-2019-8448","markdown":"https://insights.sbomify.com/CVE-2019-8448/index.md","name":"CVE-2019-8448","record":{"aliases":["GHSA-2hfj-84hx-9426"],"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 valid usernames in Jira via the login page, facilitating targeted attacks.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"atlassian","cpe":[{"product":"jira_server","vendor":"atlassian"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.0"},"cwes":[],"description":"The login.jsp resource in Jira before version 7.13.4, and from version 8.0.0 before version 8.2.2 allows remote attackers to enumerate usernames via an information disclosure vulnerability.","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":"Information disclosure in Jira","id":"CVE-2019-8448","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"atlassian:jira_server","products":["atlassian:jira_server"],"type":"information_disclosure","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Information disclosure in Jira","id":"CVE-2019-8449"},"packages":[],"prev":{"headline":"Cross-site request forgery in Jira","id":"CVE-2019-8447"},"products":["Jira"],"published":"2019-08-13","related":[{"cvss_score":9.8,"headline":"Atlassian Jira Server and Data Center Server-Side Template Injection","id":"CVE-2019-11581","kev_date_added":"2022-03-07","published":"2019-08-09"},{"cvss_score":7.8,"headline":"Code injection in Jira Server","id":"CVE-2019-20400","kev_date_added":null,"published":"2020-02-06"},{"cvss_score":6.5,"headline":"Denial of service in Jira Server","id":"CVE-2020-14177","kev_date_added":null,"published":"2020-09-21"},{"cvss_score":6.5,"headline":"Cross-site request forgery in Jira Server","id":"CVE-2019-20401","kev_date_added":null,"published":"2020-02-06"},{"cvss_score":6.5,"headline":"Cross-site request forgery in Jira","id":"CVE-2019-14998","kev_date_added":null,"published":"2019-09-11"},{"cvss_score":6.5,"headline":"Server-side request forgery in Jira","id":"CVE-2019-8451","kev_date_added":null,"published":"2019-09-11"},{"cvss_score":6.1,"headline":"Cross-site scripting in Jira Data Center","id":"CVE-2021-43942","kev_date_added":null,"published":"2022-01-04"}],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-16","vendors":["Atlassian"]},"summary":"Remote attackers can enumerate valid usernames in Jira via the login page, facilitating targeted attacks.","url":"https://insights.sbomify.com/CVE-2019-8448/"}