73 matches found
CVE-2020-1998
An improper authorization vulnerability in PAN-OS that mistakenly uses the permissions of local linux users instead of the intended SAML permissions of the account when the username is shared for the purposes of SSO authentication. This can result in authentication bypass and unintended resource...
CVE-2020-1998
CVE-2020-1998 describes an improper authorization vulnerability in PAN-OS where the system incorrectly applies local Linux user permissions instead of the intended SAML permissions when the username is shared for SSO. Affected are PAN-OS versions: 7.1.x before 7.1.26; 8.0.x before 8.1.13; 8.1.x b...
PT-2020-15221
Name of the Vulnerable Software and Affected Versions PAN-OS versions prior to 7.1.26 PAN-OS versions prior to 8.0.21 PAN-OS versions prior to 8.1.13 PAN-OS versions prior to 9.0.6 PAN-OS versions prior to 9.1.1 Description An improper authorization issue in PAN-OS mistakenly uses the permissions...
Incorrect Authentication Leading To Impersonation
Search Guard Kibana Plugin is susceptible to incorrect authentication. It is possible for a Kibana user to impersonate as kibanaserver user by submitting incorrect credentials and by fulfilling following conditions: 1 Kibana is configured to use Single-Sign-On as authentication method, one of...
Authentication flaw
Search Guard Kibana Plugin versions before 5.6.8-7 and before 6.x.y-12 had an issue that an authenticated Kibana user could impersonate as kibanaserver user when providing wrong credentials when all of the following conditions a-c are true: a Kibana is configured to use Single-Sign-On as...
PT-2017-6486
Name of the Vulnerable Software and Affected Versions TYPO3 extension "LDAP / SSO Authentication" ig ldap sso auth version 2.0.0 Description The issue is related to an Improper Authentication vulnerability in the "LDAP / SSO Authentication" extension for TYPO3. Recommendations For version 2.0.0 o...
git security and bug fix update
1.8.3.1-11 - dissalow repo names beginning with dash Resolves: CVE-2017-8386 -1.8.3.1-10 - do not put unsanitized branch names in Resolves: CVE-2014-9938 -1.8.3.1-9 - add control of GSSAPI credential delegation to enable HTTPS-SSO authentication Resolves: 1369173 1.8.3.1-8 - remove needles check ...
CVE-2017-7696
CVE-2017-7696 affects SAP AS JAVA SSO Authentication Library versions 2.0–3.0. A remote attacker can trigger a denial-of-service by sending a request that causes the server to generate a very large image via otp_logon_ui_resources/qr (e.g., width/height parameters). The issue is a memory exhausti...
CVE-2017-7696: Allocation of Resources Without Limits or Throttling
SAP AS JAVA SSO Authentication Library 2.0 through 3.0 allow remote attackers to cause a denial of service memory consumption via large values in the width and height parameters to otplogonuiresources/qr, aka SAP Security Note 2389042...
PT-2017-17894
Name of the Vulnerable Software and Affected Versions SAP AS JAVA SSO Authentication Library versions 2.0 through 3.0 Description The issue allows remote attackers to cause a denial of service, specifically memory consumption, by providing large values in the width and height parameters to the "o...
SSO Authentication Bypass and Website Takeover in DOKEOS
High-Tech Bridge Security Research Lab discovered a high-risk vulnerability in a popular e-learning software DOKEOS. A remote unauthenticated attacker can bypass authentication process and login to the vulnerable website with an arbitrary account including administrator's one. Successful...
Enhance Seraph SSO support to create users automatically
panel:bgColor=e7f4fa NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion|http://jira.atlassian.com/browse/JRACLOUD-4299. panel Users of SSO systems generally also have some sort of external user management. As a simple first step, JIRA's SSO authenticator...
Enhance Seraph SSO support to create users automatically
Users of SSO systems generally also have some sort of external user management. As a simple first step, JIRA's SSO authenticator could create an OSUser account in JIRA if the SSO authentication succeeds...