dbcve.org
JunosOperating system · Juniper

CVE-2024-30409

MEDIUM · 5.3 CVSS v3.1 Published 2024-04-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
An Improper Check for Unusual or Exceptional Conditions vulnerability in telemetry processing of Juniper Networks Junos OS and Junos OS Evolved allows a network-based authenticated attacker to cause the forwarding information base telemetry daemon (fibtd) to crash, leading to a limited Denial of Service.  This issue affects Juniper Networks Junos OS: * from 22.1 before 22.1R1-S2, 22.1R2. Junos OS Evolved:  * from 22.1 before 22.1R1-S2-EVO, 22.1R2-EVO.

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 confidence

This is an improper check for unusual or exceptional conditions vulnerability in the forwarding information base telemetry daemon (fibtd) telemetry processing code. An authenticated network attacker can send specially crafted telemetry data that triggers an unhandled exceptional condition, causing the fibtd process to crash and resulting in a limited denial of service.

MitigationApply the vendor-supplied patches (22.1R1-S2/22.1R1-S2-EVO or later) to fix the improper error handling in the fibtd telemetry processing. Until patches can be applied, consider restricting management access to trusted authenticated users only.

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
JunosOperating system
Affected:= 22.1
Junos Os EvolvedOperating system
Affected:= 22.1

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
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed Junos version
    Run 'show version' or 'version' command to obtain the exact Junos version installed on the device
    Affected if The installed version is 22.1 (such as 22.1R1 before S2 patch) since only =22.1 is listed as affected
  2. Verify the fibtd process is running
    Run 'show system processes extensive | match fibtd' or check process status via 'cli -c "show system processes"' to confirm the fibtd daemon is active
    Affected if The fibtd process is running and the device is on an affected version - if the process has crashed or recently restarted, this may indicate the vulnerability has been triggered
  3. Check if telemetry processing is enabled
    Run 'show configuration | match telemetry' or review the forwarding options configuration to see if FIB telemetry data export is configured
    Affected if Telemetry processing is enabled and the device is on an affected 22.1 version - the vulnerability exists specifically in the telemetry processing code path
  4. Review fibtd crash or restart logs
    Run 'show log messages' and search for fibtd-related entries using 'grep -i fibtd' or check 'show system core-dumps' for any fibtd crash files
    Affected if Recent fibtd crashes or unexpected restarts are found in logs on a 22.1 device, which may indicate exploitation of this unhandled exception vulnerability

A user is affected if the device runs Junos version 22.1 with fibtd telemetry enabled and exhibits unexplained fibtd crashes or restarts.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-supplied patches (22.1R1-S2/22.1R1-S2-EVO or later) to fix the improper error handling in the fibtd telemetry processing. Until patches can be applied, consider restricting management access to trusted authenticated users only.

Recommended fix High confidence

Junos OS: upgrade to 22.1R1-S2 or later (22.1R2-S1, 22.1R3, etc.); Junos OS Evolved: upgrade to 22.1R1-S2-EVO or later (22.1R2-S1-EVO, 22.1R3-EVO, etc.)

  1. 1. Identify the current Junos OS or Junos OS Evolved version running on the device using 'show version'
  2. 2. Confirm the device is running an affected version: Junos OS 22.1, 22.1R1, 22.1R1-S1, or 22.1R2; or Junos OS Evolved 22.1, 22.1R1-EVO, 22.1R1-S1-EVO, or 22.1R2-EVO
  3. 3. Download the fixed release from the Juniper Networks support portal: Junos OS 22.1R1-S2 or later, or Junos OS Evolved 22.1R1-S2-EVO or later
  4. 4. Upload the Junos OS upgrade package to the device using 'request system software add' command
  5. 5. Reboot the device using 'request system reboot' to apply the new software version
  6. 6. After reboot, verify the new version is installed using 'show version' and confirm the fibtd daemon is running using 'show system processes | match fibtd'
Caveat Standard Junos upgrade; review Juniper release notes for any configuration changes between versions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Junos Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-30409 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-30409 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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