CVE-2022-42982
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 · uneditedBKG Professional NtripCaster 2.0.39 allows querying information over the UDP protocol without authentication. The NTRIP sourcetable is typically quite long (tens of kBs) and can be requested with a packet of only 30 bytes. This presents a vector that can be used for UDP amplification attacks. Normally, only authenticated streaming data will be provided over UDP and not the sourcetable.
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 confidenceBKG Professional NtripCaster 2.0.39 exposes its NTRIP sourcetable over UDP without requiring authentication, allowing remote attackers to request large data responses (tens of kilobytes) with minimal request packets (~30 bytes), creating a UDP amplification vector for denial-of-service attacks against third parties.
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<= 2.0.39CVSS 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 NtripCaster installation and versionLocate the NtripCaster installation directory and check the version information file, or run 'ntripcaster --version' if available from command lineAffected if Version is 2.0.39 or lower
-
Verify UDP port accessibilityCheck if UDP port 2101 (default NTRIP UDP port) is open and listening using 'netstat -uanp' or 'ss -uanp' and confirm the service is boundAffected if UDP port 2101 is open and accepting connections externally
-
Test UDP sourcetable access without authenticationSend a minimal UDP packet to the server on port 2101 (e.g., using 'echo -n "GET / HTTP/1.0\r\n\r\n" | nc -u target 2101' or similar UDP client) and observe if a large sourcetable response is returnedAffected if Large sourcetable data is returned without requiring any credentials
-
Confirm lack of authentication enforcementReview the NtripCaster configuration file (typically ntripcaster.xml or similar config in the installation directory) for 'auth' or 'authentication' settings and verify UDP-based sourcetable queries are not protectedAffected if No authentication is required for UDP sourcetable queries in the configuration
The environment is affected if NtripCaster version 2.0.39 or lower is running with UDP port 2101 accessible externally and the sourcetable responds to unauthenticated requests.
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 dataImplement authentication for UDP-based sourcetable queries and/or restrict UDP access via firewall rules to prevent unauthorized information disclosure and amplification abuse.
- Consultation4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-42982 — 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-2022-42982 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