Background For regular, unencrypted FTP traffic, the FTP ALG can inspect the unencrypted control channel and open related sessions for the FTP data channel. These related sessions (gates) are specific to source and destination IPs and ports of client and server. The design intent of the ftps-extensions option (which is disabled by default) is to provide similar functionality when the SRX secures the FTP/FTPS client. As the control channel is encrypted, the FTP ALG cannot inspect the port specific information and will open a wider TCP data channel (gate) from client IP to server IP on all destination TCP ports. In FTP/FTPS client environments to an enterprise network or the Internet, this is the desired behavior as it allows firewall policy to be written to FTP/FTPS servers on well-known control ports without using a policy with destination IP ANY and destination port ANY. Issue The ftps-extensions option is not intended or recommended where the SRX secures the FTPS server, as the wide data channel session (gate) will allow the FTPS client temporary access to all TCP ports on the FTPS server. The data session is associated to the control channel and will be closed when the control channel session closes. Depending on the configuration of the FTPS server, supporting load-balancer, and SRX inactivity-timeout values, the server/load-balancer and SRX may keep the control channel open for an extended period of time, allowing an FTPS client access for an equal duration.​ Note that the ftps-extensions option is not enabled by default.
This vulnerability carries a MEDIUM severity rating with a CVSS v3.1 score of 6.5, indicating it can be exploited remotely over the network with relatively low complexity without requiring user interaction and does not require pre-existing privileges . The vulnerability impacts limited data confidentiality, limited integrity, for affected systems. Impacting 28 products from juniper, from juniper, from juniper and 25 others, organizations running these solutions should prioritize assessment and patching.
Reported in 2020, this vulnerability emerged during an era marked by increased sophistication in supply chain attacks, cloud infrastructure vulnerabilities, and software-as-a-service (SaaS) security challenges. Security practices during this period emphasized zero-trust architectures, container security, and API protection.
2020-02-28T23:15:11.103
2024-11-21T02:32:52.517
Modified
CVSSv3.1: 6.5 (MEDIUM)
AV:N/AC:M/Au:N/C:P/I:P/A:N
8.6
4.9
| Type | Vendor | Product | Version/Range | Vulnerable? |
|---|---|---|---|---|
| Operating System | juniper | junos | 12.1x44 | Yes |
| Operating System | juniper | junos | 12.1x44 | Yes |
| Operating System | juniper | junos | 12.1x44 | Yes |
| Operating System | juniper | junos | 12.1x44 | Yes |
| Operating System | juniper | junos | 12.1x44 | Yes |
| Operating System | juniper | junos | 12.1x44 | Yes |
| Operating System | juniper | junos | 12.1x44 | Yes |
| Operating System | juniper | junos | 12.1x44 | Yes |
| Operating System | juniper | junos | 12.1x44 | Yes |
| Operating System | juniper | junos | 12.1x44 | Yes |
| Operating System | juniper | junos | 12.1x46 | Yes |
| Operating System | juniper | junos | 12.1x46 | Yes |
| Operating System | juniper | junos | 12.1x46 | Yes |
| Operating System | juniper | junos | 12.1x46 | Yes |
| Operating System | juniper | junos | 12.1x46 | Yes |
| Operating System | juniper | junos | 12.1x46 | Yes |
| Operating System | juniper | junos | 12.1x46 | Yes |
| Operating System | juniper | junos | 12.1x46-d10 | Yes |
| Operating System | juniper | junos | 12.1x47 | Yes |
| Operating System | juniper | junos | 12.1x47 | Yes |
| Operating System | juniper | junos | 12.1x47 | Yes |
| Operating System | juniper | junos | 12.1x47 | Yes |
| Operating System | juniper | junos | 12.3x48 | Yes |
| Operating System | juniper | junos | 12.3x48 | Yes |
| Operating System | juniper | junos | 12.3x48 | Yes |
| Operating System | juniper | junos | 15.1x49 | Yes |
| Hardware | juniper | srx100 | - | No |
| Hardware | juniper | srx110 | - | No |
| Hardware | juniper | srx1400 | - | No |
| Hardware | juniper | srx1500 | - | No |
| Hardware | juniper | srx210 | - | No |
| Hardware | juniper | srx220 | - | No |
| Hardware | juniper | srx240 | - | No |
| Hardware | juniper | srx240h2 | - | No |
| Hardware | juniper | srx300 | - | No |
| Hardware | juniper | srx320 | - | No |
| Hardware | juniper | srx340 | - | No |
| Hardware | juniper | srx3400 | - | No |
| Hardware | juniper | srx345 | - | No |
| Hardware | juniper | srx3600 | - | No |
| Hardware | juniper | srx380 | - | No |
| Hardware | juniper | srx4000 | - | No |
| Hardware | juniper | srx4100 | - | No |
| Hardware | juniper | srx4200 | - | No |
| Hardware | juniper | srx4600 | - | No |
| Hardware | juniper | srx5000 | - | No |
| Hardware | juniper | srx5400 | - | No |
| Hardware | juniper | srx550 | - | No |
| Hardware | juniper | srx550_hm | - | No |
| Hardware | juniper | srx550m | - | No |
| Hardware | juniper | srx5600 | - | No |
| Hardware | juniper | srx5800 | - | No |
| Hardware | juniper | srx650 | - | No |
SecUtils normalizes and enriches National Vulnerability Database (NVD) records by standardizing vendor and product identifiers, aggregating vulnerability metadata from both NVD and MITRE sources, and providing structured context for security teams. For juniper's affected products, we extract Common Platform Enumeration (CPE) data, Common Weakness Enumeration (CWE) classifications, CVSS severity metrics, and reference data to enable rapid vulnerability prioritization and asset correlation. This record contains no exploit code, proof-of-concept instructions, or attack methodologies—only defensive intelligence necessary for patch management, risk assessment, and security operations.