CVE-2012-1493
HighSummary
Urządzenia F5 BIG-IP w wersjach 9.x przed 9.4.8-HF5, 10.x przed 10.2.4, 11.0.x przed 11.0.0-HF2 oraz 11.1.x przed 11.1.0-HF3, a także Enterprise Manager przed 2.1.0-HF2, 2.2.x przed 2.2.0-HF1 i 2.3.x przed 2.3.0-HF3, używają jednego klucza prywatnego SSH dla różnych instalacji klientów i nie ograniczają odpowiednio dostępu do tego klucza. To ułatwia zdalnym atakującym przeprowadzanie logowania SSH za pomocą opcji PubkeyAuthentication.
Risk Assessment
Ryzyko dla organizacji polega na tym, że zdalni atakujący mogą uzyskać dostęp do systemów klientów, co może prowadzić do nieautoryzowanego dostępu do danych i zasobów. Współdzielenie klucza prywatnego zwiększa podatność na ataki typu brute force oraz inne formy nieautoryzowanego dostępu.
Recommendation
Zaleca się aktualizację urządzeń F5 BIG-IP oraz Enterprise Manager do najnowszych wersji, które eliminują problem współdzielenia klucza prywatnego. Dodatkowo, należy wdrożyć odpowiednie mechanizmy zarządzania kluczami SSH, aby ograniczyć dostęp do kluczy prywatnych.
Related vulnerabilities
- CVE-2026-81855Critical
A hardcoded cryptographic client authentication key vulnerability exists in the robot testing framework component of Wärtsilä FOS-Onboard. The key is embedded in the software and cannot be changed by administrators.
- CVE-2026-78225Critical
A hardcoded cryptographic server key vulnerability exists in the deployer-ng Update Controller component of Wärtsilä FOS-Onboard. The key is embedded in the software and cannot be changed by administrators.
- CVE-2026-73807Critical
The mySCADA myPRO Manager command API does not properly enforce authentication for privileged functions. An unauthenticated attacker with network access to the affected API could exploit this vulnerability to access privileged management functions.
- CVE-2026-73437Critical
On affected platforms running Arista EOS with Dynamic Host Configuration Protocol (DHCP) relay configured, an unauthenticated attacker with network access could send a crafted DHCP reply packet from an IP address that is not configured as a helper address, and the relay agent would forward it to clients without validating the source.
- CVE-2026-61560Critical
`@zereight/mcp-gitlab` is a Model Context Protocol server for GitLab. Prior to version 2.1.27, the SSE transport mode (`SSE=true`) exposes all MCP tools without any authentication. The `upload_markdown` tool reads arbitrary files from the server's local filesystem via an unsanitized `file_path` parameter and uploads them to a GitLab project.
- CVE-2026-91939Critical
Cotonti 1.0.0 Comments plugin passes the ci GET parameter to unserialize() without allowed_classes restriction, allowing unauthenticated attackers to instantiate arbitrary PHP classes with attacker-controlled properties. Attackers can exploit PHP object injection through crafted serialized payloads to trigger gadget chains and achieve database manipulation or code execution.
- CVE-2026-68491Critical
An insufficient check allowed for the overwrite of arbitrary files via a symlink. Technical details were not provided in the description.
- CVE-2026-66890Critical
The affected products use hard-coded credentials, which could allow remote access to files with root privileges where FTP is reachable. Technical details were not provided in the description.
- CVE-2026-66887Critical
The affected products are missing authorization on state-changing CGIs and session checks are not performed. Technical details were not provided in the description.
- CVE-2026-61568Critical
`@zereight/mcp-gitlab` is a Model Context Protocol server for GitLab. Versions prior to 2.1.30 expose the Streamable HTTP MCP endpoint without an effective Host or Origin allowlist. A malicious web page can use DNS rebinding to route browser requests to a victim's local MCP listener while preserving an attacker-controlled `Host` and `Origin`.
Original NVD description (English source)
F5 BIG-IP appliances 9.x before 9.4.8-HF5, 10.x before 10.2.4, 11.0.x before 11.0.0-HF2, and 11.1.x before 11.1.0-HF3, and Enterprise Manager before 2.1.0-HF2, 2.2.x before 2.2.0-HF1, and 2.3.x before 2.3.0-HF3, use a single SSH private key across different customers' installations and do not properly restrict access to this key, which makes it easier for remote attackers to perform SSH logins via the PubkeyAuthentication option.

