# DRUPAL-CONTRIB-2022-006: Update 2022-03-01. New maintainers have volunteered for the project and created a new release which includes fixes for the 3 security issues

> A Drupal module was marked unsupported due to known security issues, which were later fixed in a new release by new maintainers.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** Yes
- **Published:** 25 Jan 2022

## What is DRUPAL-CONTRIB-2022-006?

DRUPAL-CONTRIB-2022-006 is a vulnerability in drupal/tac_lite, published on 25 Jan 2022. 

### Official description

Update 2022-03-01. New maintainers have volunteered for the project and created a new release which includes fixes for the 3 security issues that caused the module to be unsupported.

~~The security team is marking this project unsupported. There is a known security issue with the project that has not been fixed by the maintainer. If you would like to maintain this project, please read: <https://www.drupal.org/node/251466#procedure---own-project---unsupported>~~

## Which versions are affected by DRUPAL-CONTRIB-2022-006?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `drupal/tac_lite` | Packagist:https://packages.drupal.org/8 | All versions | 1.6.0 |

## How do I fix DRUPAL-CONTRIB-2022-006?

Upgrade to a fixed version.

## Is DRUPAL-CONTRIB-2022-006 being exploited?

There is no known exploitation of DRUPAL-CONTRIB-2022-006 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for DRUPAL-CONTRIB-2022-006 and fix it if it is affected.

What it is: DRUPAL-CONTRIB-2022-006 is a vulnerability in drupal/tac_lite, published on 25 Jan 2022. 
Exploitation: There is no known exploitation of DRUPAL-CONTRIB-2022-006 in the wild and no public exploit code.

Affected product: drupal/tac_lite. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/DRUPAL-CONTRIB-2022-006/ (Markdown: https://insights.sbomify.com/DRUPAL-CONTRIB-2022-006/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/DRUPAL-CONTRIB-2022-006

---
From sbomify Insights: https://insights.sbomify.com/DRUPAL-CONTRIB-2022-006/
Summaries are generated and may contain mistakes; the official description above is the record.