{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2007-6619 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2007-6619 yet. Limit exposure of the affected software until one is available.","what":"CVE-2007-6619 is a high-severity missing authorization vulnerability in Atlassian Jira, published on 3 Jan 2008. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2007-6619 and fix it if it is affected.\n\nWhat it is: CVE-2007-6619 is a high-severity missing authorization vulnerability in Atlassian Jira, published on 3 Jan 2008. 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-2007-6619 in the wild and no public exploit code.\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-2007-6619/ (Markdown: https://insights.sbomify.com/CVE-2007-6619/index.md)","id":"CVE-2007-6619","markdown":"https://insights.sbomify.com/CVE-2007-6619/index.md","name":"CVE-2007-6619","record":{"aliases":["GHSA-qc68-5gff-qw5c"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"JIRA Enterprise Edition","requires_auth":"none","summary":"Remote attackers can change the default language via the Setup Wizard after installation due to missing authorization checks.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"jira","vendor":"atlassian"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[{"id":"CWE-264","name":null}],"description":"The Setup Wizard in Atlassian JIRA Enterprise Edition before 3.12.1 does not properly restrict setup attempts after setup is complete, which allows remote attackers to change the default language.","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-2007-6619","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"atlassian:jira","products":["atlassian:jira"],"type":"missing_authorization","year":"2007"},"n_packages":0,"n_references":4,"next":{"headline":"Path traversal in n/a","id":"CVE-2007-6620"},"packages":[],"prev":{"headline":"JIRA Enterprise Edition before 3.12.1 allows remote attackers to delete another user's shared filter via a modified filter ID.","id":"CVE-2007-6618"},"products":["n/a"],"published":"2008-01-03","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)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-07","vendors":["n/a"]},"summary":"Remote attackers can change the default language via the Setup Wizard after installation due to missing authorization checks.","url":"https://insights.sbomify.com/CVE-2007-6619/"}