CVE-2023-28968: Junos OS: SRX Series: Policies that rely on JDPI-Decoder actions may fail open
Noroxi assessment
Priority: Monitor (action score 21/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.56% (FIRST EPSS).
- 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 CISA the attack is automatable: targets can be found by mass scanning.
- According to the record, no fixed version is available yet.
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
An Improperly Controlled Sequential Memory Allocation vulnerability in the Juniper Networks Deep Packet Inspection-Decoder (JDPI-Decoder) Application Signature component of Junos OS's AppID service on SRX Series devices will stop the JDPI-Decoder from identifying dynamic application traffic, allowing an unauthenticated network-based attacker to send traffic to the target device using the JDPI-Decoder, designed to inspect dynamic application traffic and take action upon this traffic, to instead begin to not take action and to pass the traffic through. An example session can be seen by running the following command and evaluating the output. user@device# run show security flow session source-prefix <address/mask> extensive Session ID: <session ID>, Status: Normal, State: Active Policy name: <name of policy> Dynamic application: junos:UNKNOWN, <<<<< LOOK HERE Please note, the JDPI-Decoder and the AppID SigPack are both affected and both must be upgraded along with the operating system to address the matter. By default, none of this is auto-enabled for automatic updates. This issue affects: Juniper Networks any version of the JDPI-Decoder Engine prior to version 5.7.0-47 with the JDPI-Decoder enabled using any version of the AppID SigPack prior to version 1.550.2-31 (SigPack 3533) on Junos OS on SRX Series: All versions prior to 19.1R3-S10; 19.2 versions prior to 19.2R3-S7; 19.3 versions prior to 19.3R3-S8; 19.4 versions prior to 19.4R3-S11; 20.1 version 20.1R1 and later versions prior to 20.2R3-S7; 20.3 version 20.3R1 and later versions prior to 20.4R3-S6; 21.1 versions prior to 21.1R3-S5; 21.2 versions prior to 21.2R3-S4; 21.3 versions prior to 21.3R3-S3; 21.4 versions prior to 21.4R3-S3; 22.1 versions prior to 22.1R3-S1; 22.2 versions prior to 22.2R2-S1, 22.2R3; 22.3 versions prior to 22.3R1-S2, 22.3R2;
- Published
- Apr 17, 2023
- Updated
- Jun 17, 2026
- EPSS
- 0.5% · 47th percentile
- CWE
- CWE-1325
Report tools
Action score
21
Monitor
Low priority for now.
- CVSS
- 21 / 40 · 5.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.5%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · juniper
- 5.3
- NVD has not scored this yet; the score shown is the CNA’s.
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.
Running WordPress? Scan your site free with WP Lens
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 helpAffected 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 | appid service sigpack | cpe:2.3:a:juniper:appid_service_sigpack |
| juniper | jdpi-decoder engine | cpe:2.3:a:juniper:jdpi-decoder_engine |
| juniper | srx100 | cpe:2.3:h:juniper:srx100 |
| juniper | srx110 | cpe:2.3:h:juniper:srx110 |
| juniper | srx1400 | cpe:2.3:h:juniper:srx1400 |
| juniper | srx1500 | cpe:2.3:h:juniper:srx1500 |
| juniper | srx210 | cpe:2.3:h:juniper:srx210 |
| juniper | srx220 | cpe:2.3:h:juniper:srx220 |
| juniper | srx240 | cpe:2.3:h:juniper:srx240 |
| juniper | srx240h2 | cpe:2.3:h:juniper:srx240h2 |
| juniper | srx240m | cpe:2.3:h:juniper:srx240m |
| juniper | srx300 | cpe:2.3:h:juniper:srx300 |
and 19 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- juniper appid service sigpackbefore 1.550.2-31
- juniper jdpi-decoder enginebefore 5.7.0-47
- 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 junos21.3
- juniper junos21.4
- juniper junos22.1
- juniper junos22.2
- juniper junos22.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 AppID Service Sigpack
- unspecified and later · before 1.550.2-31affected
Juniper Networks JDPI-Decoder Engine
- unspecified and later · before 5.7.0-47affected
Juniper Networks Junos OS
- unspecified and later · before 19.1R3-S10affected
- 19.2 and later · before 19.2R3-S7affected
- 19.3 and later · before 19.3R3-S8affected
- 19.4 and later · before 19.4R3-S11affected
- 20.1R1 and later · before 20.1*affected
- 20.2 and later · before 20.2R3-S7affected
- 20.3R1 and later · before 20.3*affected
- 20.4 and later · before 20.4R3-S6affected
- 21.1 and later · before 21.1R3-S5affected
- 21.2 and later · before 21.2R3-S4affected
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 researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
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).
Technical details
Attack conditions
- 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.
If successful
- Confidentiality
- none
- Integrity
- low · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- Low
- Availability impact
- None
Weakness class (CWE)
CWE-1325 · Improperly Controlled Sequential Memory AllocationCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.