coreruleset / coreruleset/drupal-rule-exclusions-plugin

Config Split, exclude

Open Beginner friendly
#16 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
5
Forks
4
Avg merge
9h 57m
Merged PRs (30d)
3

Description

Hi all

We use config split, and if we put in config split relative folders (i.e. ../config) the waf block our form submit. Possible to add a special rule like bellow for config split?

# ========================================================================
#
# ========================================================================
#
# Pfad: /admin/config/development/configuration/config-split/
#
# Problem: Beim Speichern von config_split-Ordnern wird die Pfadangabe
# (z.B.../config_elitos/...) fälschlicherweise als Directory-Traversal-
# Angriff (LFI) gewertet und blockiert.
#
# Loesung: Wir entfernen das Ziel "ARGS:folder" gezielt aus der Regel
# 930110, falls der Aufruf aus dem Config-Split-Bereich kommt.
#
SecRule REQUEST_FILENAME "@contains /admin/config/development/configuration/config-split/" \
    "id:9506130,\
    phase:1,\
    pass,\
    nolog,\
    ctl:ruleRemoveTargetById=930110;ARGS:folder,\
    ver:'drupal-rule-exclusions-plugin/1.0.0'"

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Config Split admin path and rule 930110 target ARGS:folder described in the issue. Review how this plugin stores Drupal-specific exclusions, then verify that submitting a relative config folder no longer triggers the WAF rule.

Written by the indexing model from the issue text.

Assessment

Tech stack
drupal
Domain
security
Issue type
Feature
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
65/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.