CVE-2024-34713

What it is

sshproxy is used on a gateway to transparently proxy a user SSH connection on the gateway to an internal host via SSH. Prior to version 1.6.3, any user authorized to connect to a ssh server using `sshproxy` can inject options to the `ssh` command executed by `sshproxy`. All versions of `sshproxy` are impacted. The problem is patched starting in version 1.6.3. The only workaround is to use the `force_command` option in `sshproxy.yaml`, but it's rarely relevant.

At a glance

Exploitability

Can be exploited over the network with a low-privilege account, but needs a user to act. Limited direct impact.

Exploit odds

0.4% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2024-05-14 16:17 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 07:33 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.4% in the next 30 days (EPSS).
• Severity: 3.5 LOW (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2024-05-14 16:17 UTC

Last modified

2026-06-17 07:33 UTC

Exploit probability

0.4% · EPSS, next 30 days

Weakness

CWE-77 · Command injection

Record status

Deferred

Attack profile CVSS 3.1 · 3.5

Attack vector

Network

Complexity

Low

Privileges needed

Low

User interaction

Required

Scope

Unchanged

Confidentiality

Low

Integrity

None

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2024-34713.md and follow it. Check whether this project is affected by CVE-2024-34713. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge