5389 matches found
openam-CVE-2021-35464
openam CVE-2021-35464 tomcat command execution with echo. Project based on ysoserial and Java-Rce-Echo Building the project requires adding ysoserial.jar and jato-14.6.3.jar to dependencies. root@kitploit: POST /OpenAM/ccversion/Version HTTP/1.1 Host: php.local:8081 Upgrade-Insecure-Requests: 1...
CVE-2017-7269-Echo-PoC
CVE-2017-7269 Remote Code Execution Echo Verification Our team's analysis report on the CVE-2017-7269 vulnerability: https://ht-sec.org/cve-2017-7269-vulnerabilities/ The default PoC only launches calc.exe. Now it has been modified to respond to requests. The command format is:...
mtr
WHAT IS MTR? mtr combines the functionality of the 'traceroute' and 'ping' programs in a single network diagnostic tool. As mtr starts, it investigates the network connection between the host mtr runs on and a user-specified destination host. It sends probes to the destination with successively...
mosh
Mosh: the mobile shell Mosh is a remote terminal application that supports intermittent connectivity, allows roaming, and provides speculative local echo and line editing of user keystrokes. It aims to support the typical interactive uses of SSH, plus: Mosh keeps the session alive if the client...
GeoServer-Tools-CVE-2024-36401
GeoServer-Tools-CVE-2024-36401 CVE-2024-36401 Graphical Exploitation Tool, supports exploitation across various JDK versions, as well as echo and memory shell implementation. Affected versions: GeoServer 2.23.6 2.24.0 = GeoServer 2.24.4 2.25.0 = GeoServer 2.25.2 Recently during HW Red/Blue team...
CVE-2020-10199
CVE-2020-10199 Echo version, casually written untested bug root@kitploit: Usage: python http://127.0.0.1:8080 username password Reference: https://www.cnblogs.com/magic-zero/p/12641068.html...
CVE-2022-22947-POC
CVE-2022-22947-POC CVE-2022-22947 batch detection script. The echo command is not regex-filtered. Please use it for now; I will update later. Place url.txt in the script directory. Directly run: python 脚本.py Demo: After the scan is complete, a success.txt file will be generated. This script will...
Log4j2-RCE
Log4j2-RCE Log4j2 CVE-2021-44228 Reproduction and Echo Exploit...
pyc2
pyc2 simple c2 written in python2 to demonstrate security concepts. use icmp echo requests and replies to trade base64 encoded commands and replies. Video explaining some of the security concepts and implementation decisions: https://www.youtube.com/watch?v=DHrEn7oK9vQ requires scapy pip install...
mosh
Mosh：移动 Shell Mosh 是一个远程终端应用，支持间歇性连接、允许漫游，并提供用户按键的推测性本地回显和行编辑。 它旨在支持 SSH 的典型交互式使用场景，此外： Mosh 在客户端休眠或稍后唤醒、或暂时失去网络连接时保持会话活跃。 Mosh 允许客户端和服务器“漫游”并更换 IP 地址，同时保持连接存活。与 SSH 不同，Mosh 可在 Wi-Fi 网络之间切换、或从 Wi-Fi 切换到蜂窝数据再到有线以太网时使用。 Mosh...
CVE-2023-30212
CVE-2023-30212 Explotando vulnerabilidad en Ourphp versión 7.2.0 también conocido como CVE 2023 30212 Step 1. Descargar e instalar Docker en tu sistema Nota. Estoy usando Docker porque es rápido y fácil instalar ubuntu. Step 2. Configurar entorno Docker root@kitploit: docker pull ubuntu docker ru...
github.com/labstack/echo: Echo: Unauthorized Information Disclosure via URL Path Decoding Discrepancy
A flaw was found in Echo, a Go web framework. An attacker can exploit a disagreement in URL path decoding between the router and the static file handler. The router processes raw encoded paths, while the static file handler unescapes encoded forward slashes. This allows an attacker to bypass...
SUSE SLES12 Security Update : kernel (Live Patch 85 for SUSE Linux Enterprise 12 SP5) (SUSE-SU-2026:3820-1)
The remote SUSE Linux SLES12 host has a package installed that is affected by multiple vulnerabilities as referenced in the SUSE-SU-2026:3820-1 advisory. This update for the SUSE Linux Enterprise Kernel 4.12.14-122.320 fixes various security issues: The following security issues were fixed: -...
ECHO-FEA2-5EA1-2849
Bulletin has no description...
ECHO-26F2-ACDE-46CC
Bulletin has no description...
ECHO-1969-C688-A45C Keycloak's GHSA advisory (GHSA-rr5q-3xwr-f323) lists the affected range as < 26.6.3 with no lower bound, so by version string alone 25.0.6 is nominally in range. The actual vulnerability requires a generic parameter-length-limiting mechanism (OIDCProviderConfig's max-length-per-parameter config, TokenEndpoint's checkParameters() gate) that silently drops any oversized request parameter, including subject_token — the fix exempts token-shaped parameters from that drop via a new getTokenParameterNames() method. That length-limiting framework does not exist anywhere in 25.0.6 (same finding as CVE-2026-4634, investigated separately) — confirmed via source search, no getMaxLengthForTheParameter/checkParameters/length-cap mechanism exists on any OIDC grant-type endpoint. With no mechanism to silently drop an oversized subject_token, the described fallback to client-credentials cannot occur.
Bulletin has no description...
ECHO-7E4D-4229-7370
Bulletin has no description...
ECHO-1EC0-58D1-CB3D Keycloak's GHSA advisory (GHSA-gv3v-2cpp-3pmq) lists the affected package/range as org.keycloak:keycloak-quarkus-server < 26.5.6 with no lower bound, so by version string alone 25.0.6 is nominally in range. The actual vulnerable mechanism is the HTTP access log feature (config.HttpAccessLogOptions, HttpAccessLogPropertyMappers) added by the fix commit's PR to mask Authorization/Cookie headers in a verbose access-log pattern. That feature does not exist in 25.0.6 at all — confirmed via a full source search (no HttpAccessLogOptions.java, HttpAccessLogPropertyMappers.java, or any http-access-log config option anywhere in quarkus/config-api or quarkus/runtime). There is no access-log-pattern mechanism in this version capable of the described header disclosure.
Bulletin has no description...
ECHO-73AB-600D-62BE Caught by Cursor Bugbot review on PR #19827: the real vulnerability (GHSA-7xf9-4jfc-wgm4) is specific to Fine-Grained Admin Permissions V2's RealmPermissionsV2 treating manage-clients as equivalent to managing the special "admin-permissions" client, which then grants realm-wide admin power. RealmPermissionsV2 and the admin-permissions client concept do not exist in 25.0.6 — its older RealmPermissions.canManageAuthorizationDefault() has no per-ResourceServer parameter at all (it's a single, undifferentiated realm-wide check), so there is no "is this the special admin-permissions client" distinction for a narrow, upstream-faithful fix to attach to. An earlier patch here unconditionally removed MANAGE_CLIENTS from that check to close the described escalation, but that changes intended authorization behavior for every regular client's authorization management, not just a vulnerable path (upstream's real fix leaves the MANAGE_CLIENTS grant intact for non-admin-permissions clients) — reverted.
Bulletin has no description...