Schwachstellen verstehen. Anwendungen schützen.
Erfahren Sie, welche Schwachstellen Ihre Technologien betreffen und wie Sie diese beheben. Hier finden Sie verständliche Erklärungen, betroffene Versionen und konkrete Empfehlungen - von CMS und Plugins bis zu Anwendungsbibliotheken.
Schwachstellenarchiv 6.856
Filter zurücksetzenopenssl-encrypt has CORS wildcard with allow_credentials=True in standalone servers
openssl-encrypt's unverified key bundle from_dict() + to_identity() path allows encryption to attacker keys
openssl-encrypt's readiness endpoint leaks database error details to unauthenticated callers
openssl_encrypt versions before 1.4.0 contain a sandbox bypass vulnerability where the plugin sandbox fails to restrict alternative file access methods like pathlib.Path and io.open. Attackers can imp
openssl-encrypt: TOTP rate limiter is in-memory only — not shared across workers, lost on restart
openssl-encrypt accepts refresh tokens as URL query parameters causing token leakage
openssl-encrypt has no owner verification on key revocation — any client can revoke any key
openssl_encrypt versions before 1.4.0 contain an insecure default configuration that trusts the entire RFC 1918 private address space in IntegrityProxyConfig trusted_proxies. Attackers on private netw
openssl_encrypt versions before 1.4.6 contain a key derivation flaw in sequential XOR composition mode where the last stage cancels out during key generation. When configured with a single KDF and no
openssl_encrypt (pip) versions <= 1.4.7 contain an information exposure vulnerability where the 'hsm fido2-test' and 'hsm onlykey-test' diagnostic commands unconditionally print the full derived hardw
openssl-encrypt has non-cryptographic PRNG used for steganography pixel selection
openssl-encrypt silently skips schema validation when jsonschema library is not installed
openssl-encrypt has visible password in process list via --password CLI argument
openssl-encrypt: Dynamic .so loading for Whirlpool uses broad glob pattern without integrity verification
NLTK version 3.9.4 is vulnerable to a path traversal attack due to an incomplete fix for GitHub Issue #3504. The `_UNSAFE_NO_PROTOCOL_RE` regex in `nltk/data.py` checks for literal `../` sequences but
atomic-agents-stack: Dashboard HTTP server path traversal allows arbitrary file read
Pydantic AI: Unvalidated UploadedFile references in UI adapters allow server-side file access using the application's credentials
GitPython: Arbitrary file overwrite via git diff --output argument injection in Diffable.diff (key- and value-controlled)
GitPython: Incomplete unsafe_git_clone_options denylist omits --template enabling arbitrary command execution via clone hooks
GitPython: Arbitrary file truncation via git rev-list --output argument injection in unguarded Commit.count
GitPython: Unguarded git option forwarding in IndexFile.checkout() and TagReference.create() enables arbitrary file overwrite and arbitrary file read
GitPython: Environment-variable exfiltration via Repo.create_remote() / Remote.add() URL (incomplete fix of GHSA-rwj8-pgh3-r573)
GitPython: Unsafe git option guard bypass via single-character kwarg value token smuggling enables arbitrary command execution
Erkennen Sie Schwachstellen in Ihrer Anwendung
Mit der DockRay-Integration und aktivierter Softwareinventarisierung prüft DockRay gemeldete Komponentenversionen auf bekannte Schwachstellen und benachrichtigt Sie über bestätigte Treffer. Die Abdeckung hängt von der unterstützten Technologie und den verfügbaren Meldungen ab.