SecOps SignalSecurity Intelligence Workspace
Collection Running30 / 46 Sources HealthyPublic Intel Only
Vulnerabilities/CVE-2016-3081Public Intelligence Dossier
Source: huawei · Limited verification•Last verified: •Collection Running
CVE-2016-3081ListedHIGH (raw)CVSS 9.3CWE-77

Apache Struts 2.3.19 to 2.3.20.2, 2.3.21 to 2.3.24.1, and 2.3.25 to 2.3.28, when Dynamic Method Invocation is enabled, allow remote attackers to execute arbitrary code via method: prefix, related to chained expressions.

Published: 26 Apr 2016•Last updated: 09 Oct 2026, 08:13 PM IST•Source identifier: secalert@redhat.com
Dossier completeness: source-provided sections 3 / 3 · rule guidance available. Missing source facts count as incomplete.
Official source
CISA KEV catalog
Listed
Added08 Oct 2026
Due11 Oct 2026
RansomwareUnknown
CVSS score
9.3HIGH (raw)
AV:N/AC:M/Au:N/C:C/I:C/A:C
Metric sourcenvd@nist.gov
EPSS probability
—
Percentile—
Weakness type
CWE-77
No further CWE recorded
Remediation
Patch status unknown
No fixed version or KB recorded

Why It Matters

Analysis dossier

Why It Matters

Apache Struts 2.3.19 to 2.3.20.2, 2.3.21 to 2.3.24.1, and 2.3.25 to 2.3.28, when Dynamic Method Invocation is enabled, allow remote attackers to execute arbitrary code via method: prefix, related to chained expressions.

SOC priority

Immediate Attention

Actively exploited

Yes

Publicly disclosed

Unknown

Risk basis: CISA KEV exploitation signal; SOC ecosystem technology relevance; HIGH severity; Known exploitation signal from CISA KEV or ransomware metadata

Affected Products & Remediation

20 source-backed products
Affected products and versions (source)
  • huawei agile controller-campus firmware · v100r002c00 · NVD CPE · Source
  • huawei anyoffice · v200r005c00; v200r006c00 · NVD CPE · Source
  • huawei logcenter · v100r001c10; v100r001c20 · NVD CPE · Source
  • huawei firehunter6000 firmware · v100r001c20 · NVD CPE · Source
  • huawei oceanstor 5300 v3 firmware · v300r001; v300r002; v300r003c00; v300r003c10 · NVD CPE · Source
  • huawei oceanstor 5500 v3 firmware · v300r001; v300r002; v300r003c00; v300r003c10 · NVD CPE · Source
  • huawei oceanstor 5600 v3 firmware · v300r001; v300r002; v300r003c00; v300r003c10 · NVD CPE · Source
  • huawei oceanstor 5800 v3 firmware · v300r001; v300r002; v300r003c00; v300r003c10 · NVD CPE · Source
  • huawei oceanstor 6800 v3 firmware · v300r001; v300r002; v300r003c00; v300r003c10 · NVD CPE · Source
  • huawei oceanstor 18500 v3 firmware · v300r001; v300r002; v300r003c00; v300r003c10 · NVD CPE · Source
  • huawei oceanstor 18500f firmware · v300r001; v300r002; v300r003c00; v300r003c10 · NVD CPE · Source
  • huawei oceanstor 18800 v3 firmware · v300r001; v300r002; v300r003c00; v300r003c10 · NVD CPE · Source
  • huawei oceanstor 18800f firmware · v300r001; v300r002 · NVD CPE · Source
  • huawei oceanstor 9000 firmware · version range not provided by source · NVD CPE · Source
  • huawei oceanstor n8500 firmware · version range not provided by source · NVD CPE · Source
  • huawei oceanstor onebox firmware · version range not provided by source · NVD CPE · Source
  • apache struts · version range not provided by source · NVD CPE · Source
  • oracle flexcube private banking · version range not provided by source · NVD CPE · Source
  • oracle micros retail xbri loss prevention · version range not provided by source · NVD CPE · Source
  • oracle siebel e-billing · version range not provided by source · NVD CPE · Source
NVD applicability prerequisites: cpe:2.3:h:huawei:agile_controller-campus:-:*:*:*:*:*:*:*, cpe:2.3:h:huawei:firehunter6000:-:*:*:*:*:*:*:*, cpe:2.3:h:huawei:oceanstor_5300_v3:-:*:*:*:*:*:*:*, cpe:2.3:h:huawei:oceanstor_5500_v3:-:*:*:*:*:*:*:*, cpe:2.3:h:huawei:oceanstor_5600_v3:-:*:*:*:*:*:*:*, cpe:2.3:h:huawei:oceanstor_5800_v3:-:*:*:*:*:*:*:*, cpe:2.3:h:huawei:oceanstor_6800_v3:-:*:*:*:*:*:*:*, cpe:2.3:h:huawei:oceanstor_18500_v3:-:*:*:*:*:*:*:*, cpe:2.3:h:huawei:oceanstor_18500f:v3:*:*:*:*:*:*:*, cpe:2.3:h:huawei:oceanstor_18800_v3:-:*:*:*:*:*:*:*. These are conditions, not proof that an environment is exposed or unaffected.
Recorded patch / KBNot provided by source

Vendor or catalog guidance (source)

  • CISA KEV: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

Known exploitation (source facts)

Only what a source states. Unknown means no source has said either way; it is not "not exploited".

CISA KEV
Listed
Exploited (source statement)
Yes
Publicly disclosed (source)
Unknown

CISA required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

Suggested hunting (rule-based inference)

SecOps Signal recommendation (rule-based inference). These steps are hunting hypotheses from the vulnerability class; they do not state or imply that exploitation occurred here or anywhere.

Matched kev-network-exposure (CVSS AV:N, CISA KEV Listed)

Exposure

  1. Identify assets with the exact CVE and confirm the affected product/version against the advisory.Telemetry: DeviceTvmSoftwareVulnerabilities · KEV listing raises urgency, but inventory is needed to establish local exposure. · Rule kev-network-exposure

Exploitation evidence

  1. Review relevant edge or application access logs for unusual requests around the advisory window.Telemetry: CommonSecurityLog · Log review is a hunting hypothesis; KEV listing alone does not show local exploitation. · Rule kev-network-exposure

Response

  1. Recheck the affected assets after the source-stated mitigation or update is applied.Telemetry: DeviceTvmSoftwareVulnerabilities · A follow-up inventory check verifies local remediation. · Rule kev-network-exposure

CISA KEV Record

Catalog entry
08 Oct 2026
Required action due
11 Oct 2026
Known ransomware use
Unknown

Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

Change History & Source Data

— No recorded material change

CNA / source
secalert@redhat.com
Record status · verification
NEW · CISA KEV confirmed
CPE
cpe:2.3:o:huawei:agile_controller-campus_firmware:v100r002c00:*:*:*:*:*:*:*, cpe:2.3:h:huawei:agile_controller-campus:-:*:*:*:*:*:*:*, cpe:2.3:a:huawei:anyoffice:v200r005c00:*:*:*:*:*:*:*, cpe:2.3:a:huawei:anyoffice:v200r006c00:*:*:*:*:*:*:*, cpe:2.3:a:huawei:logcenter:v100r001c10:*:*:*:*:*:*:*, cpe:2.3:a:huawei:logcenter:v100r001c20:*:*:*:*:*:*:*, cpe:2.3:o:huawei:firehunter6000_firmware:v100r001c20:*:*:*:*:*:*:*, cpe:2.3:h:huawei:firehunter6000:-:*:*:*:*:*:*:*, cpe:2.3:o:huawei:oceanstor_5300_v3_firmware:v300r001:*:*:*:*:*:*:*, cpe:2.3:o:huawei:oceanstor_5300_v3_firmware:v300r002:*:*:*:*:*:*:*

Evidence & Provenance

4 public sources
CISA KEV CatalogAdded 2026-10-08nvd.nist.govSource recordstruts.apache.orgSource recordexploit-db.comSource record

Linked by the query's stored exact CVE association. Review required tables and validation status before use.

Detection Hunting Query
Target: DeviceTvmSoftwareVulnerabilities•Defender XDR
Detect endpoints exposed to CVE-2016-3081
Purpose: Exposure assessment (Category: Exposure Check)Why linked: Query metadata names CVE-2016-3081
DeviceTvmSoftwareVulnerabilities| where CveId == "CVE-2016-3081"| project DeviceId, DeviceName, OSPlatform, OSVersion, SoftwareVendor, SoftwareName, SoftwareVersion, CveId, VulnerabilitySeverityLevel, RecommendedSecurityUpdate, RecommendedSecurityUpdateId| sort by VulnerabilitySeverityLevel desc
Schema Checked · Not runtime validatedSource: SecOps Signal deterministic template · Limited verificationStatic screening: Passed structure and schema checks; tenant execution is not verified.
Open KQL Library

Correlated briefings

— No published briefing references this CVE

SecOps Signal surfaces public advisory facts only. A missing value means the source has not published it, not that your environment is unaffected. No tenant inventory is connected.