What is the CVSS score of CVE-2013-4484?

CVE-2013-4484 has a CVSS 2.0 base score of 5.0 (Medium). CVSS vector: AV:N/AC:L/Au:N/C:N/I:N/A:P. EPSS exploitation probability: 1.6%.

Is there a public PoC exploit available for CVE-2013-4484?

Yes, a public proof-of-concept exploit is available for CVE-2013-4484. Prioritise patching immediately. EPSS: 1.6%.

Varnish CVE-2013-4484

MEDIUM

Buffer Overflow (CWE-119)

2013-11-01 secalert@redhat.com

Buffer Overflow Denial Of Service Varnish Varnish Cache

5.0

CVSS 2.0 · NVD

Severity by source

NVD PRIMARY

5.0 MEDIUM

AV:N/AC:L/Au:N/C:N/I:N/A:P

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

AV:N/AC:L/Au:N/C:N/I:N/A:P

Attack Vector

Network

Attack Complexity

Low

Confidentiality

None

Integrity

None

Availability

Lifecycle Timeline

CVE Published

Nov 01, 2013 - 02:55 cve.org

MEDIUM 5.0

DescriptionCVE.org

Varnish before 3.0.5 allows remote attackers to cause a denial of service (child-process crash and temporary caching outage) via a GET request with trailing whitespace characters and no URI.

AnalysisAI

Varnish before 3.0.5 allows remote attackers to cause a denial of service (child-process crash and temporary caching outage) via a GET request with trailing whitespace characters and no URI. Rated medium severity (CVSS 5.0), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available and no vendor patch available.

Technical ContextAI

This vulnerability is classified as Buffer Overflow (CWE-119), which allows attackers to corrupt memory to execute arbitrary code or crash the application. Varnish before 3.0.5 allows remote attackers to cause a denial of service (child-process crash and temporary caching outage) via a GET request with trailing whitespace characters and no URI. Affected products include: Varnish-Cache Varnish, Varnish Cache Project Varnish Cache. Version information: before 3.0.5.

RemediationAI

No vendor patch is available at time of analysis. Monitor vendor advisories for updates. Use memory-safe languages or bounds-checking. Enable ASLR, DEP/NX, stack canaries. Use safe string functions.