{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2016-0380 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2016-0380 yet. Limit exposure of the affected software until one is available.","what":"CVE-2016-0380 is a low-severity vulnerability in n/a, published on 8 Aug 2016. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2016-0380 and fix it if it is affected.\n\nWhat it is: CVE-2016-0380 is a low-severity vulnerability in n/a, published on 8 Aug 2016. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2016-0380 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-2016-0380/ (Markdown: https://insights.sbomify.com/CVE-2016-0380/index.md)","id":"CVE-2016-0380","markdown":"https://insights.sbomify.com/CVE-2016-0380/index.md","name":"CVE-2016-0380","record":{"aliases":["GHSA-mhp5-4q48-rcqc"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"IBM Sterling Connect:Direct","requires_auth":"low_privilege","summary":"Local users can read sensitive information due to insecure default file permissions in IBM Sterling Connect:Direct for Unix.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"sterling_connect\\","vendor":"ibm"}],"cvss":{"score":3.3,"severity":"low","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-264","name":null}],"description":"IBM Sterling Connect:Direct for Unix 4.1.0 before 4.1.0.4 iFix073 and 4.2.0 before 4.2.0.4 iFix003 uses default file permissions of 0664, which allows local users to obtain sensitive information via standard filesystem operations.","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 n/a","id":"CVE-2016-0380","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2016"},"n_packages":0,"n_references":3,"next":{"headline":"Denial of service in n/a","id":"CVE-2016-0381"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2016-0379"},"products":["n/a"],"published":"2016-08-08","related":[{"cvss_score":7.5,"headline":"IBM Connect:Express for UNIX denial of service","id":"CVE-2023-32331","kev_date_added":null,"published":"2024-03-04"},{"cvss_score":7.5,"headline":"Memory corruption in Sterling Connect Direct for Microsoft Windows","id":"CVE-2020-4767","kev_date_added":null,"published":"2020-10-28"},{"cvss_score":7.2,"headline":"IBM Sterling Connect:Direct for UNIX command execution","id":"CVE-2025-36137","kev_date_added":null,"published":"2025-10-30"},{"cvss_score":6.7,"headline":"Privilege escalation in Sterling Connect:Direct for UNIX","id":"CVE-2018-1903","kev_date_added":null,"published":"2019-04-10"},{"cvss_score":6.5,"headline":"IBM Sterling Connect:Express for UNIX server-side request forgery","id":"CVE-2023-29260","kev_date_added":null,"published":"2023-07-19"},{"cvss_score":6.3,"headline":"Multiple vulnerabilities were addressed in IBM Sterling Connect:Express for UNIX.","id":"CVE-2025-36063","kev_date_added":null,"published":"2026-01-20"},{"cvss_score":6.3,"headline":"Multiple vulnerabilities were addressed in IBM Sterling Connect:Express for UNIX.","id":"CVE-2025-36065","kev_date_added":null,"published":"2026-01-20"}],"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-05","vendors":["n/a"]},"summary":"Local users can read sensitive information due to insecure default file permissions in IBM Sterling Connect:Direct for Unix.","url":"https://insights.sbomify.com/CVE-2016-0380/"}