klar

Klar Intégration de Clair et du registre Docker supporte à la fois les API Clair v1 et v3 Klar est un outil simple pour analyser les images stockées dans un registre Docker privé ou public à la recherche de vulnérabilités de sécurité en utilisant Clair https://github.com/coreos/clair. Klar est...

klar

Klar Integration of Clair and Docker Registry supports both Clair API v1 and v3 Klar is a simple tool to analyze images stored in a private or public Docker registry for security vulnerabilities using Clair https://github.com/coreos/clair. Klar is designed to be used as an integration tool so it...

github-dorks

Github Dorks Github Search is a quite powerful and useful feature that can be used to search for sensitive data on repositories. Collection of Github dorks can reveal sensitive personal and/or organizational information such as private keys, credentials, authentication tokens, etc. This list is...

jenkinsci__docker-commons-plugin_CVE-2022-20617_1-17

Docker Commons API Plugin pour Jenkins Plugin d'API, qui fournit les fonctionnalités communes partagées pour divers plugins liés à Docker. Résumé API pour gérer les empreintes d'images Docker et de conteneurs Identifiants et localisation du Docker Registry Identifiants et localisation du démon...

ictf-framework

Le Framework iCTF 3.0 Ceci est le framework que Shellphish utilise pour héberger l'iCTF. Le Framework iCTF est décrit dans un article présenté à l'atelier Usenix 3GSE en 2014. Nous avons publié ceci dans l'espoir que cela permette aux éducateurs et formateurs d'organiser leurs propres A/D CTFs. C...

CVE-2026-21005-Docker-Registry-V2-Schema-1-Image-Poisoning

CVE-2026-21005 – Отравление образов Docker Registry V2 Schema 1 Программный код Python Flask + Shell root@kitploit: dockerregistrysim.py - Simulated registry that serves schema1 manifests from flask import Flask, request, jsonify app = Flaskname images = 'myapp': 'v1': 'layers': 'sha256:abc',...

CVE-2019-16097

CVE-2019-16097-batch Avertissement Utilisation à des fins de recherche en sécurité uniquement. Ne pas utiliser pour des tests illégaux. Toute conséquence est de votre responsabilité !!! CVE-2019-16097-batch Script d'exploitation de vulnérabilité par lots Ajoutez les adresses cibles en masse dans ...

CVE-2019-16097-batch

CVE-2019-16097-batch Avertissement Utilisation uniquement pour la recherche en sécurité. Ne pas l'utiliser pour des tests illégaux. Les conséquences sont de votre propre responsabilité !!! CVE-2019-16097-batch Script d'exploitation par lots Ajoutez les adresses cibles par lots dans le fichier...

go-pillage-registries

go-pillage-registries Ce projet prend un registre Docker et pille le manifeste et la configuration de chaque image de son catalogue. Il utilise le paquet de la commande crane de Google, qui devrait suivre la sémantique de keychain de docker. Si vous souhaitez remplacer cela, modifiez simplement...

Astra Linux – Vulnerability in Docker-Registry

A flaw was discovered in the /v2/catalog endpoint located in the distribution/distribution directory. This endpoint accepts a parameter that controls the maximum number of records to be returned query string: n. This vulnerability allows a malicious user to submit an excessively large value for n...

CVE-2026-49349 regclient may leak authentication credentials to external blob stores

regclient is a Docker and OCI Registry Client in Go. Prior to version 0.11.5, credentials for a registry may be inadvertently leaked to external servers. A prerequisite for this attack is a malicious registry server, a malicious blob store, or a registry that does not restrict the external URLs f...

PYSEC-2026-2391 BBOT: Server-Side Request Forgery (SSRF) in docker_pull module via WWW-Authenticate realm parsing

The dockerpull module uses the realm parameter from a Docker registry's WWW-Authenticate response header as the authentication endpoint without validation. An attacker in a man-in-the-middle position between bbot and a Docker registry could modify this header to redirect the authentication reques...

BBOT: Server-Side Request Forgery (SSRF) in docker_pull module via WWW-Authenticate realm parsing

The dockerpull module uses the realm parameter from a Docker registry's WWW-Authenticate response header as the authentication endpoint without validation. An attacker in a man-in-the-middle position between bbot and a Docker registry could modify this header to redirect the authentication reques...

PT-2026-39313

🔴 Docker Registry Auth Substring Match Forwards Credentials to a Different Registry CVE-2025-27119, High https://t.co/gO08whMpWZ...

Exploit for CVE-2026-7482

CVE-2026-7482: Ollama Heap Out-of-Bounds Read 1-Day PoC Thi...

org.keycloak/keycloak-services: Keycloak: Missing Check on Disabled Client for Docker Registry Protocol

A flaw was identified in the Docker v2 authentication endpoint of Keycloak, where tokens continue to be issued even after a Docker registry client has been administratively disabled. This means that turning the client “Enabled” setting to OFF does not fully prevent access. As a result, previously...

GHSA-FJF4-6F34-W64Q Keycloak: Missing Check on Disabled Client for Docker Registry Protocol

A flaw was identified in the Docker v2 authentication endpoint of Keycloak, where tokens continue to be issued even after a Docker registry client has been administratively disabled. This means that turning the client “Enabled” setting to OFF does not fully prevent access. As a result, previously...

CVE-2026-2733 Org.keycloak/keycloak-services: keycloak: missing check on disabled client for docker registry protocol

A flaw was identified in the Docker v2 authentication endpoint of Keycloak, where tokens continue to be issued even after a Docker registry client has been administratively disabled. This means that turning the client “Enabled” setting to OFF does not fully prevent access. As a result, previously...

CVE-2026-2733 Org.keycloak/keycloak-services: keycloak: missing check on disabled client for docker registry protocol

A flaw was identified in the Docker v2 authentication endpoint of Keycloak, where tokens continue to be issued even after a Docker registry client has been administratively disabled. This means that turning the client “Enabled” setting to OFF does not fully prevent access. As a result, previously...

malcontent OCI image pull credential exfiltration via malicious registry token realm

Malcontent could be made to expose Docker registry credentials if it scanned a specially crafted OCI image reference. Malcontent uses google/go-containerregistry for OCI image pulls, which by default uses the Docker credential keychain. A malicious registry could return a WWW-Authenticate header...