Security - RDS (Remote Development Services)

Configure remote development access and security settings

Overview

Remote Development Services (RDS) is a ColdFusion feature that gives development tools remote HTTP-based access to files and databases on your ColdFusion server. Adobe lists Dreamweaver, HomeSite+, ColdFusion Extensions for Eclipse, and the ColdFusion Report Builder as RDS clients (source: Use the ColdFusion administrator). Adobe recommends that you disable RDS for production servers. While useful for development, RDS provides significant server access and must be carefully controlled in production environments.

Critical Security Warning: RDS provides direct file system and database access to your server. It should be DISABLED on production servers and only enabled on development/staging environments with proper authentication and network restrictions.

RDS Configuration Settings

Control whether RDS is enabled and configure authentication requirements.

Enable RDS Service

PurposeEnable or disable Remote Development Services functionality
DefaultConfigurable at install time; Secure Profile disables it
RecommendationProduction: Disabled (always)
Staging: Disabled or restricted by IP
Development: Enabled with strong password
ImpactWhen enabled, remote tools can access files and databases. Disabling RDS also disables the directory browsing applets in the Administrator.
Security Risk: Enabling RDS on production servers exposes your file system, database connections, and server resources to potential unauthorized access. Only enable on isolated development environments.

RDS Password

PurposeAuthentication password required for RDS connections
DefaultSet during ColdFusion installation; 5 to 50 characters
RecommendationAlways use a strong, unique password (16+ characters, mixed case, numbers, symbols)
SecuritySingle password protects all RDS access - compromise grants full server access
Best Practices:
  • Use password manager to generate and store complex password
  • Never use the same password as the ColdFusion Administrator
  • Rotate password regularly (every 90 days minimum)
  • Never share RDS passwords via email or chat
  • Change immediately if compromise suspected

RDS Authentication

PurposeChoose how RDS clients authenticate
OptionsSingle password: All RDS users share the RDS password
Separate user name and password: Each developer signs in with an individual account created in the User Manager and granted RDS access
RecommendationUse separate user names and passwords so access can be granted and revoked per developer
Defense in Depth: Individual accounts mean one leaked credential does not expose every developer's access, and the RDS password should never match the Administrator password.

What RDS Provides Access To

Understanding the scope of access granted when RDS is enabled.

File System Access

Capabilities
Browse, read, edit, create, delete files
Scope
Full server file system (subject to OS permissions)
Risk Level
Critical

Allows complete file system manipulation including CFM templates, configuration files, and data.

Database Access

Capabilities
Query all configured datasources
Scope
Full database read/write access
Risk Level
Critical

Direct SQL execution against all configured databases with datasource privileges.

Debugging Access

Capabilities
Remote debugging sessions
Scope
Inspect variables, step through code
Risk Level
High

View application variables, session data, and execution flow in real-time. Adobe lists RDS as a prerequisite for the ColdFusion Builder extension's step debugger (source: Adobe: Debug applications).

Configuring RDS in Development Tools

IDE Connections

End of life: Adobe ColdFusion Builder reached end of life on October 1, 2024. Adobe now focuses on the ColdFusion Builder extension for Visual Studio Code as the IDE for ColdFusion.

In any RDS client, enter the server host name, the port of the web server that serves ColdFusion, and the RDS credentials. Use HTTPS for connections over untrusted networks. Check your tool's own documentation for the exact menu path.

Security Best Practices

Production Environment

Mandatory Security Requirements:
  • Disable RDS completely - No exceptions for production
  • Verify RDS is disabled in administrator before deployment
  • Block /CFIDE/main/ide.cfm (the RDS endpoint) at the web server; RDS has no dedicated port
  • Remove or restrict /CFIDE directory web access
  • Include RDS disabled check in deployment checklist
  • Monitor logs for any RDS connection attempts
Compliance: Adobe recommends disabling RDS on production servers, and security audits commonly flag it when enabled.

Development Environment

Secure RDS Usage Guidelines:
  • Enable RDS only on local development machines
  • Use strong, unique passwords (16+ characters)
  • Use separate user name and password RDS authentication, and never reuse the Administrator password
  • Never expose the RDS endpoint to the internet
  • Use VPN for remote RDS access if absolutely required
  • Restrict access by IP address when possible
  • Disable RDS when not actively developing
  • Use HTTPS for all RDS connections
  • Rotate RDS passwords quarterly

Alternatives to RDS

File AccessUse SFTP, SCP, or file sync tools (rsync, WinSCP)
More secure with granular access control
Database AccessUse dedicated database clients (DataGrip, DBeaver, MySQL Workbench)
Direct database connection with better security
DebuggingUse FusionReactor or ColdFusion debugging output
CommandBox server for local development
Modern Development Workflow: Most developers have moved away from RDS in favor of Git-based version control, SFTP deployment, and dedicated database tools. Consider adopting these more secure alternatives.

RDS Network Exposure

Where RDS Is Reachable

HTTP Port8500 (default for standalone ColdFusion)
J2EE DeploymentUses web server port (80/443) with /CFIDE path
No Dedicated Port: RDS is a servlet mapped to /CFIDE/main/ide.cfm (see Adobe's JEE configuration guide) served on whatever port serves ColdFusion. Firewalling port 8500 only restricts the built-in web server (which also serves the Administrator and applications); it does not disable RDS behind IIS or Apache. Disable RDS in Security > RDS and block /CFIDE/main/ide.cfm at the web server.
Restricting the Built-in Web Server Port (Linux iptables)
# Restrict the built-in web server port (which also carries RDS)
# This does not affect RDS served through IIS or Apache
# Allow only from specific IP (replace with your IP)

# Block built-in web server HTTP port from all
iptables -A INPUT -p tcp --dport 8500 -j DROP

# Allow from trusted IP only
iptables -I INPUT -p tcp -s 192.168.1.100 --dport 8500 -j ACCEPT


# Allow from local network (adjust subnet as needed)
iptables -I INPUT -p tcp -s 192.168.1.0/24 --dport 8500 -j ACCEPT

# Save rules
service iptables save
# PowerShell commands for Windows Firewall

# Block built-in web server HTTP port (also carries RDS)
New-NetFirewallRule -DisplayName "Block RDS HTTP" `
  -Direction Inbound -LocalPort 8500 -Protocol TCP -Action Block

# Allow RDS from specific IP
New-NetFirewallRule -DisplayName "Allow RDS from Dev IP" `
  -Direction Inbound -LocalPort 8500 -Protocol TCP `
  -Action Allow -RemoteAddress 192.168.1.100

Common Issues & Solutions

Cannot Connect to RDS

Symptom: IDE shows "Cannot connect to RDS server" or timeout errors
Solutions:
  • Verify RDS is enabled in ColdFusion Administrator
  • Check ColdFusion service is running
  • Confirm correct port number (8500 default)
  • Verify the firewall allows the ColdFusion web port from your IP
  • Test connectivity: telnet server.com 8500
  • Check RDS password is correct
  • Review ColdFusion logs for authentication failures

RDS Authentication Failed

Symptom: "Authentication failed" or "Invalid password" errors
Solutions:
  • Verify RDS password in CF Administrator (Security → RDS)
  • Check whether RDS authentication uses a single password or separate user names, and use the matching credentials
  • Check for special characters that may need escaping
  • Reset RDS password in administrator and retry
  • Clear IDE's saved RDS credentials and re-enter

RDS Security Audit Failed

Symptom: Security audit or penetration test identifies RDS as vulnerability
Immediate Actions:
  • Disable RDS immediately on production servers
  • Verify RDS disabled: check Security → RDS in administrator
  • Block /CFIDE/main/ide.cfm at the web server and restrict the built-in web server port (8500 by default)
  • Restrict /CFIDE directory access in web server config
  • Review access logs for unauthorized RDS usage
  • Document remediation for audit report
  • Add RDS check to deployment verification checklist

Verifying RDS Status

Confirm on every production server that Enable RDS Service is unchecked under Security > RDS in the ColdFusion Administrator. As a second check, request /CFIDE/main/ide.cfm (the RDS endpoint) from outside your network and confirm the web server blocks it.

Related Resources

Security - RDS (Remote Development Services) | ColdFusion Administrator | CFGuide