{"answers":{"affected":"2 open source packages ship an affected version, including org.pac4j:pac4j-saml. It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-10755 in the wild and no public exploit code.","fix":"Upgrade org.pac4j:pac4j-saml to 3.8.2 or later.","what":"CVE-2019-10755 is a medium-severity vulnerability in PAC4J For SAML Protocol, published on 23 Sep 2019. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-10755 and fix it if it is affected.\n\nWhat it is: CVE-2019-10755 is a medium-severity vulnerability in PAC4J For SAML Protocol, published on 23 Sep 2019. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-10755 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.pac4j:pac4j-saml (Maven): affected all versions; fixed in 3.8.2\n- org.pac4j:pac4j-saml (Maven): affected all versions; fixed in 3.8.2\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-10755/ (Markdown: https://insights.sbomify.com/CVE-2019-10755/index.md)","id":"CVE-2019-10755","markdown":"https://insights.sbomify.com/CVE-2019-10755/index.md","name":"CVE-2019-10755","record":{"aliases":["GHSA-rc75-cf5c-mxvh","SNYK-JAVA-ORGPAC4J-467407"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Java SAML library","requires_auth":"high_privilege","summary":"Predictable SAML identifiers due to weak random number generation allow attackers to bypass authentication in the pac4j-saml library.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"snyk","cpe":[{"product":"pac4j","vendor":"pac4j"}],"cvss":{"score":4.9,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-338","name":"Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)"}],"description":"The SAML identifier generated within SAML2Utils.java was found to make use of the apache commons-lang3 RandomStringUtils class which makes them predictable due to RandomStringUtils PRNG's algorithm not being cryptographically strong. This issue only affects the 3.X release of pac4j-saml.","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":"Use of Cryptographically Weak Pseudo-Random Number Generator in org.pac4j:pac4j-saml","id":"CVE-2019-10755","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"weak_cryptography","year":"2019"},"n_packages":2,"n_references":1,"next":{"headline":"Cross-site Scripting in node-red-dashboard","id":"CVE-2019-10756"},"packages":[{"ecosystem":"Maven","fixed":["3.8.2"],"introduced":["0"],"last_affected":[],"package":"org.pac4j:pac4j-saml","purl":null,"source":"GHSA-rc75-cf5c-mxvh"},{"ecosystem":"Maven","fixed":["3.8.2"],"introduced":["0"],"last_affected":[],"package":"org.pac4j:pac4j-saml","purl":"pkg:maven/org.pac4j/pac4j-saml","source":"GHSA-rc75-cf5c-mxvh"}],"prev":{"headline":"Use of Insufficiently Random Values in Apereo CAS","id":"CVE-2019-10754"},"products":["PAC4J For SAML Protocol"],"published":"2019-09-23","related":[{"cvss_score":8.7,"headline":"LDAP Injection in PAC4J","id":"CVE-2026-40459","kev_date_added":null,"published":"2026-04-17"},{"cvss_score":7.5,"headline":"Pac4j token validation bypass if OpenID Connect provider supports none algorithm","id":"CVE-2021-44878","kev_date_added":null,"published":"2022-01-06"},{"cvss_score":7,"headline":"Cross-Site Request Forgery in PAC4J","id":"CVE-2026-40458","kev_date_added":null,"published":"2026-04-17"}],"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":["n/a"]},"summary":"Predictable SAML identifiers due to weak random number generation allow attackers to bypass authentication in the pac4j-saml library.","url":"https://insights.sbomify.com/CVE-2019-10755/"}