Threats / Array Networks / CVE-2023-28461
CVE-2023-28461
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-09-19
Array Networks AG/vxAG ArrayOS vulnerability
Array Networks AG and vxAG ArrayOS lack authentication for critical functions, allowing attackers to read local files and execute code on SSL VPN gateways.
Verdict
Today item, not a backlog item.
Missing authentication on critical functions in SSL VPN appliances enables unauthenticated remote code execution and file access. Active exploitation and ransomware deployment observed in the wild.
CISA KEV Yes · 2024-11-254Ransomware use Flagged4EPSS 0.68079 (verify live)5CVSS 9.8 (CISA)3CISA SSVC Exploitation: active · Automatable: yes · Impact: total3
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
28 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2024-11-25), flagged for known ransomware use.
Probability (EPSS)
EPSS 0.68079 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) · Affected: Array Networks , AG/vxAG ArrayOS. Confirm exact fixed builds in the vendor advisory.CVSS — CISA-assigned via the ADP container (CVE.org), version 3.1; the CNA left no metrics, so CISA's own score is used ahead of NVD.
Weakness (CWE)
Mapped to CWE-306 Missing Authentication — weakness family: Authentication.CWE assignment from the public NVD record (may be stale); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 621 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I identify the SSL VPN gateway as internet-facing and accessible without authentication requirements.
Business
Perimeter security fails to prevent unauthorized access to critical VPN infrastructure.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I invoke critical functions on the appliance that lack authentication checks, bypassing intended access controls.
Business
Authentication mechanisms designed to protect sensitive operations are ineffective.
3
Lateral reach — past segmentation narrative 3
Attacker
I read sensitive local files from the system to gather credentials, configuration, or intelligence.
Business
Confidential data stored on the VPN gateway is compromised and exfiltrated.
4
Data at risk — exfiltration narrative 4
Attacker
I execute arbitrary code with the privileges of the VPN appliance process.
Business
The gateway is fully compromised and becomes a pivot point into the internal network.
5
Lights out — disruption & extortion narrative 5
Attacker
I deploy ransomware or establish persistence to encrypt data and extort the organization.
Business
Operations are disrupted, data is encrypted, and the organization faces financial and reputational damage.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05
Coverage & confidence
— what we know, and what we don’tEstablished (cited)
Coverage gaps — stated, not hidden
Disclosure & credit2
Catalogued by mitreCNA
Credited with finding itNo finder is named in the public CVE record or the scanned vendor advisory — attribution scoped to the sources checked.
Found an error? Propose a correction.
A correction is a cited counter-claim — it must cite a source,
gets reviewed by a second human, and is never auto-applied. See the
correction convention and our identity
npub1j7gt9ky7sfcrjn8jjee6693dkzvk4rahs0fk2suu7968dfns62zs3mqm3y.