Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • T ticket
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,809
    • Issues 1,809
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Administrator
  • ticket
  • Issues
  • #1839

Closed
Open
Created Mar 14, 2024 by Administrator@rootMaintainer

Findings for Container Security, High, [TheRedHatter/javagoof:Dockerfile]:Improper Authentication

Created by: armorcodegithubpreprod[bot]

Findings for Container Security, High, [TheRedHatter/javagoof:Dockerfile]:Improper Authentication

Component Details

  • Exploit Maturity: no-known-exploit
  • Vulnerable Package: -
  • Current Version: -
  • Vulnerable Version(s): ><2.4.44+dfsg-5+deb9u3
  • Vulnerable Path: >null

NVD Description

Note: Versions mentioned in the description apply to the upstream openldap package. See How to fix? for Debian:9 relevant versions.

An issue was discovered in OpenLDAP 2.x before 2.4.48. When using SASL authentication and session encryption, and relying on the SASL security layers in slapd access controls, it is possible to obtain access that would otherwise be denied via a simple bind for any identity covered in those ACLs. After the first SASL bind is completed, the sasl_ssf value is retained for all new non-SASL connections. Depending on the ACL configuration, this can affect different types of operations (searches, modifications, etc.). In other words, a successful authorization step completed by one user affects the authorization requirement for a different user.

References

  • ADVISORY
  • BUGTRAQ
  • CONFIRM
  • CONFIRM
  • CONFIRM
  • Debian Security Announcement
  • Debian Security Tracker
  • FULLDISC
  • MISC
  • MLIST
  • MLIST
  • MLIST
  • N/A
  • OpenSuse Security Announcement
  • OpenSuse Security Announcement
  • Ubuntu CVE Tracker
  • Ubuntu Security Advisory
  • Ubuntu Security Advisory

Origin : null Type : null Image Id : null

Snyk Project Status: Active



Assignee
Assign to
Time tracking