CVE-2016-3118: CRLF injection vulnerability in CA API Gateway (formerly Layer7 API Gateway) 7.1 before 7.1.04, 8.0 through 8.

This month

MEDIUM 6.5REMOTEDOWNGRADE

CVE-2016-3118 is a medium-severity flaw (CVSS 6.5) affecting api gateway. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

CRLF injection vulnerability in CA API Gateway (formerly Layer7 API Gateway) 7.1 before 7.1.04, 8.0 through 8.3 before 8.3.01, and 8.4 before 8.4.01 allows remote attackers to have an unspecified impact via unknown vectors.

Why this priority

Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	6.5 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.2% (top 31%)
CISA exploited list	No
Published	2016-04-06
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: broadcom

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2016-04-06 01:59 UTCPublished CVE record published
2026-06-17 00:45 UTCUpdated Record last modified

broadcom api gateway DOWNGRADE

Affected: 7.1 · 8.0 · 8.1 · 8.2 · 8.3 · 8.4

Fixed in: no fixed release known

Safe to downgrade to: a release before 7.1

1. Check installed version

apt-cache policy api-gateway || rpm -q api-gateway || api-gateway --version

2. No fixed release: DOWNGRADE to a release before 7.1 (Debian / Ubuntu)

apt-cache madison api-gateway sudo apt install api-gateway=<VERSION_BEFORE_7.1> sudo apt-mark hold api-gateway

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list api-gateway sudo dnf downgrade api-gateway-<VERSION_BEFORE_7.1> sudo dnf versionlock add api-gateway

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2016-3118?

api gateway: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2016-3118 being exploited?

CVE-2016-3118 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2016-3118 affect?

CVE-2016-3118 affects api gateway. Severity is medium (CVSS 6.5). CRLF injection vulnerability in CA API Gateway (formerly Layer7 API Gateway) 7.1 before 7.1.04, 8.0 through 8.3 before 8.3.01, and 8.4 before 8.4.01 allows remote attackers to have an unspecified impact via unknown vectors.

How urgent is CVE-2016-3118?

Priority 45/100. Remotely exploitable, no login, no user action

Related CVEs

CVE-2020-11979 HIGH 7.5 DOWNGRADE UPGRADE As mitigation for CVE-2020-1945 Apache Ant 1.10.8 changed the permissions of temporary files it created so tha
CVE-2018-5407 MEDIUM 4.7 MITIGATE MITIGATE Simultaneous Multi-threading (SMT) in processors can enable local users to exploit software vulnerable to timi
CVE-2020-1971 MEDIUM 5.9 UPGRADE MITIGATE The X.509 GeneralName type is a generic type for representing different types of names
CVE-2019-17566 HIGH 7.5 UPGRADE DOWNGRADE Apache Batik is vulnerable to server-side request forgery, caused by improper input validation by the "xlink:h
CVE-2019-15631 CRITICAL 9.8 UPGRADE UPGRADE Remote Code Execution vulnerability in MuleSoft Mule CE/EE 3.x and API Gateway 2.x released before October 31,

References

← Back to latest CVEs