CVE-2025-0980
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 · uneditedNokia SR Linux is vulnerable to an authentication vulnerability allowing unauthorized access to the JSON-RPC service. When exploited, an invalid validation allows JSON RPC access without providing valid authentication credentials.
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 confidenceNokia SR Linux contains an authentication bypass vulnerability in its JSON-RPC service where invalid validation logic permits unauthenticated access to the RPC interface. An attacker can invoke JSON-RPC methods without providing valid credentials, potentially exposing management functions.
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
- Local
- Complexity
- High
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:H/PR:H/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.
-
Confirm the product is Nokia SR LinuxRun 'show system information' or check the startup banner/logs to verify the device is running Nokia SR LinuxAffected if The device is not Nokia SR Linux
-
Identify the installed SR Linux versionRun 'show version' or check '/etc/version' file to obtain the exact software version numberAffected if The installed version falls within any affected version range (compare against vendor advisory)
-
Verify JSON-RPC service is enabledCheck the configuration for 'json-rpc' or 'rpc' service settings using 'show config json-rpc' or similar command; look for service listening on typical ports (default 443 or 8080)Affected if JSON-RPC service is enabled and running
-
Check network exposure of JSON-RPC interfaceReview firewall rules, interface bindings, and management access lists; use 'show interfaces' or check network configuration to determine if JSON-RPC port is bound to non-loopback interfacesAffected if JSON-RPC service is bound to accessible network interfaces (not localhost-only)
-
Test for unauthenticated RPC accessSend a benign JSON-RPC request (e.g., method 'get' or 'ping') to the JSON-RPC endpoint without providing authentication credentials; inspect HTTP response for success rather than authentication failureAffected if RPC methods return valid responses without authentication headers or tokens
If Nokia SR Linux with JSON-RPC enabled is exposed to network access and accepts unauthenticated RPC method calls, the environment is affected by CVE-2025-0980.
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 CVE-2025-0980 when available; restrict network access to the JSON-RPC service to trusted management networks until the vulnerability is remediated.
- 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-2025-0980 — 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-0980 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