CVE-2025-30118
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 · uneditedAn issue was discovered on the Audi Universal Traffic Recorder 2.88. It has Susceptibility to denial of service. It uses the same default credentials for all devices and does not implement proper multi-device authentication, allowing attackers to deny the owner access by occupying the only available connection. The SSID remains broadcast at all times, increasing exposure to potential attacks.
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 · moderate confidenceThe Audi Universal Traffic Recorder 2.88 uses identical default credentials across all deployed devices and lacks proper multi-device authentication, allowing an attacker to occupy the single available connection slot and deny the owner access. The device continuously broadcasts its SSID, increasing its visibility and attack surface to unauthorized parties.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 Audi Universal Traffic Recorder device on your networkScan your network for devices broadcasting an SSID containing 'Audi', 'Universal Traffic Recorder', or similar branding. Alternatively, check your router's connected devices list for unknown devices.Affected if A device matching this description is present on your network and responds to queries.
-
Determine the device firmware versionAccess the device's web interface or companion mobile application and navigate to the settings or about section to view the installed firmware version.Affected if The firmware version is 2.88 or falls within the affected release range.
-
Verify if default credentials are in useAttempt to log into the device's web interface using common default credentials such as admin/admin, admin/1234, or the credentials documented in the product manual. Check if the login succeeds without requiring a password change on first access.Affected if Default credentials (admin/admin, admin/1234, or similar) successfully authenticate to the device.
-
Check SSID broadcast configurationAccess the device wireless settings through its web interface or mobile app and verify whether SSID broadcast is enabled or if it can be disabled.Affected if SSID broadcast is continuously enabled with no option to disable it.
-
Confirm single connection slot limitationAttempt to access the device from two different client devices simultaneously, or check the device specifications and settings to confirm only one concurrent connection is allowed.Affected if Only a single concurrent connection is permitted and a second connection attempt is rejected or displaces the first.
You are affected if you own an Audi Universal Traffic Recorder running firmware 2.88 that is using default credentials and has SSID broadcast enabled, allowing an attacker to hijack the single connection slot.
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 dataChange default credentials to unique, strong passwords per device and implement multi-device authentication to prevent connection hijacking. Consider disabling SSID broadcast when not actively needed to reduce exposure.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-30118 — 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-2025-30118 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