Cfripper

Latest version: v1.15.6

Safety actively analyzes 629639 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 12 of 13

0.14.0

Not secure
Breaking changes
- Completely changed base `Rule` abstract class signature and adapted rule classes to match it:
- Init now only takes a `Config`
- `invoke` method now accepts an optional extra Dict
- `invoke` method returns a `Result` instead of `None`
- `add_failure` has been renamed to `add_failure_to_result`. It now takes a result instead of a reason
(that now it's inferred)
- `add_warning` has been renamed to `add_warning_to_result`. It now has the same signature than `add_failure_to_result`
Improvements
- Rule Invoke extras parameter has been added to allow changing the rule behaviour depending on state besides the cfmodel itself:
- Stack naming rules
- Stack tags
- User restrictions
- ...

0.13.0

Not secure
Fixed
- Regular expressions had an unescaped '.' before 'amazonaws.com', so it might match more hosts than expected.
Changed
- `CloudFormationAuthenticationRule` now in `MONITOR` mode and new test added
- `IAMRoleWildcardActionOnPolicyRule` combines three previous unused rules in `IAMManagedPolicyWildcardActionRule`, `IAMRoleWildcardActionOnPermissionsPolicyRule`, and `IAMRoleWildcardActionOnTrustPolicyRule`
- `IAMRoleWildcardActionOnPolicyRule` now in `DEBUG` mode
- `S3BucketPolicyWildcardActionRule` has now been changed to be an instantiation of the new generic rule `GenericWildcardPolicyRule`. It is set in `DEBUG` mode
- `S3BucketPolicyWildcardActionRule` has had updated regex filter to make it more aligned with both further rules to do with wildcards in actions, and the existing `SQSQueuePolicyWildcardActionRule`
- `SQSQueuePolicyWildcardActionRule` has now been changed to be an instantiation of the new generic rule `GenericWildcardPolicyRule`. It is set in `DEBUG` mode
- `SecurityGroupMissingEgressRule` now in `DEBUG` mode and a new test added
- `SNSTopicPolicyWildcardActionRule` has beed added. It is an instantiation of the new generic rule `GenericWildcardPolicyRule`. It is set in `DEBUG` mode
Breaking changes
- The following rules are no longer available:
- `IAMRoleWildcardActionOnPermissionsPolicyRule`
- `IAMRoleWildcardActionOnTrustPolicyRule`
- `IAMManagedPolicyWildcardActionRule`
- The following rules have been moved:
- `S3BucketPolicyWildcardActionRule`
- `SQSQueuePolicyWildcardActionRule`

0.12.2

Improvements
- Documentation updated to show the risk of rules and possible fixes where available,
as well as a large set of updates to the content. The macros for parsing the documentation
have also been updated.

0.12.1

Not secure
Fixes
- Fix for `CrossAccountCheckingRule` was adding errors when the principal was sts when it shouldn't.
Added
- `get_account_id_from_sts_arn` and `get_aws_service_from_arn` in utils.

0.12.0

Not secure
Added
- Adds CLI to package
- `KMSKeyCrossAccountTrustRule`
Changed
- `GenericWildcardPrincipalRule`, `PartialWildcardPrincipalRule`, `FullWildcardPrincipalRule` no longer check for
wildcards in KMSKey principals.
- Improved granularity of most rules

0.11.3

Not secure
Improvements
- `S3CrossAccountTrustRule` now accepts resource level exceptions
- New documentation!
Breaking changes
- `cfripper.rules.s3_bucked_policy` renamed to `cfripper.rules.s3_bucket_policy` (typo)

Page 12 of 13

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.