{"answers":{"affected":"2 open source packages ship an affected version, including org.jenkins-ci.plugins:assembla-auth. It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-10280 in the wild and no public exploit code.","fix":"Upgrade org.jenkins-ci.plugins:assembla-auth to 1.13 or later.","what":"CVE-2019-10280 is a high-severity vulnerability in Jenkins Assembla Auth Plugin, published on 4 Apr 2019. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-10280 and fix it if it is affected.\n\nWhat it is: CVE-2019-10280 is a high-severity vulnerability in Jenkins Assembla Auth Plugin, published on 4 Apr 2019. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-10280 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.jenkins-ci.plugins:assembla-auth (Maven): affected all versions; fixed in 1.13\n- org.jenkins-ci.plugins:assembla-auth (Maven): affected all versions; fixed in 1.13\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-10280/ (Markdown: https://insights.sbomify.com/CVE-2019-10280/index.md)","id":"CVE-2019-10280","markdown":"https://insights.sbomify.com/CVE-2019-10280/index.md","name":"CVE-2019-10280","record":{"aliases":["GHSA-wmq3-24jm-m8xh"],"analysis":{"component_type":"cms_plugin","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenkins Assembla Auth Plugin","requires_auth":"low_privilege","summary":"Attackers with file system access can read unencrypted credentials stored in the Jenkins configuration file.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jenkins","cpe":[{"product":"assembla_auth","vendor":"jenkins"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-522","name":"Insufficiently Protected Credentials"}],"description":"Jenkins Assembla Auth Plugin stores credentials unencrypted in the global config.xml configuration file on the Jenkins master where they can be viewed by users with access to the master file system.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Jenkins Assembla Auth Plugin stores credentials in plain text","id":"CVE-2019-10280","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"hardcoded_credentials","year":"2019"},"n_packages":2,"n_references":3,"next":{"headline":"Jenkins Relution Enterprise Appstore Publisher Plugin stores credentials in plain text","id":"CVE-2019-10281"},"packages":[{"ecosystem":"Maven","fixed":["1.13"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:assembla-auth","purl":null,"source":"GHSA-wmq3-24jm-m8xh"},{"ecosystem":"Maven","fixed":["1.13"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:assembla-auth","purl":"pkg:maven/org.jenkins-ci.plugins/assembla-auth","source":"GHSA-wmq3-24jm-m8xh"}],"prev":{"headline":"Missing permission check in Jenkins jenkins-reviewbot Plugin","id":"CVE-2019-10279"},"products":["Jenkins Assembla Auth Plugin"],"published":"2019-04-04","related":[{"cvss_score":8.8,"headline":"Disabled permissions granted by Jenkins Assembla Auth Plugin","id":"CVE-2023-41945","kev_date_added":null,"published":"2023-09-06"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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":["Jenkins project"]},"summary":"Attackers with file system access can read unencrypted credentials stored in the Jenkins configuration file.","url":"https://insights.sbomify.com/CVE-2019-10280/"}