How severe is CVE-2007-5560?

CVE-2007-5560 has a CVSS 2.0 base score of 10.0, rated critical severity.

Is CVE-2007-5560 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 4% (90th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2007-5560?

CVE-2007-5560 affects Juniper Http Service. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2007-5560?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

When was CVE-2007-5560 published?

CVE-2007-5560 was published on 2007-10-18 and last updated on 2026-06-16.

CVE-2007-5560

CVE-2007-5560 is a critical-severity vulnerability in Juniper Http Service with a CVSS 2.0 base score of 10.0. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-119.

Key facts

Severity: Critical (CVSS 2.0 base score 10.0)
EPSS exploit prediction: 4% (90th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-119
Affected product: Juniper Http Service
Published: 2007-10-18
Last modified: 2026-06-16

Description

Heap-based buffer overflow in the Juniper HTTP Service allows remote attackers to execute arbitrary code via a crafted HTTP packet. NOTE: as of 20071016, the only disclosure is a vague pre-advisory with no actionable information. However, since it is from a well-known researcher, it is being assigned a CVE identifier for tracking purposes.

Frequently asked questions

What is CVE-2007-5560?: Heap-based buffer overflow in the Juniper HTTP Service allows remote attackers to execute arbitrary code via a crafted HTTP packet. NOTE: as of 20071016, the only disclosure is a vague pre-advisory with no actionable information. However, since it is from a well-known researcher, it is being assigned a CVE identifier for tracking purposes.
How severe is CVE-2007-5560?: CVE-2007-5560 has a CVSS 2.0 base score of 10.0, rated critical severity.
Is CVE-2007-5560 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 4% (90th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2007-5560?: CVE-2007-5560 affects Juniper Http Service. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2007-5560?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2007-5560 published?: CVE-2007-5560 was published on 2007-10-18 and last updated on 2026-06-16.

References

http://www.irmplc.com/index.php/111-Vendor-Alerts

Affected products (1)

cpe:2.3:a:juniper:http_service:*:*:*:*:*:*:*:*

Other CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer) vulnerabilities

CVE-2026-2778 — Critical (CVSS 10.0): Sandbox escape due to incorrect boundary conditions in the DOM: Core & HTML component. This vulnerability was fixed in…
CVE-2026-2776 — Critical (CVSS 10.0): Sandbox escape due to incorrect boundary conditions in the Telemetry component in External Software. This vulnerability…
CVE-2025-1866 — Critical (CVSS 10.0): Improper Restriction of Operations within the Bounds of a Memory Buffer vulnerability in warmcat libwebsockets allows…
CVE-2022-27625 — Critical (CVSS 10.0): A vulnerability regarding improper restriction of operations within the bounds of a memory buffer is found in the…
CVE-2022-27624 — Critical (CVSS 10.0): A vulnerability regarding improper restriction of operations within the bounds of a memory buffer is found in the…
CVE-2020-11896 — Critical (CVSS 10.0): The Treck TCP/IP stack before 6.0.1.66 allows Remote Code Execution, related to IPv4 tunneling.

Browse all CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer) vulnerabilities →