CVE-2015-7755
Exploitation confirmed. First attested on 2025-10-02 by CISA-ADP, CISA KEV, GCVE · kevintel.
- Published2015-12-19
- WeaknessCWE-287
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
Juniper ScreenOS 6.2.0r15 through 6.2.0r18, 6.3.0r12 before 6.3.0r12b, 6.3.0r13 before 6.3.0r13b, 6.3.0r14 before 6.3.0r14b, 6.3.0r15 before 6.3.0r15b, 6.3.0r16 before 6.3.0r16b, 6.3.0r17 before 6.3.0r17b, 6.3.0r18 before 6.3.0r18b, 6.3.0r19 before 6.3.0r19b, and 6.3.0r20 before 6.3.0r21 allows remote attackers to obtain administrative access by entering an unspecified password during a (1) SSH or (2) TELNET session.
Timeline
dates in UTC- 2015-12-1914:59CVE publishedNVD
- 2025-10-02Listed as exploited by GCVEGCVE
- 2025-10-02Exploitation first reportedCISA KEV
- 2025-10-02Added to the CISA KEV catalogCISA KEV
- 2025-10-0203:55SSVC exploitation set to activeCISA-ADP
- 2026-10-2319:23First public proof of conceptPoC-in-GitHub
- 2026-10-2319:23EPSS crossed 10 %FIRST EPSS
Observed activity
isMalicious corpus · updated 2026-10-23 18:48 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2015-7755?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2015-7755?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 6.3 | = 6.3.0 | no fix published | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
- CISA’s required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.due 2025-10-23
Advisories and patches
- kb.juniper.netVendor Advisory
- forums.juniper.netVendor Advisory
Detection
read 2026-10-23 19:23 UTC- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- 2 repositories, unverifiedhdm/juniper-cve-2015-7755cinno/CVE-2015-7755-POC PoC-in-GitHub
CISA Known Exploited Vulnerability
- Date Added
- 2025-10-02
- Patch Due Date
- 2025-10-23
- Ransomware Use
- Unknown
- Required Action
- Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Sources
- CISA KEVKEV entry2025-10-02
- GCVEexploitation2025-10-02
- CISA-ADPSSVC decisionactive2025-10-02
- OpenCVESSVC decisionactive—
- CISA-ADPCVSS 3.19.82025-10-01
- NVDCVSS 3.19.8read 2026-10-23
- NVDCVSS 2.010read 2026-10-23
- CISA-ADPweakness (CWE)CWE-2872025-10-01
- NVDweakness (CWE)CWE-287read 2026-10-23
- FIRST EPSSEPSS score61.1 %read 2026-10-23
- PoC-in-GitHubproof of concept2read 2026-10-23
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Published
- 2015-12-19
- Last Modified
- 2026-06-17
- NVD status
- Analyzed
Frequently asked questions
What is CVE-2015-7755?
Is CVE-2015-7755 actively exploited?
What is the CVSS score for CVE-2015-7755?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- For a threat intelligence platform: malware, C2 and ransomware indicators over STIX/TAXII.
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.