CVE-2023-6930
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedEuroTel ETL3100 versions v01c01 and v01x37 suffer from an unauthenticated configuration and log download vulnerability. This enables the attacker to disclose sensitive information and assist in authentication bypass, privilege escalation, and full system access.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe EuroTel ETL3100 versions v01c01 and v01x37 contain an unauthenticated directory traversal or improper access control vulnerability that allows attackers to download configuration files and system logs without any authentication. This exposes sensitive credentials, system settings, and potentially API keys or session tokens that can be leveraged to bypass authentication mechanisms, escalate privileges, and achieve full administrative access to the device.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 01c01= 01x37CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelCheck the device web interface banner, SNMP sysDescr, or SSH login banner for 'ETL3100' or 'EuroTel' brandingAffected if Device is not an EuroTel ETL3100 unit (not affected)
-
Check the firmware versionAccess the device web interface system info page, or run 'show version' via CLI, or check the SNMP sysVersion OIDAffected if Firmware version is NOT 01c01 or 01x37 (not affected)
-
Test for unauthenticated directory traversalAttempt to access a known config file path via HTTP without providing credentials, for example: http://<device-ip>/../../etc/passwd or /config/system.cfg (use paths specific to the device's web server)Affected if Device returns configuration files or system logs WITHOUT requiring any login credentials (AFFECTED)
-
Verify config file exposureAttempt to download what appears to be a configuration or system log file (e.g., .cfg, .conf, .log, .xml files) from the device's web interface without authenticationAffected if Sensitive files containing credentials, API keys, or session tokens are accessible without authentication (AFFECTED)
You are affected if you have an ETL3100 device running firmware version 01c01 or 01x37 that allows downloading configuration files or system logs without any authentication credentials.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply vendor-supplied patches for ETL3100 v01c01 and v01x37; if no patch exists, restrict network access to the management interface via firewall or VLAN segmentation, and disable any unnecessary remote management services.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-6930 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-6930 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data