-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Coverity-report-output-v7-json Demo #14
base: main
Are you sure you want to change the base?
Conversation
Coverity Issue - Explicit null dereferencedCalling a method on null object "newStr". Medium Impact, CWE-476 Issue locationThis issue was discovered outside the diff for this Pull Request. You can find it at: |
InstanceType: "m3.medium.elasticsearch" | ||
DedicatedMasterType: "m3.medium.elasticsearch" | ||
DedicatedMasterCount: 3 | ||
EncryptionAtRestOptions: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Coverity Issue - Disk-level encryption is disabled
The Amazon ElasticSearch Domain does not have encryption enabled for data at rest.
Medium Impact, CWE-313
SIGMA.disk_encryption_disabled_cloudformation_elastic_search
How to fix
Enable encryption for data at rest by explicitly setting the Properties.EncryptionAtRestOptions.Enabled
value to true
.
Resources: | ||
ElasticsearchDomain: | ||
Type: AWS::Elasticsearch::Domain | ||
Properties: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Coverity Issue - Insecure TLS version
The Amazon Elasticsearch Service (Amazon ES) domain supports TLS 1.0.
Low Impact, CWE-327
SIGMA.insecure_tls_version_cloudformation_elastic_search
How to fix
Configure the ElasticSearch service domain to require TLS 1.2 or newer by explicitly setting the Properties.DomainEndpointOptions.TLSSecurityPolicy
value to Policy-Min-TLS-1-2-2019-07
.
Resources: | ||
ElasticsearchDomain: | ||
Type: AWS::Elasticsearch::Domain | ||
Properties: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Coverity Issue - Missing TLS
The Amazon Elasticsearch Service (Amazon ES) domain does not enforce HTTPS connections, exposing data in transit.
High Impact, CWE-319
SIGMA.missing_tls_cloudformation_elastic_search
How to fix
Explicitly set the Properties.DomainEndpointOptions.EnforceHTTPS
value to true
to require HTTPS for all connections.
Resources: | ||
ElasticsearchDomain: | ||
Type: AWS::Elasticsearch::Domain | ||
Properties: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Coverity Issue - Missing TLS
The Amazon Elasticsearch Service (Amazon ES) domain does not use TLS for node-to-node encryption within the VPC.
Low Impact, CWE-319
SIGMA.missing_tls_cloudformation_elastic_search_node_to_node
How to fix
Enable node-to-node encryption by explicitly setting the Properties.NodeToNodeEncryptionOptions.Enabled
value to true
.
|
||
var socket1 = tls.connect({ | ||
port: 1337, | ||
host: 'https://example1.com', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
host: 'https://example1.com', | |
host: 'https://example2.com', |
No description provided.