CVE-2015-0733

Home/CVE/CRLF injection vulnerability in the HTTP Header Handler in Digital Broadband Delivery System in Cisco Headend System Rel

CVE

↯ PDF report

CRLF injection vulnerability in the HTTP Header Handler in Digital Broadband Delivery System in Cisco Headend System Rel

CRLF injection vulnerability in the HTTP Header Handler in Digital Broadband Delivery System in Cisco Headend System Release allows remote attackers to inject arbitrary HTTP headers, and conduct HTTP response splitting attacks or cross-site scripting (XSS) attacks, via a crafted request, aka Bug ID CSCur25580.

MEDIUM · CVSS 4.3 EPSS 0.01546

EPSS exploitation odds1.55% · top 28%

Monitor

No active-exploitation, high-EPSS, or public-exploit signals - routine patching cadence

No Sigma yet — build one → YARA rules0

Look this up elsewhere - one-click external pivots

NVD CVE.org CISA Exploit-DB GitHub PoC VulnCheck KEV GreyNoise

▸ How to read a CVE - triage first, then detect and patch

This page is every public fact about CVE-2015-0733, cross-linked. Its job is to answer one question fast - does this need my attention now? - and then hand you the two things you do about it. Here is how an analyst reads it.

Triage: should I act now? Four signals, and they are not interchangeable:

CVSSseverity - how bad it is IF exploited, 0-10. A high CVSS alone is not urgency; a flaw can be a perfect 10 and never actually be attacked. EPSSprobability - a model’s estimate of the chance it is exploited in the next 30 days, 0-1. This is the “will it actually happen” signal. CISA KEVconfirmed - it is being exploited in the wild right now. The strongest signal on the page; KEV beats any score. Weaponisedavailability - public exploits / PoCs, and especially Metasploit modules rated Excellent / Great. Reliable, packaged exploit code means low-skill attackers can use it today.

How they combine: KEV, or a dependable Metasploit module, means patch now regardless of CVSS. High CVSS + low EPSS + no exploit is real but not an emergency - schedule it. Low CVSS but KEV-listed still gets patched now. The verdict above already weighed these for you; this is how it got there.

Then what - two workflows:

Detectwhen you cannot patch today, follow this CVE to the ATT&CK techniques it enables, then Build a SIEM detection (the green button) - author a rule, test it in Atomic, deploy it. That buys visibility while the patch waits. PatchAffected products / packages tell you if you are exposed; Fixed versions by distribution and Vendor advisories give the exact version that closes it.

Reading order for the panels below: verdict + badges, then Public exploits / Metasploit (is it weaponised), then ATT&CK techniques + Sigma / IDS rules (can I detect it), then Affected products / packages + Fixed versions (am I exposed, what patches it), then Threat actors / IOCs (who uses it), then Scoring & timeline / references (the evidence).

▣

Severity & exploitation scoring

CVSS base score

4.3

MEDIUMCVSS v3.1 · [email protected]

EPSS exploitation probability

1.55%

Top 28%odds of exploitation in the next 30 days

CVSS metric silhouette

No structured CVSS vector for this CVE. Older entries often have only a numeric base score - the metric breakdown radar requires a full AV:_/AC:_/... vector string published by NVD.

SSVC triage

No SSVC vulnrichment for this CVE. CISA's Vulnrichment program scores newer CVEs (~2024 onwards) plus selected older critical ones. Use the EPSS probability + KEV status to triage instead.

Lifecycle

30 May 2015Published to NVD
17 Jun 2026Last modified

Every entry is a recorded date - NVD publish/modify, CISA KEV add, public exploit disclosure. No inferred events.

Attack path

Full kill chain

→

◆

ATT&CK techniques

Techniques this CVE enables. Pills with a solid outline are high confidence - named directly in ATT&CK or Nuclei, or human-curated by CTID; the rest are inferred from the weakness type using MITRE's CVE Mapping Methodology and the CWE → CAPEC chain. Broad, generic-weakness guesses are filtered out. A small N× marks a technique that N independent sources agree on.

T1059.007 · JavaScript T1539 · Steal Web Session Cookie

▤ Build a SIEM detection for these techniques

▤

CAPEC attack patterns

Attack patterns this CVE enables - the bridge from weakness to ATT&CK technique.

CAPEC-CAPEC-105 · HTTP Request Splitting CAPEC-CAPEC-31 · Accessing/Intercepting/Modifying HTTP Cookies CAPEC-CAPEC-34 · HTTP Response Splitting CAPEC-CAPEC-85 · AJAX Footprinting

⬡

Weakness Classification

CWE-113Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Request/Response Splitting')

▤

Affected Products & Versions

cisco headend digital broadband delivery systemall versions

▤

Related CVEs

CVEs linked to this one by a shared weakness (CWE) or affected product - joins on data already in the engine, with the reason shown per row. Not a guess.

CVE-2007-5595 CRLF injection vulnerability in the drupal_goto function in includes/common.inc ... same CWE-113 CVE-2015-1445 HTTP header injection in the httpd package in fli4l before 3.10.1 and 4.0 before... same CWE-113 HIGH CVE-2016-5699 CRLF injection vulnerability in the HTTPConnection.putheader function in urllib2... same CWE-113 MEDIUM CVE-2016-6839 CRLF injection vulnerability in Huawei FusionAccess before V100R006C00 allows re... same CWE-113 MEDIUM CVE-2015-0724 Multiple cross-site scripting (XSS) vulnerabilities in dncs 7.0.0.12 in Cisco He... same product CVE-2015-0743 Cisco Headend System Release allows remote attackers to cause a denial of servic... same product CVE-2015-0744 Cisco DTA Control System (DTACS) 4.0.0.9 and Cisco Headend System Release allow ... same product CVE-2015-0745 Cisco Headend System Release allows remote attackers to read temporary script fi... same product

🔗

References & Sources

Source URLs (vendor pages, mailing lists, write-ups). Exploit/PoC links are in their own section above to avoid duplication.

http://tools.cisco.com/security/center/viewAlert.x?alertId=38863

Vendor Advisory

http://www.securitytracker.com/id/1032445

Third Party AdvisoryVDB Entry