JVNDB-2026-000162
Vulnerability from jvndb - Published: 2026-10-29 04:57 - Updated:2026-10-29 04:57Summary
Apache Struts 2 REST Plugin: @StrutsParameter checks do not cover @JsonAnySetter
Details
The Apache Struts 2 REST plugin includes ParameterAuthorizingModule, which enforces @StrutsParameter restrictions when deserializing JSON or XML request bodies into objects, preventing unauthorized parameters from being assigned. The plugin uses Jackson for deserialization, and Jackson supports the @JsonAnySetter annotation for handling dynamically named properties.
However, ParameterAuthorizingModule does not perform these authorization checks for fields or methods annotated with @JsonAnySetter.
The issue applies only when @StrutsParameter enforcement is enabled (struts.parameters.requireAnnotations=true) and the application itself declares a @JsonAnySetter on an Action or Model class bound from a REST request body.
Satoshi Ogawa of Mitsui Bussan Secure Directions, Inc. reported this issue to IPA under Information Security Early Warning Partnership.
The developer received a report from Darren Carreras, GitHub: carrerasdarren-cell before receiving a report from Satoshi Ogawa and addressed the issue.
JPCERT/CC coordinated with the developer and published the advisory.
References
| Type | URL | |
|---|---|---|
Impacted products
| Vendor | Product | |
|---|---|---|
{
"@rdf:about": "https://jvndb.jvn.jp/en/contents/2026/JVNDB-2026-000162.html",
"dc:date": "2026-10-29T13:57+09:00",
"dcterms:issued": "2026-10-29T13:57+09:00",
"dcterms:modified": "2026-10-29T13:57+09:00",
"description": "The Apache Struts 2 REST plugin includes ParameterAuthorizingModule, which enforces @StrutsParameter restrictions when deserializing JSON or XML request bodies into objects, preventing unauthorized parameters from being assigned. The plugin uses Jackson for deserialization, and Jackson supports the @JsonAnySetter annotation for handling dynamically named properties.\r\n\r\nHowever, ParameterAuthorizingModule does not perform these authorization checks for fields or methods annotated with @JsonAnySetter.\r\n\r\nThe issue applies only when @StrutsParameter enforcement is enabled (struts.parameters.requireAnnotations=true) and the application itself declares a @JsonAnySetter on an Action or Model class bound from a REST request body.\r\n\r\nSatoshi Ogawa of Mitsui Bussan Secure Directions, Inc. reported this issue to IPA under Information Security Early Warning Partnership.\r\n\r\nThe developer received a report from Darren Carreras, GitHub: carrerasdarren-cell before receiving a report from Satoshi Ogawa and addressed the issue.\r\nJPCERT/CC coordinated with the developer and published the advisory.",
"link": "https://jvndb.jvn.jp/en/contents/2026/JVNDB-2026-000162.html",
"sec:cpe": {
"#text": "cpe:/a:apache:struts",
"@product": "Apache Struts",
"@vendor": "Apache Software Foundation",
"@version": "2.2"
},
"sec:identifier": "JVNDB-2026-000162",
"sec:references": {
"#text": "https://jvn.jp/en/jp/JVN82782759/index.html",
"@id": "JVN#82782759",
"@source": "JVN"
},
"title": "Apache Struts 2 REST Plugin: @StrutsParameter checks do not cover @JsonAnySetter"
}
Loading…
Loading…
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…
The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the
vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base
model, served locally by ML-Gateway.
They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Loading…
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.
Loading…