dbcve.org
Path TraversalWeakness · CWE-22

CVE-2023-35812

MEDIUM · 5.3 CVSS v3.1 Published 2024-04-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An issue was discovered in the Amazon Linux packages of OpenSSH 7.4 for Amazon Linux 1 and 2, because of an incomplete fix for CVE-2019-6111 within these specific packages. The fix had only covered cases where an absolute path is passed to scp. When a relative path is used, there is no verification that the name of a file received by the client matches the file requested. Fixed packages are available with numbers 7.4p1-22.78.amzn1 and 7.4p1-22.amzn2.0.2.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

OpenSSH 7.4 packages for Amazon Linux 1 and 2 contain an incomplete fix for CVE-2019-6111. The original patch only verified file names when absolute paths were used in scp commands; when relative paths are used, the client does not verify that the received file name matches the requested file, allowing a malicious server to send different files than requested.

MitigationApply the fixed OpenSSH packages (7.4p1-22.78.amzn1 for Amazon Linux 1 or 7.4p1-22.amzn2.0.2 for Amazon Linux 2) via the package manager to address the relative path verification gap.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify your Amazon Linux version
    Run 'cat /etc/system-release' or 'cat /etc/os-release' to determine if you are on Amazon Linux 1 or Amazon Linux 2
    Affected if The system is not Amazon Linux 1 or Amazon Linux 2 (other distributions are not affected by this specific CVE)
  2. Check installed OpenSSH version
    Run 'rpm -qa | grep openssh' or 'ssh -V' to list the installed OpenSSH packages and version
    Affected if OpenSSH version shown is 7.4p1 but the package is earlier than 22.78.amzn1 (AL1) or 22.amzn2.0.2 (AL2)
  3. Verify scp binary version
    Run 'rpm -qf /usr/bin/scp' to get the package name, then 'rpm -q --changelog openssh-clients' to see if the fix for CVE-2019-6111 is fully applied
    Affected if The scp package is the original 7.4p1 version without the later security updates that address the relative path verification gap
  4. Confirm scp usage with relative paths is possible
    Review any scripts or automation that use scp with relative paths (e.g., 'scp user@host:file .' instead of absolute paths)
    Affected if You use scp commands with relative path syntax to receive files from remote servers (the vulnerability only triggers when relative paths are used in scp commands)

You are affected if you run Amazon Linux 1 or 2 with OpenSSH 7.4 packages earlier than 22.78.amzn1 (AL1) or 22.amzn2.0.2 (AL2), and you use scp to copy files from remote servers using relative path syntax.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the fixed OpenSSH packages (7.4p1-22.78.amzn1 for Amazon Linux 1 or 7.4p1-22.amzn2.0.2 for Amazon Linux 2) via the package manager to address the relative path verification gap.

Recommended fix High confidence

OpenSSH 7.4p1-22.78.amzn1 (Amazon Linux 1) or 7.4p1-22.amzn2.0.2 (Amazon Linux 2)

  1. 1. Determine your Amazon Linux version by running 'cat /etc/system-release' or 'amazon-linux-version'
  2. 2. For Amazon Linux 1: Run 'sudo yum update openssh-clients' to upgrade to version 7.4p1-22.78.amzn1
  3. 3. For Amazon Linux 2: Run 'sudo yum update openssh-clients' to upgrade to version 7.4p1-22.amzn2.0.2
  4. 4. Verify the installed version by running 'rpm -qa | grep openssh'
Caveat Standard OpenSSH upgrade; no major breaking changes expected for typical SSH/SCP usage

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-35812 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-35812 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data