Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 2055471 (CVE-2022-25271) - CVE-2022-25271 drupal: improper input validation found via drupal core api
Summary: CVE-2022-25271 drupal: improper input validation found via drupal core api
Keywords:
Status: CLOSED UPSTREAM
Alias: CVE-2022-25271
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 2055472 2055473 2055474
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-17 03:55 UTC by Sandipan Roy
Modified: 2022-03-02 18:49 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2022-03-02 18:49:53 UTC
Embargoed:

Attachments (Terms of Use)

Description Sandipan Roy 2022-02-17 03:55:21 UTC 
Drupal core's form API has a vulnerability where certain contributed or custom modules' forms may be vulnerable to improper input validation. This could allow an attacker to inject disallowed values or overwrite data. Affected forms are uncommon, but in certain cases an attacker could alter critical or sensitive data.

https://www.drupal.org/sa-core-2022-003
Comment 1 Sandipan Roy 2022-02-17 03:55:56 UTC 
Created drupal7 tracking bugs for this issue:

Affects: epel-all [bug 2055472]
Affects: fedora-all [bug 2055473]


Created drupal8 tracking bugs for this issue:

Affects: fedora-all [bug 2055474]
Comment 2 Product Security DevOps Team 2022-03-02 18:49:51 UTC 
This CVE Bugzilla entry is for community support informational purposes only as it does not affect a package in a commercially supported Red Hat product. Refer to the dependent bugs for status of those individual community products.
Note You need to log in before you can comment on or make changes to this bug.