CVE-2017-14016 — CVE & Security Advisory Radar

🎯 CVE-2017-14016 🧪 PoC 🇪🇺 EUVD

📄 .md Alle CVEs anzeigen ✕

CVE-2017-14016 | A Stack-based Buffer Overflow issue was discovered in Advantech WebAccess versions prior to V8.2_20170817. The application lacks proper validation of the length of user-supplied data prior to copying it to a stack-based buffer, which could allow an attacker to execute arbitrary code under the context of the process.

A Stack-based Buffer Overflow issue was discovered in Advantech WebAccess versions prior to V8.2_20170817. The application lacks proper validation of the length of user-supplied data prior to copying it to a stack-based buffer, which could allow an attacker to execute arbitrary code under the context of the process.

Klassifikation & Betroffenheit:

n/a Advantech WebAccess Advantech WebAccessadvantech webaccess *

Improper Restriction of Operations within the Bounds of a Memory Buffer 🎯 High

The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data.

🛡️ Empfohlene Mitigation: Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, many languages that perform their own memory management, such as Java and Perl, are not subject to buffer overflows. Other languages, such as Ada and C#, typically provide overflow prot…

Vollständige Definition bei MITRE ➔

⚔️ Typische Angriffsmuster (CAPEC):

CAPEC-10 · Buffer Overflow via Environment Variable… (High) CAPEC-14 · Client-side Injection-induced Buffer Ove… (High) CAPEC-24 · Filter Failure through Buffer Overflow (High) CAPEC-42 · MIME Conversion (High) CAPEC-44 · Overflow Binary Resource File (Very High) CAPEC-45 · Buffer Overflow via Symbolic Links (High) CAPEC-100 · Overflow Buffers (Very High) CAPEC-123 · Buffer Manipulation (Very High)

🧩 Ähnliche Schwachstellen (Hersteller/Klasse/Score-Band):

CVE-2026-78971 4.6 CVE-2026-75331 4.6 CVE-2025-59320 4.6 CVE-2026-35502 4.6 CVE-2026-20765 4.6

🧪 Exploit-Evidenz: EDB-43340 · Advantech WebAccess 8.2-2017.03.31 - Webvrpcs Service Opcode 80061 Sta verified

📚 Referenzen & Quellen:

🇪🇺 Original-Eintrag (ENISA EUVD) 🇺🇸 NVD-Eintrag

Ausnutzungs-Zeitleiste:

Reserviert 2017

Veröffentlicht 11/2017

Heute 18.09.

Veröffentlicht:06.11.2017

Aktualisiert:17.06.2026 01:05

Assigner (CNA):icscert

EUVD-ID:EUVD-2017-5531

Quellen: 🇪🇺 EUVD-Datenbank (ENISA) + 🇺🇸 NVD-Anreicherung · 24-h-Cache

CWE-119: Memory Corruption ✓ Offizieller Patch / Advisory verfügbar

💡 Gegenmaßnahme: Sicherheits-Update des Herstellers zeitnah einspielen und Netzwerksegmentierung prüfen.

Tier	2026-08-29	2026-09-17
≥90 %	4	0
≥50 %	4	0
≥10 %	3	0
<10 %	304	300

Datenquellen & Methodik: Primärquelle ist die EUVD der ENISA (laufender Datenbank-Sync, alle 15 Minuten), abgeglichen mit dem CISA-KEV-Katalog und der NVD — Detail-Dossiers reichern fehlende Felder live per NVD an — mit Fallback auf CIRCL vulnerability-lookup (EU/Non-Profit, aggregiert CVE-, GitHub- und OSV-Advisories). Der CISA-KEV-Katalog (Known Exploited Vulnerabilities, ~1.700 aktiv ausgenutzte Schwachstellen) wird bei jedem Sync vollständig neu geladen und kreuzreferenziert — filterbar über die KEV-Pille. CVSS 3.1 wird nach Ampel-Logik aus Verteidigersicht dekodiert; EPSS bezeichnet die 30-Tage-Exploit-Wahrscheinlichkeit (FIRST.org).

🇪🇺 ENISA EUVD 🇺🇸 NVD ⚠️ CISA KEV ⚡ EPSS

3.1 LOW

🇪🇺 EUVD

EPSS

16%

CVE-2017-14016 🌐 Netzwerk (Remote) 🔓 Keine Authentifizierung nötig

🧪 n/a

CVE-2017-14016 | A Stack-based Buffer Overflow issue was discovered in Advantech WebAccess versions prior to V8.2_20170817. The application lacks proper validation of the length of user-supplied data prior to copying it to a stack-based buffer, which could allow an attacker to execute arbitrary code under the context of the process.

CWE-119: Memory Corruption ✓ Offizieller Patch / Advisory verfügbar

💡 Gegenmaßnahme: Sicherheits-Update des Herstellers zeitnah einspielen und Netzwerksegmentierung prüfen.

06.11.2017

🛡️ Details ➔

Zero-Day & Vulnerability Intelligence Hub