NVD / CVE Program· CNA juniper

CVE-2022-22177: Junos OS and Junos OS Evolved: After receiving a specific number of crafted packets snmpd will segmentation fault (SIGSEGV) requiring a manual restart.

Noroxi assessment

Priority: Monitor (action score 30/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.95% (FIRST EPSS); higher than 61.7% of all records.
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
According to the record, no fixed version is available yet.
Severity is disputed: the assigning authority (CNA) scores it 5.3, NVD 7.5.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Update when a fix is released; follow the vendor's advisory.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

A release of illegal memory vulnerability in the snmpd daemon of Juniper Networks Junos OS, Junos OS Evolved allows an attacker to halt the snmpd daemon causing a sustained Denial of Service (DoS) to the service until it is manually restarted. This issue impacts any version of SNMP – v1,v2, v3 This issue affects: Juniper Networks Junos OS 12.3 versions prior to 12.3R12-S20; 15.1 versions prior to 15.1R7-S11; 18.3 versions prior to 18.3R3-S6; 18.4 versions prior to 18.4R2-S9, 18.4R3-S10; 19.1 versions prior to 19.1R2-S3, 19.1R3-S7; 19.2 versions prior to 19.2R1-S8, 19.2R3-S4; 19.3 versions prior to 19.3R3-S4; 19.4 versions prior to 19.4R2-S5, 19.4R3-S6; 20.1 versions prior to 20.1R3-S2; 20.2 versions prior to 20.2R3-S3; 20.3 versions prior to 20.3R3-S1; 20.4 versions prior to 20.4R3; 21.1 versions prior to 21.1R2-S2, 21.1R3; 21.2 versions prior to 21.2R1-S2, 21.2R2. Juniper Networks Junos OS Evolved 21.2 versions prior to 21.2R3-EVO; 21.3 versions prior to 21.3R2-EVO.

HighCVSS 7.5 · v3.1—No exploit No fix recorded

BDU:2023-03537

Published: Jan 18, 2022
Updated: Jun 17, 2026
EPSS: 0.9% · 61th percentile
CWE: CWE-755

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 30 / 40 · 7.5 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.9%

CNA vs NVD score

NVD: 7.5
CNA · juniper: 5.3; 2.2 point gap

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
juniper	junos	cpe:2.3:o:juniper:junos
juniper	junos os evolved	cpe:2.3:o:juniper:junos_os_evolved

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

juniper junos12.3
juniper junos15.1
juniper junos18.3
juniper junos18.4
juniper junos19.1
juniper junos19.2
juniper junos19.3
juniper junos19.4
juniper junos20.1
juniper junos20.2
juniper junos20.3
juniper junos20.4
juniper junos21.1
juniper junos21.2
juniper junos os evolved21.2
juniper junos os evolved21.3

Versions reported by the vendor

Affected version ranges reported by the assigning authority (juniper). Independent of NVD's CPE analysis and usually ahead of it.

Juniper Networks Junos OS
- 12.3 and later · before 12.3R12-S20affected
- 15.1 and later · before 15.1R7-S11affected
- 18.3 and later · before 18.3R3-S6affected
- 18.4 and later · before 18.4R2-S9, 18.4R3-S10affected
- 19.1 and later · before 19.1R2-S3, 19.1R3-S7affected
- 19.2 and later · before 19.2R1-S8, 19.2R3-S4affected
- 19.3 and later · before 19.3R3-S4affected
- 19.4 and later · before 19.4R2-S5, 19.4R3-S6affected
- 20.1 and later · before 20.1R3-S2affected
- 20.2 and later · before 20.2R3-S3affected
Juniper Networks Junos OS Evolved
- unspecified and later · before 21.2R3-EVOaffected
- 21.3 and later · before 21.3R2-EVOaffected

Same product

juniper: all records

Other highest-scoring records for the same primary product.

CVE-2023-36845Junos OS: EX and SRX Series: A PHP vulnerability in J-Web allows an unauthenticated to control an important environment variableKEV
98Now
CVE-2023-36846Junos OS: SRX Series: A vulnerability in J-Web allows an unauthenticated attacker to upload arbitrary filesKEV
79This week
CVE-2023-36844Junos OS: EX Series: A PHP vulnerability in J-Web allows an unauthenticated attacker to control important environment variablesKEV
78This week

Published before and after this one in the same product

← EarlierCVE-2022-22175Jan 18, 2022 · Junos OS: MX Series and SRX Series: The flowd daemon will crash if the SIP ALG is enabled and specific SIP messages are processed
30Monitor
← EarlierCVE-2022-22176Jan 18, 2022 · Junos OS: In a scenario with dhcp-security and option-82 configured jdhcpd crashes upon receipt of a malformed DHCP packet
26Monitor
Later →CVE-2022-22178Jan 18, 2022 · Junos OS: MX and SRX series: Flowd core observed if the SIP ALG is enabled and a specific Session Initiation Protocol (SIP) packet is received
30Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Nanyu Zhong and Yu ZhangVARAS at the Institute of Information Engineering

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).