A vulnerability in Go's crypto/x509 package used by Red Hat's Service Telemetry Framework (STF) allows man-in-the-middle attacks via untrusted intermediate certificates. The certificate verification process fails to block trust in intermediate certificates from compromised Certificate Authorities, enabling attackers to impersonate legitimate servers during secure connections. This flaw affects Go-based clients or servers relying on standard certificate verification and requires specific network positioning and attacker-controlled certificates. Red Hat has released STF components version 1.5.7 to address this issue.
This is a call for volunteers to test telemetry and logging on a honeypot environment designed to capture automated attacks and brute-force attempts. The honeypot is accessible via SSH through a public remote port forwarding service (serveo.net). The request is for participants to run attack tools against the honeypot to generate live traffic for research purposes. No specific vulnerability or exploit is described, and the environment is isolated for research. The service used for port forwarding is a developer tool that exposes local servers to the internet securely via SSH or WireGuard tunnels.
Windows 11's input pipeline causes typed passwords from third-party applications like PuTTY, WinSCP, and MySQL to appear in system process memory such as LSASS.exe, Defender (MsMpEng.exe), and ctfmon.exe. This is due to Windows telemetry and text input buffering, not malicious credential harvesting. Passwords may remain in ctfmon.exe memory even after application closure, posing a risk if non-admin malware accesses that process. Credential Guard does not protect these third-party passwords as they are not Windows authentication credentials. This behavior is architectural and expected, not a vulnerability, but it creates a real risk of password exposure through memory forensics or malware. Mitigations include using secure credential APIs, key-based authentication, password managers with secure injection, and avoiding typing passwords into standard text input fields.
FastNetMon Community Edition through 1.2.9 does not verify TLS certificates on outbound HTTPS connections. The execute_web_request_secure() function in src/fast_library.cpp creates a boost::asio::ssl::context with tls_client mode and calls set_default_verify_paths() to load CA certificates, but never calls set_verify_mode(boost::asio::ssl::verify_peer). Without this call, OpenSSL performs the TLS handshake without validating the server's certificate chain, making all HTTPS connections vulnerable to man-in-the-middle attacks. This function is used for telemetry reporting to community-stats.fastnetmon.com, which sends system information including CPU model, kernel version, traffic statistics, and software configuration. An attacker can intercept and modify this data or redirect it to a malicious server.
OpenTelemetry.Exporter.OpenTelemetryProtocol is the OTLP (OpenTelemetry Protocol) exporter implementation. From 1.8.0 to 1.15.2, the OTLP disk retry feature in OpenTelemetry.Exporter.OpenTelemetryProtocol silently fell back to Path.GetTempPath() when OTEL_DOTNET_EXPERIMENTAL_OTLP_RETRY=disk was set but OTEL_DOTNET_EXPERIMENTAL_OTLP_DISK_RETRY_DIRECTORY_PATH was not configured. The exporter stored and loaded *.blob files under fixed, signal-named subdirectories (traces, metrics, logs) beneath that shared temporary root path. On multi-user systems where the temporary directory is accessible to other local accounts, this allows an attacker to write crafted *.blob files, read *.blob files written by the application between export failures, or deposit numerous or oversized blob files, degrading retry-loop performance or consuming disk space. This vulnerability is fixed in 1.15.3.