CVE-2020-25197
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 · uneditedA code injection vulnerability exists in one of the webpages in GE Reason RT430, RT431 & RT434 GNSS clocks in firmware versions prior to version 08A06 that could allow an authenticated remote attacker to execute arbitrary code on the system.
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 confidenceA code injection vulnerability in the web interface of GE Reason RT430, RT431, and RT434 GNSS clocks allows authenticated remote attackers to inject and execute arbitrary code due to insufficient input validation in firmware versions prior to 08A06.
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< 08a06< 08a06< 08a06CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 GE Reason device modelAccess the device web interface or check the device label/serial number to confirm whether the unit is an RT430, RT431, or RT434 model.Affected if The device is a GE Reason RT430, RT431, or RT434 GNSS clock.
-
Locate the firmware version informationLog into the device web interface and navigate to the system status or firmware information page. Alternatively, check the device documentation or use the web interface 'About' or 'System Info' section to retrieve the installed firmware version.Affected if The device displays a firmware version less than 08A06.
-
Confirm the web interface is enabledVerify that the device web management interface is accessible and enabled. This is typically the default state for these devices. Check network settings or try accessing the device IP via HTTP/HTTPS.Affected if The web interface is enabled and reachable on the network.
-
Verify authentication is configuredCheck the security settings in the web interface to confirm whether authentication is enabled for web access. The vulnerability affects authenticated users, so determine if default credentials or any user accounts are configured.Affected if User authentication is enabled (the vulnerability requires authenticated access to the web interface).
If the device is a GE Reason RT430, RT431, or RT434 with firmware version below 08A06 and the web interface is enabled with authentication configured, the environment is affected by CVE-2020-25197.
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 data08a06
Upgrade the device firmware to version 08A06 or later. If immediate patching is not possible, restrict network access to the management interface and disable remote web access until the update can be applied.
- Consultation3.0 h
- Implementation4.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 $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-25197 — 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-2020-25197 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