CVE-1999-0013: High severity SSH ssh vulnerability

Published Jan 22, 1998
·
Updated

Stolen credentials from SSH clients via ssh-agent program, allowing other local users to access remote accounts belonging to the ssh-agent user.

Affected Software

15 affected components
SSH ssh=1.2.0
SSH ssh=1.2.1
SSH ssh=1.2.2
SSH ssh=1.2.3
SSH ssh=1.2.4
SSH ssh=1.2.5
SSH ssh=1.2.6
SSH ssh=1.2.7
SSH ssh=1.2.8
SSH ssh=1.2.9
SSH ssh=1.2.10
SSH ssh=1.2.11
SSH ssh=1.2.12
SSH ssh=1.2.13
SSH ssh=1.2.14

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Remove

    Remove ssh-agent (SSH) from your environment.

    Uninstall or remove the ssh-agent program from systems where it is not required.

  2. Configuration

    Disable or stop ssh-agent on systems where it is not required to prevent credentials from being exposed to other local users.

    ssh-agent (SSH) enabled = false
  3. Compensating control

    Ensure local users cannot access another user's ssh-agent socket (SSH_AUTH_SOCK); restrict filesystem permissions and local access so the agent socket is not reachable by other accounts.

  4. Operational

    Assume credentials may be compromised: rotate SSH keys/credentials and revoke any keys or sessions that may have been exposed.

Event History

Jan 22, 1998
CVE Published
05:00 AM
Data Sourced
via NVD·05:00 AM
DescriptionSeverityWeaknessAffected Software
Sep 29, 1999
CVE Published
via MITRE·08:00 AM
Data Sourced
via MITRE·08:00 AM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-1999-0013?

CVE-1999-0013 is considered a moderate severity vulnerability due to the unauthorized access it can allow to remote accounts.

2

How do I fix CVE-1999-0013?

To fix CVE-1999-0013, upgrade your SSH client to a version greater than 1.2.14 which addresses this vulnerability.

3

Who is affected by CVE-1999-0013?

Users of SSH versions 1.2.0 through 1.2.14 are affected by CVE-1999-0013 due to the use of the vulnerable ssh-agent program.

4

What are the risks of not addressing CVE-1999-0013?

Not addressing CVE-1999-0013 can lead to compromised user accounts and unauthorized access to sensitive remote services.

5

Is CVE-1999-0013 still relevant today?

While CVE-1999-0013 pertains to older SSH versions, it remains a significant case study in credential theft risks for local environments.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203