CVE-1999-1369: Medium severity realnetworks realserver vulnerability
Real Media RealServer (rmserver) 6.0.3.353 stores a password in plaintext in the world-readable rmserver.cfg file, which allows local users to gain privileges.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Remove
Remove
RealNetworks RealServer (rmserver)from your environment.If the server is not required, uninstall RealServer to eliminate the vulnerable component.
- Configuration
Change filesystem permissions on rmserver.cfg so it is not world-readable; ensure only the rmserver service account and/or root can read the file (for example, restrict to 0600 or equivalent ACLs).
RealNetworks RealServer (rmserver) rmserver.cfg file permissions = remove world-readable access (restrict to service account/root) - Compensating control
Until the file permissions and credentials are remediated, restrict local user access to the host (limit interactive logins, tighten filesystem ACLs, and isolate the server) to reduce the risk of privilege escalation.
- Operational
Rotate any passwords or credentials stored in rmserver.cfg after fixing file permissions, and audit for any accounts that may have been accessed by local users.
Event History
Frequently Asked Questions
What is the severity of CVE-1999-1369?
CVE-1999-1369 has a severity level that allows local users to gain unauthorized privileges due to password exposure.
How do I fix CVE-1999-1369?
To fix CVE-1999-1369, you should secure the rmserver.cfg file by changing its permissions to restrict access.
What software versions are affected by CVE-1999-1369?
CVE-1999-1369 affects Real Media RealServer version 6.0.3.353.
What are the implications of CVE-1999-1369?
The implications of CVE-1999-1369 include potential local privilege escalation by unauthorized users.
Can CVE-1999-1369 be exploited remotely?
CVE-1999-1369 primarily involves local exploitation, as it requires access to the machine where RealServer is installed.