Safeguard
Vulnerability Analysis•

CVE-2019-16638: High Recoverable Passwords on Ruijie EG-2000 Gateway

CVE-2019-16638 is a 7.5 High flaw on Ruijie EG-2000SE gateways: stored passwords can be recovered from the config file. No fix is confirmed; rotate them.

Safeguard Security Team
3 min read

CVE-2019-16638 is a high severity flaw, scored 7.5, on the Ruijie EG-2000SE gateway running EG_RGOS 11.1(1)B1. Passwords stored in the configuration file can be recovered with simple XOR operations. No fixed version is confirmed, so contact the vendor and rotate credentials.

What's affected

  • Product: Ruijie EG-2000 series gateway, confirmed for the EG-2000SE running EG_RGOS 11.1(1)B1.
  • Affected: the record names that firmware build. Other builds were not tested in the source.
  • Fixed: no fixed version is named in the record or in the researcher write-up. Ask Ruijie for a statement.
  • Severity: 7.5 High (AV:N/AC:L/PR:N/UI:N, confidentiality only).
  • Weakness: NVD tags it CWE-312, cleartext storage of sensitive information. The researcher write-up labels it CWE-257, storing passwords in a recoverable format. Both are in the sources.

How to check if you're exposed

  • Find out whether you operate Ruijie EG-2000 series gateways. Check the asset inventory for the model and the firmware string shown in the device web interface.
  • Compare the firmware to EG_RGOS 11.1(1)B1, the build named in the record.
  • Ask who can read the configuration on those devices: administrators, backup systems, network management tools and anyone who holds exported configuration files.
  • Search configuration backups stored outside the device. The weakness concerns what is stored in the file, so every copy is in scope.

What to do now

  1. Contact Ruijie for a fixed firmware or a written mitigation, and record the answer.
  2. Rotate every password that is stored on the gateway, assuming old configuration copies are readable.
  3. Restrict management access to a trusted network and keep configuration exports in a protected location.
  4. Where the gateway protects something important, plan to replace it if the vendor will not fix the storage of credentials.

Why it matters

The researcher write-up says passwords in the configuration file were obfuscated with a simple XOR and a fixed table rather than protected with a one way hash. Anyone who can read the file can reverse the obfuscation. This post does not reproduce the method.

The write-up covers several other flaws in the same product family, each with its own CVE. The one in this record is only about stored passwords. The KEV flag is false, and the write-up does not report exploitation in the wild. The CWE difference between NVD and the researcher is a labelling issue, not a disagreement about the facts.

Quick check

Why do two sources give different weakness numbers?

NVD uses CWE-312 for cleartext storage. The researcher wrote CWE-257 for recoverable password storage. They are neighbouring classes and describe the same behaviour.

Is hashing the answer?

For stored passwords, a salted one way hash is the standard answer, because it avoids storing anything that can be reversed. Where a device must replay a credential, protect the file and limit who can read it.

Sources

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

We email you a link to confirm, and only then add you to the list. Unsubscribe in one click. Privacy

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.