Unnamed: 0 int64 0 832k | id float64 2.49B 32.1B | type stringclasses 1 value | created_at stringlengths 19 19 | repo stringlengths 5 112 | repo_url stringlengths 34 141 | action stringclasses 3 values | title stringlengths 1 844 | labels stringlengths 4 721 | body stringlengths 1 261k | index stringclasses 12 values | text_combine stringlengths 96 261k | label stringclasses 2 values | text stringlengths 96 248k | binary_label int64 0 1 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
63,916 | 14,656,803,336 | IssuesEvent | 2020-12-28 14:14:02 | fu1771695yongxie/yapi | https://api.github.com/repos/fu1771695yongxie/yapi | opened | WS-2019-0332 (Medium) detected in handlebars-4.0.11.tgz | security vulnerability | ## WS-2019-0332 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>handlebars-4.0.11.tgz</b></p></summary>
<p>Handlebars provides the power necessary to let you build semantic templates effectively with no frustration</p>
<p>Library home page: <a href="https://registry.npmjs.org/handlebars/-/handlebars-4.0.11.tgz">https://registry.npmjs.org/handlebars/-/handlebars-4.0.11.tgz</a></p>
<p>Path to dependency file: yapi/package.json</p>
<p>Path to vulnerable library: yapi/node_modules/handlebars/package.json</p>
<p>
Dependency Hierarchy:
- react-scripts-1.0.10.tgz (Root Library)
- jest-20.0.4.tgz
- jest-cli-20.0.4.tgz
- istanbul-api-1.2.2.tgz
- istanbul-reports-1.1.4.tgz
- :x: **handlebars-4.0.11.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/fu1771695yongxie/yapi/commit/426884f4927afe9500db9cacc24729657b10526b">426884f4927afe9500db9cacc24729657b10526b</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Arbitrary Code Execution vulnerability found in handlebars before 4.5.3. Lookup helper fails to validate templates. Attack may submit templates that execute arbitrary JavaScript in the system.It is due to an incomplete fix for a WS-2019-0331.
<p>Publish Date: 2019-11-17
<p>URL: <a href=https://github.com/wycats/handlebars.js/commit/198887808780bbef9dba67a8af68ece091d5baa7>WS-2019-0332</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 2 Score Details (<b>5.0</b>)</summary>
<p>
Base Score Metrics not available</p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.npmjs.com/advisories/1324">https://www.npmjs.com/advisories/1324</a></p>
<p>Release Date: 2019-12-05</p>
<p>Fix Resolution: handlebars - 4.5.3</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | WS-2019-0332 (Medium) detected in handlebars-4.0.11.tgz - ## WS-2019-0332 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>handlebars-4.0.11.tgz</b></p></summary>
<p>Handlebars provides the power necessary to let you build semantic templates effectively with no frustration</p>
<p>Library home page: <a href="https://registry.npmjs.org/handlebars/-/handlebars-4.0.11.tgz">https://registry.npmjs.org/handlebars/-/handlebars-4.0.11.tgz</a></p>
<p>Path to dependency file: yapi/package.json</p>
<p>Path to vulnerable library: yapi/node_modules/handlebars/package.json</p>
<p>
Dependency Hierarchy:
- react-scripts-1.0.10.tgz (Root Library)
- jest-20.0.4.tgz
- jest-cli-20.0.4.tgz
- istanbul-api-1.2.2.tgz
- istanbul-reports-1.1.4.tgz
- :x: **handlebars-4.0.11.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/fu1771695yongxie/yapi/commit/426884f4927afe9500db9cacc24729657b10526b">426884f4927afe9500db9cacc24729657b10526b</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Arbitrary Code Execution vulnerability found in handlebars before 4.5.3. Lookup helper fails to validate templates. Attack may submit templates that execute arbitrary JavaScript in the system.It is due to an incomplete fix for a WS-2019-0331.
<p>Publish Date: 2019-11-17
<p>URL: <a href=https://github.com/wycats/handlebars.js/commit/198887808780bbef9dba67a8af68ece091d5baa7>WS-2019-0332</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 2 Score Details (<b>5.0</b>)</summary>
<p>
Base Score Metrics not available</p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.npmjs.com/advisories/1324">https://www.npmjs.com/advisories/1324</a></p>
<p>Release Date: 2019-12-05</p>
<p>Fix Resolution: handlebars - 4.5.3</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | ws medium detected in handlebars tgz ws medium severity vulnerability vulnerable library handlebars tgz handlebars provides the power necessary to let you build semantic templates effectively with no frustration library home page a href path to dependency file yapi package json path to vulnerable library yapi node modules handlebars package json dependency hierarchy react scripts tgz root library jest tgz jest cli tgz istanbul api tgz istanbul reports tgz x handlebars tgz vulnerable library found in head commit a href found in base branch master vulnerability details arbitrary code execution vulnerability found in handlebars before lookup helper fails to validate templates attack may submit templates that execute arbitrary javascript in the system it is due to an incomplete fix for a ws publish date url a href cvss score details base score metrics not available suggested fix type upgrade version origin a href release date fix resolution handlebars step up your open source security game with whitesource | 0 |
394,252 | 27,025,080,967 | IssuesEvent | 2023-02-11 13:51:31 | bp4151/cvss-rescore | https://api.github.com/repos/bp4151/cvss-rescore | closed | 2023-02-04-01: Fix file name format, update RULES.rst documentation | bug documentation | The current release filename format is incorrrect, so we have to replace the underscore with a hyphen so the release filename complies with the wheel specification. Also need to remove the "v" from the version in the filename.
Updated RULES file that better describes how rules files are built and used. | 1.0 | 2023-02-04-01: Fix file name format, update RULES.rst documentation - The current release filename format is incorrrect, so we have to replace the underscore with a hyphen so the release filename complies with the wheel specification. Also need to remove the "v" from the version in the filename.
Updated RULES file that better describes how rules files are built and used. | non_priority | fix file name format update rules rst documentation the current release filename format is incorrrect so we have to replace the underscore with a hyphen so the release filename complies with the wheel specification also need to remove the v from the version in the filename updated rules file that better describes how rules files are built and used | 0 |
118,330 | 17,580,034,802 | IssuesEvent | 2021-08-16 05:47:09 | ghc-dev/Amy-Yoder | https://api.github.com/repos/ghc-dev/Amy-Yoder | opened | CVE-2019-20444 (High) detected in netty-codec-http-4.1.39.Final.jar | security vulnerability | ## CVE-2019-20444 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>netty-codec-http-4.1.39.Final.jar</b></p></summary>
<p>Netty is an asynchronous event-driven network application framework for
rapid development of maintainable high performance protocol servers and
clients.</p>
<p>Library home page: <a href="https://netty.io/">https://netty.io/</a></p>
<p>Path to dependency file: Amy-Yoder/build.gradle</p>
<p>Path to vulnerable library: adle/caches/modules-2/files-2.1/io.netty/netty-codec-http/4.1.39.Final/732d06961162e27fa3ae5989541c4460853745d3/netty-codec-http-4.1.39.Final.jar</p>
<p>
Dependency Hierarchy:
- :x: **netty-codec-http-4.1.39.Final.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/ghc-dev/Amy-Yoder/commit/5e77d25b99e0bd3fbc967a4b95297aac8dbf6a0e">5e77d25b99e0bd3fbc967a4b95297aac8dbf6a0e</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
HttpObjectDecoder.java in Netty before 4.1.44 allows an HTTP header that lacks a colon, which might be interpreted as a separate header with an incorrect syntax, or might be interpreted as an "invalid fold."
<p>Publish Date: 2020-01-29
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-20444>CVE-2019-20444</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-20444">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-20444</a></p>
<p>Release Date: 2020-01-29</p>
<p>Fix Resolution: io.netty:netty-all:4.1.44.Final</p>
</p>
</details>
<p></p>
***
:rescue_worker_helmet: Automatic Remediation is available for this issue
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"io.netty","packageName":"netty-codec-http","packageVersion":"4.1.39.Final","packageFilePaths":["/build.gradle"],"isTransitiveDependency":false,"dependencyTree":"io.netty:netty-codec-http:4.1.39.Final","isMinimumFixVersionAvailable":true,"minimumFixVersion":"io.netty:netty-all:4.1.44.Final"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2019-20444","vulnerabilityDetails":"HttpObjectDecoder.java in Netty before 4.1.44 allows an HTTP header that lacks a colon, which might be interpreted as a separate header with an incorrect syntax, or might be interpreted as an \"invalid fold.\"","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-20444","cvss3Severity":"high","cvss3Score":"9.1","cvss3Metrics":{"A":"None","AC":"Low","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> --> | True | CVE-2019-20444 (High) detected in netty-codec-http-4.1.39.Final.jar - ## CVE-2019-20444 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>netty-codec-http-4.1.39.Final.jar</b></p></summary>
<p>Netty is an asynchronous event-driven network application framework for
rapid development of maintainable high performance protocol servers and
clients.</p>
<p>Library home page: <a href="https://netty.io/">https://netty.io/</a></p>
<p>Path to dependency file: Amy-Yoder/build.gradle</p>
<p>Path to vulnerable library: adle/caches/modules-2/files-2.1/io.netty/netty-codec-http/4.1.39.Final/732d06961162e27fa3ae5989541c4460853745d3/netty-codec-http-4.1.39.Final.jar</p>
<p>
Dependency Hierarchy:
- :x: **netty-codec-http-4.1.39.Final.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/ghc-dev/Amy-Yoder/commit/5e77d25b99e0bd3fbc967a4b95297aac8dbf6a0e">5e77d25b99e0bd3fbc967a4b95297aac8dbf6a0e</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
HttpObjectDecoder.java in Netty before 4.1.44 allows an HTTP header that lacks a colon, which might be interpreted as a separate header with an incorrect syntax, or might be interpreted as an "invalid fold."
<p>Publish Date: 2020-01-29
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-20444>CVE-2019-20444</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-20444">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-20444</a></p>
<p>Release Date: 2020-01-29</p>
<p>Fix Resolution: io.netty:netty-all:4.1.44.Final</p>
</p>
</details>
<p></p>
***
:rescue_worker_helmet: Automatic Remediation is available for this issue
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"io.netty","packageName":"netty-codec-http","packageVersion":"4.1.39.Final","packageFilePaths":["/build.gradle"],"isTransitiveDependency":false,"dependencyTree":"io.netty:netty-codec-http:4.1.39.Final","isMinimumFixVersionAvailable":true,"minimumFixVersion":"io.netty:netty-all:4.1.44.Final"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2019-20444","vulnerabilityDetails":"HttpObjectDecoder.java in Netty before 4.1.44 allows an HTTP header that lacks a colon, which might be interpreted as a separate header with an incorrect syntax, or might be interpreted as an \"invalid fold.\"","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-20444","cvss3Severity":"high","cvss3Score":"9.1","cvss3Metrics":{"A":"None","AC":"Low","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> --> | non_priority | cve high detected in netty codec http final jar cve high severity vulnerability vulnerable library netty codec http final jar netty is an asynchronous event driven network application framework for rapid development of maintainable high performance protocol servers and clients library home page a href path to dependency file amy yoder build gradle path to vulnerable library adle caches modules files io netty netty codec http final netty codec http final jar dependency hierarchy x netty codec http final jar vulnerable library found in head commit a href found in base branch master vulnerability details httpobjectdecoder java in netty before allows an http header that lacks a colon which might be interpreted as a separate header with an incorrect syntax or might be interpreted as an invalid fold publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution io netty netty all final rescue worker helmet automatic remediation is available for this issue isopenpronvulnerability true ispackagebased true isdefaultbranch true packages istransitivedependency false dependencytree io netty netty codec http final isminimumfixversionavailable true minimumfixversion io netty netty all final basebranches vulnerabilityidentifier cve vulnerabilitydetails httpobjectdecoder java in netty before allows an http header that lacks a colon which might be interpreted as a separate header with an incorrect syntax or might be interpreted as an invalid fold vulnerabilityurl | 0 |
38,047 | 10,133,256,240 | IssuesEvent | 2019-08-02 02:24:41 | tronprotocol/java-tron | https://api.github.com/repos/tronprotocol/java-tron | closed | whats wrong? | build | Please answer these questions before submitting your issue. Thanks!
1. What did you do?
If possible, provide a recipe for reproducing the error.
when i run build i see the following error like bellow
i dont know what should i do
2. What did you expect to see?
3. What did you see instead?
root@vps489802:/home/java-tron# ./gradlew build
Downloading https://services.gradle.org/distributions/gradle-4.3-all.zip
...........................................................................................
Unzipping /root/.gradle/wrapper/dists/gradle-4.3-all/2c1rgv6vofd95kl0ugolfeu5r/gradle-4.3-all.zip to /root/.gradle/wrapper/dists/gradle-4.3-all/2c1rgv6vofd95kl0ugolfeu5r
Set executable permissions for: /root/.gradle/wrapper/dists/gradle-4.3-all/2c1rgv6vofd95kl0ugolfeu5r/gradle-4.3/bin/gradle
Starting a Gradle Daemon (subsequent builds will be faster)
Download http://mvnrepository.com/com/google/protobuf/protobuf-gradle-plugin/0.8.3/protobuf-gradle-plugin-0.8.3.pom
Download http://mvnrepository.com/com/github/jengelman/gradle/plugins/shadow/2.0.2/shadow-2.0.2.pom
Download http://mvnrepository.com/org/sonarsource/scanner/gradle/sonarqube-gradle-plugin/2.6/sonarqube-gradle-plugin-2.6.pom
> Configure project :
[Fatal Error] protobuf-gradle-plugin-0.8.3.pom:1:44: Content is not allowed in prolog.
[Fatal Error] sonarqube-gradle-plugin-2.6.pom:1:44: Content is not allowed in prolog.
[Fatal Error] shadow-2.0.2.pom:1:44: Content is not allowed in prolog.
FAILURE: Build failed with an exception.
* What went wrong:
A problem occurred configuring root project 'java-tron'.
> Could not resolve all files for configuration ':classpath'.
> Could not resolve com.google.protobuf:protobuf-gradle-plugin:0.8.3.
Required by:
project :
> Could not resolve com.google.protobuf:protobuf-gradle-plugin:0.8.3.
> Could not parse POM http://mvnrepository.com/com/google/protobuf/protobuf-gradle-plugin/0.8.3/protobuf-gradle-plugin-0.8.3.pom
> Content is not allowed in prolog.
> Could not resolve com.github.jengelman.gradle.plugins:shadow:2.0.2.
Required by:
project :
> Could not resolve com.github.jengelman.gradle.plugins:shadow:2.0.2.
> Could not parse POM http://mvnrepository.com/com/github/jengelman/gradle/plugins/shadow/2.0.2/shadow-2.0.2.pom
> Content is not allowed in prolog.
> Could not resolve org.sonarsource.scanner.gradle:sonarqube-gradle-plugin:2.6.
Required by:
project :
> Could not resolve org.sonarsource.scanner.gradle:sonarqube-gradle-plugin:2.6.
> Could not parse POM http://mvnrepository.com/org/sonarsource/scanner/gradle/sonarqube-gradle-plugin/2.6/sonarqube-gradle-plugin-2.6.pom
> Content is not allowed in prolog.
* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.
* Get more help at https://help.gradle.org
BUILD FAILED in 18s
| 1.0 | whats wrong? - Please answer these questions before submitting your issue. Thanks!
1. What did you do?
If possible, provide a recipe for reproducing the error.
when i run build i see the following error like bellow
i dont know what should i do
2. What did you expect to see?
3. What did you see instead?
root@vps489802:/home/java-tron# ./gradlew build
Downloading https://services.gradle.org/distributions/gradle-4.3-all.zip
...........................................................................................
Unzipping /root/.gradle/wrapper/dists/gradle-4.3-all/2c1rgv6vofd95kl0ugolfeu5r/gradle-4.3-all.zip to /root/.gradle/wrapper/dists/gradle-4.3-all/2c1rgv6vofd95kl0ugolfeu5r
Set executable permissions for: /root/.gradle/wrapper/dists/gradle-4.3-all/2c1rgv6vofd95kl0ugolfeu5r/gradle-4.3/bin/gradle
Starting a Gradle Daemon (subsequent builds will be faster)
Download http://mvnrepository.com/com/google/protobuf/protobuf-gradle-plugin/0.8.3/protobuf-gradle-plugin-0.8.3.pom
Download http://mvnrepository.com/com/github/jengelman/gradle/plugins/shadow/2.0.2/shadow-2.0.2.pom
Download http://mvnrepository.com/org/sonarsource/scanner/gradle/sonarqube-gradle-plugin/2.6/sonarqube-gradle-plugin-2.6.pom
> Configure project :
[Fatal Error] protobuf-gradle-plugin-0.8.3.pom:1:44: Content is not allowed in prolog.
[Fatal Error] sonarqube-gradle-plugin-2.6.pom:1:44: Content is not allowed in prolog.
[Fatal Error] shadow-2.0.2.pom:1:44: Content is not allowed in prolog.
FAILURE: Build failed with an exception.
* What went wrong:
A problem occurred configuring root project 'java-tron'.
> Could not resolve all files for configuration ':classpath'.
> Could not resolve com.google.protobuf:protobuf-gradle-plugin:0.8.3.
Required by:
project :
> Could not resolve com.google.protobuf:protobuf-gradle-plugin:0.8.3.
> Could not parse POM http://mvnrepository.com/com/google/protobuf/protobuf-gradle-plugin/0.8.3/protobuf-gradle-plugin-0.8.3.pom
> Content is not allowed in prolog.
> Could not resolve com.github.jengelman.gradle.plugins:shadow:2.0.2.
Required by:
project :
> Could not resolve com.github.jengelman.gradle.plugins:shadow:2.0.2.
> Could not parse POM http://mvnrepository.com/com/github/jengelman/gradle/plugins/shadow/2.0.2/shadow-2.0.2.pom
> Content is not allowed in prolog.
> Could not resolve org.sonarsource.scanner.gradle:sonarqube-gradle-plugin:2.6.
Required by:
project :
> Could not resolve org.sonarsource.scanner.gradle:sonarqube-gradle-plugin:2.6.
> Could not parse POM http://mvnrepository.com/org/sonarsource/scanner/gradle/sonarqube-gradle-plugin/2.6/sonarqube-gradle-plugin-2.6.pom
> Content is not allowed in prolog.
* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.
* Get more help at https://help.gradle.org
BUILD FAILED in 18s
| non_priority | whats wrong please answer these questions before submitting your issue thanks what did you do if possible provide a recipe for reproducing the error when i run build i see the following error like bellow i dont know what should i do what did you expect to see what did you see instead root home java tron gradlew build downloading unzipping root gradle wrapper dists gradle all gradle all zip to root gradle wrapper dists gradle all set executable permissions for root gradle wrapper dists gradle all gradle bin gradle starting a gradle daemon subsequent builds will be faster download download download configure project protobuf gradle plugin pom content is not allowed in prolog sonarqube gradle plugin pom content is not allowed in prolog shadow pom content is not allowed in prolog failure build failed with an exception what went wrong a problem occurred configuring root project java tron could not resolve all files for configuration classpath could not resolve com google protobuf protobuf gradle plugin required by project could not resolve com google protobuf protobuf gradle plugin could not parse pom content is not allowed in prolog could not resolve com github jengelman gradle plugins shadow required by project could not resolve com github jengelman gradle plugins shadow could not parse pom content is not allowed in prolog could not resolve org sonarsource scanner gradle sonarqube gradle plugin required by project could not resolve org sonarsource scanner gradle sonarqube gradle plugin could not parse pom content is not allowed in prolog try run with stacktrace option to get the stack trace run with info or debug option to get more log output get more help at build failed in | 0 |
80,367 | 7,746,181,430 | IssuesEvent | 2018-05-29 20:48:25 | adamdecaf/cert-manage | https://api.github.com/repos/adamdecaf/cert-manage | closed | run tests and CI on windows | help wanted testing | https://github.com/adamdecaf/cert-manage/pull/23 added testing on both linux and osx, but windows support would be nice as well.
There's currently an issue for TravisCI: https://github.com/travis-ci/travis-ci/issues/2104
This would be pretty important to have for [windows support](https://github.com/adamdecaf/cert-manage/issues/8).
We could look at other options as it might not be a near-term addition from TravisCI. https://www.appveyor.com/ | 1.0 | run tests and CI on windows - https://github.com/adamdecaf/cert-manage/pull/23 added testing on both linux and osx, but windows support would be nice as well.
There's currently an issue for TravisCI: https://github.com/travis-ci/travis-ci/issues/2104
This would be pretty important to have for [windows support](https://github.com/adamdecaf/cert-manage/issues/8).
We could look at other options as it might not be a near-term addition from TravisCI. https://www.appveyor.com/ | non_priority | run tests and ci on windows added testing on both linux and osx but windows support would be nice as well there s currently an issue for travisci this would be pretty important to have for we could look at other options as it might not be a near term addition from travisci | 0 |
93,265 | 8,406,796,733 | IssuesEvent | 2018-10-11 18:58:40 | eclipse/openj9 | https://api.github.com/repos/eclipse/openj9 | closed | JTReg test fail : java/lang/invoke/VarHandles/VarHandleTestByteArrayAsChar.java | comp:jit jdk11 test failure | Fails with following exception ...
```
test VarHandleTestByteArrayAsChar.testAccess(" VarHandle [ALIGNED, LITTLE_ENDIAN, READ_WRITE] -> byte[] [ALIGNED, LITTLE_ENDIAN, READ_WRITE] read write", VarHandleBaseByteArrayTest$VarHandleSourceAccessTestCase@b6c2da1d): failure
java.lang.ArrayIndexOutOfBoundsException
at java.base/java.lang.Character.valueOf(Character.java:7937)
at org.testng.Assert.assertEquals(Assert.java:330)
at VarHandleTestByteArrayAsChar.testArrayReadWrite(VarHandleTestByteArrayAsChar.java:788)
at VarHandleTestByteArrayAsChar.lambda$accessTestCaseProvider$0(VarHandleTestByteArrayAsChar.java:139)
at VarHandleTestByteArrayAsChar$$Lambda$9.00000000C805E640.action(Unknown Source)
at VarHandleBaseTest$AccessTestCase.testAccess(VarHandleBaseTest.java:405)
at VarHandleTestByteArrayAsChar.testAccess(VarHandleTestByteArrayAsChar.java:196)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:85)
at org.testng.internal.Invoker.invokeMethod(Invoker.java:639)
at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:821)
at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1131)
at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125)
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:108)
at org.testng.TestRunner.privateRun(TestRunner.java:773)
at org.testng.TestRunner.run(TestRunner.java:623)
at org.testng.SuiteRunner.runTest(SuiteRunner.java:357)
at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:352)
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:310)
at org.testng.SuiteRunner.run(SuiteRunner.java:259)
at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
at org.testng.TestNG.runSuitesSequentially(TestNG.java:1185)
at org.testng.TestNG.runSuitesLocally(TestNG.java:1110)
at org.testng.TestNG.run(TestNG.java:1018)
at com.sun.javatest.regtest.agent.TestNGRunner.main(TestNGRunner.java:94)
at com.sun.javatest.regtest.agent.TestNGRunner.main(TestNGRunner.java:54)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at com.sun.javatest.regtest.agent.MainWrapper$MainThread.run(MainWrapper.java:115)
at java.base/java.lang.Thread.run(Thread.java:825)
```
... from what's been discussed, I suspect this may well just be a further symptom of the problem identified in https://github.com/eclipse/openj9/issues/3137 and might aid in resolving it.
Full logs : [byteArrayAsCharProblem.tar.gz](https://github.com/eclipse/openj9/files/2446923/byteArrayAsCharProblem.tar.gz)
Passes against Hotspot. | 1.0 | JTReg test fail : java/lang/invoke/VarHandles/VarHandleTestByteArrayAsChar.java - Fails with following exception ...
```
test VarHandleTestByteArrayAsChar.testAccess(" VarHandle [ALIGNED, LITTLE_ENDIAN, READ_WRITE] -> byte[] [ALIGNED, LITTLE_ENDIAN, READ_WRITE] read write", VarHandleBaseByteArrayTest$VarHandleSourceAccessTestCase@b6c2da1d): failure
java.lang.ArrayIndexOutOfBoundsException
at java.base/java.lang.Character.valueOf(Character.java:7937)
at org.testng.Assert.assertEquals(Assert.java:330)
at VarHandleTestByteArrayAsChar.testArrayReadWrite(VarHandleTestByteArrayAsChar.java:788)
at VarHandleTestByteArrayAsChar.lambda$accessTestCaseProvider$0(VarHandleTestByteArrayAsChar.java:139)
at VarHandleTestByteArrayAsChar$$Lambda$9.00000000C805E640.action(Unknown Source)
at VarHandleBaseTest$AccessTestCase.testAccess(VarHandleBaseTest.java:405)
at VarHandleTestByteArrayAsChar.testAccess(VarHandleTestByteArrayAsChar.java:196)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:85)
at org.testng.internal.Invoker.invokeMethod(Invoker.java:639)
at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:821)
at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1131)
at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125)
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:108)
at org.testng.TestRunner.privateRun(TestRunner.java:773)
at org.testng.TestRunner.run(TestRunner.java:623)
at org.testng.SuiteRunner.runTest(SuiteRunner.java:357)
at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:352)
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:310)
at org.testng.SuiteRunner.run(SuiteRunner.java:259)
at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
at org.testng.TestNG.runSuitesSequentially(TestNG.java:1185)
at org.testng.TestNG.runSuitesLocally(TestNG.java:1110)
at org.testng.TestNG.run(TestNG.java:1018)
at com.sun.javatest.regtest.agent.TestNGRunner.main(TestNGRunner.java:94)
at com.sun.javatest.regtest.agent.TestNGRunner.main(TestNGRunner.java:54)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at com.sun.javatest.regtest.agent.MainWrapper$MainThread.run(MainWrapper.java:115)
at java.base/java.lang.Thread.run(Thread.java:825)
```
... from what's been discussed, I suspect this may well just be a further symptom of the problem identified in https://github.com/eclipse/openj9/issues/3137 and might aid in resolving it.
Full logs : [byteArrayAsCharProblem.tar.gz](https://github.com/eclipse/openj9/files/2446923/byteArrayAsCharProblem.tar.gz)
Passes against Hotspot. | non_priority | jtreg test fail java lang invoke varhandles varhandletestbytearrayaschar java fails with following exception test varhandletestbytearrayaschar testaccess varhandle byte read write varhandlebasebytearraytest varhandlesourceaccesstestcase failure java lang arrayindexoutofboundsexception at java base java lang character valueof character java at org testng assert assertequals assert java at varhandletestbytearrayaschar testarrayreadwrite varhandletestbytearrayaschar java at varhandletestbytearrayaschar lambda accesstestcaseprovider varhandletestbytearrayaschar java at varhandletestbytearrayaschar lambda action unknown source at varhandlebasetest accesstestcase testaccess varhandlebasetest java at varhandletestbytearrayaschar testaccess varhandletestbytearrayaschar java at java base jdk internal reflect nativemethodaccessorimpl native method at java base jdk internal reflect nativemethodaccessorimpl invoke nativemethodaccessorimpl java at java base jdk internal reflect delegatingmethodaccessorimpl invoke delegatingmethodaccessorimpl java at java base java lang reflect method invoke method java at org testng internal methodinvocationhelper invokemethod methodinvocationhelper java at org testng internal invoker invokemethod invoker java at org testng internal invoker invoketestmethod invoker java at org testng internal invoker invoketestmethods invoker java at org testng internal testmethodworker invoketestmethods testmethodworker java at org testng internal testmethodworker run testmethodworker java at org testng testrunner privaterun testrunner java at org testng testrunner run testrunner java at org testng suiterunner runtest suiterunner java at org testng suiterunner runsequentially suiterunner java at org testng suiterunner privaterun suiterunner java at org testng suiterunner run suiterunner java at org testng suiterunnerworker runsuite suiterunnerworker java at org testng suiterunnerworker run suiterunnerworker java at org testng testng runsuitessequentially testng java at org testng testng runsuiteslocally testng java at org testng testng run testng java at com sun javatest regtest agent testngrunner main testngrunner java at com sun javatest regtest agent testngrunner main testngrunner java at java base jdk internal reflect nativemethodaccessorimpl native method at java base jdk internal reflect nativemethodaccessorimpl invoke nativemethodaccessorimpl java at java base jdk internal reflect delegatingmethodaccessorimpl invoke delegatingmethodaccessorimpl java at java base java lang reflect method invoke method java at com sun javatest regtest agent mainwrapper mainthread run mainwrapper java at java base java lang thread run thread java from what s been discussed i suspect this may well just be a further symptom of the problem identified in and might aid in resolving it full logs passes against hotspot | 0 |
161,725 | 25,386,701,745 | IssuesEvent | 2022-11-21 22:36:55 | BCDevOps/developer-experience | https://api.github.com/repos/BCDevOps/developer-experience | closed | In-person team day planning | training service-design | **Describe the issue**
Planning associated with in-person team day
**Additional context**
Schedule [document](https://docs.google.com/spreadsheets/d/1Mu2yvDmR-QHQzyZB7snIgScV3QHCBeBmmmeUdJr1_hk/edit?usp=sharing)
Previous schedule [mural board](https://app.mural.co/invitation/mural/platformservices5977/1664481434643?sender=uf0df5317d8dbea9ee48c7230&key=b9be9e37-f7af-4de8-b473-e8ac33587780)
**How does this benefit the users of our platform?**
Many of the functions of the in person team day will directly benefit users, including working on documentation as well as video content relating to OpenShift
**Definition of done**
- [x] Dates finalized
- [x] Legislature tour booking and follow up
- [x] Room bookings for sessions that need these (contact Luke)
- [x] Contact and discuss w/ everyone who is facilitator for a session or knowledge transfer
- [x] Create outlines and plan for individual sessions on the team days
- [x] Create calendar events for team day, consider which of these sessions can be attended virtually | 1.0 | In-person team day planning - **Describe the issue**
Planning associated with in-person team day
**Additional context**
Schedule [document](https://docs.google.com/spreadsheets/d/1Mu2yvDmR-QHQzyZB7snIgScV3QHCBeBmmmeUdJr1_hk/edit?usp=sharing)
Previous schedule [mural board](https://app.mural.co/invitation/mural/platformservices5977/1664481434643?sender=uf0df5317d8dbea9ee48c7230&key=b9be9e37-f7af-4de8-b473-e8ac33587780)
**How does this benefit the users of our platform?**
Many of the functions of the in person team day will directly benefit users, including working on documentation as well as video content relating to OpenShift
**Definition of done**
- [x] Dates finalized
- [x] Legislature tour booking and follow up
- [x] Room bookings for sessions that need these (contact Luke)
- [x] Contact and discuss w/ everyone who is facilitator for a session or knowledge transfer
- [x] Create outlines and plan for individual sessions on the team days
- [x] Create calendar events for team day, consider which of these sessions can be attended virtually | non_priority | in person team day planning describe the issue planning associated with in person team day additional context schedule previous schedule how does this benefit the users of our platform many of the functions of the in person team day will directly benefit users including working on documentation as well as video content relating to openshift definition of done dates finalized legislature tour booking and follow up room bookings for sessions that need these contact luke contact and discuss w everyone who is facilitator for a session or knowledge transfer create outlines and plan for individual sessions on the team days create calendar events for team day consider which of these sessions can be attended virtually | 0 |
35,096 | 7,892,538,822 | IssuesEvent | 2018-06-28 15:15:50 | TypeCobolTeam/TypeCobol | https://api.github.com/repos/TypeCobolTeam/TypeCobol | closed | Bad location of the Commented version line in presence of COBOL Options. | Bug Codegen TypeCobol User Visible | In the following generated Code the TYpeCobol version appears before de CBL option.
```cobol
*TypeCobol_Version:0.1(alpha)
CBL ARITH(EXTEND)
IDENTIFICATION DIVISION.
PROGRAM-ID. DVZXERRM.
DATA DIVISION.
WORKING-STORAGE SECTION.
PROCEDURE DIVISION.
END PROGRAM DVZXERRM.
```
See also #932.
| 1.0 | Bad location of the Commented version line in presence of COBOL Options. - In the following generated Code the TYpeCobol version appears before de CBL option.
```cobol
*TypeCobol_Version:0.1(alpha)
CBL ARITH(EXTEND)
IDENTIFICATION DIVISION.
PROGRAM-ID. DVZXERRM.
DATA DIVISION.
WORKING-STORAGE SECTION.
PROCEDURE DIVISION.
END PROGRAM DVZXERRM.
```
See also #932.
| non_priority | bad location of the commented version line in presence of cobol options in the following generated code the typecobol version appears before de cbl option cobol typecobol version alpha cbl arith extend identification division program id dvzxerrm data division working storage section procedure division end program dvzxerrm see also | 0 |
135,601 | 18,714,950,509 | IssuesEvent | 2021-11-03 02:24:32 | ChoeMinji/spring-boot | https://api.github.com/repos/ChoeMinji/spring-boot | opened | CVE-2017-18640 (High) detected in snakeyaml-1.25.jar | security vulnerability | ## CVE-2017-18640 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>snakeyaml-1.25.jar</b></p></summary>
<p>YAML 1.1 parser and emitter for Java</p>
<p>Library home page: <a href="http://www.snakeyaml.org">http://www.snakeyaml.org</a></p>
<p>Path to dependency file: spring-boot/ci/images/releasescripts/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/yaml/snakeyaml/1.25/snakeyaml-1.25.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-2.2.4.RELEASE.jar (Root Library)
- :x: **snakeyaml-1.25.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/ChoeMinji/spring-boot/commit/60faa10f9718625efdb26811e56686ca96286347">60faa10f9718625efdb26811e56686ca96286347</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The Alias feature in SnakeYAML 1.18 allows entity expansion during a load operation, a related issue to CVE-2003-1564.
<p>Publish Date: 2019-12-12
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-18640>CVE-2017-18640</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-18640">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-18640</a></p>
<p>Release Date: 2019-12-12</p>
<p>Fix Resolution: org.yaml:snakeyaml:1.26</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2017-18640 (High) detected in snakeyaml-1.25.jar - ## CVE-2017-18640 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>snakeyaml-1.25.jar</b></p></summary>
<p>YAML 1.1 parser and emitter for Java</p>
<p>Library home page: <a href="http://www.snakeyaml.org">http://www.snakeyaml.org</a></p>
<p>Path to dependency file: spring-boot/ci/images/releasescripts/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/yaml/snakeyaml/1.25/snakeyaml-1.25.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-2.2.4.RELEASE.jar (Root Library)
- :x: **snakeyaml-1.25.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/ChoeMinji/spring-boot/commit/60faa10f9718625efdb26811e56686ca96286347">60faa10f9718625efdb26811e56686ca96286347</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The Alias feature in SnakeYAML 1.18 allows entity expansion during a load operation, a related issue to CVE-2003-1564.
<p>Publish Date: 2019-12-12
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-18640>CVE-2017-18640</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-18640">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-18640</a></p>
<p>Release Date: 2019-12-12</p>
<p>Fix Resolution: org.yaml:snakeyaml:1.26</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve high detected in snakeyaml jar cve high severity vulnerability vulnerable library snakeyaml jar yaml parser and emitter for java library home page a href path to dependency file spring boot ci images releasescripts pom xml path to vulnerable library home wss scanner repository org yaml snakeyaml snakeyaml jar dependency hierarchy spring boot starter release jar root library x snakeyaml jar vulnerable library found in head commit a href found in base branch main vulnerability details the alias feature in snakeyaml allows entity expansion during a load operation a related issue to cve publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution org yaml snakeyaml step up your open source security game with whitesource | 0 |
182,657 | 30,881,541,981 | IssuesEvent | 2023-08-03 18:00:29 | department-of-veterans-affairs/vets-design-system-documentation | https://api.github.com/repos/department-of-veterans-affairs/vets-design-system-documentation | opened | Memorable date must not reveal regex to user when using pattern prop | bug platform-design-system-team | # Bug Report
- [x] I’ve searched for any related issues and avoided creating a duplicate issue.
## What happened
Error message for memorable date reveals regex when that prop is used.
## What I expected to happen
I expect us to return a plain language error to the user. If we need one from CAIA, they should have it for us or be able to quickly generate one.
## Reproducing
Steps to reproduce:
1. Enter an invalid year in the year field
2. See error that contains regex
## Urgency
How urgent is this request? Please select the appropriate option below and/or provide details
- [x] This bug is blocking work currently in progress
- [ ] This bug is affecting work currently in progress but we have a workaround
- [ ] This bug is blocking work planned within the next few sprints
- [ ] This bug is not blocking any work
- [ ] Other
### Details
This is blocking us from shipping form 21P-0847 | 1.0 | Memorable date must not reveal regex to user when using pattern prop - # Bug Report
- [x] I’ve searched for any related issues and avoided creating a duplicate issue.
## What happened
Error message for memorable date reveals regex when that prop is used.
## What I expected to happen
I expect us to return a plain language error to the user. If we need one from CAIA, they should have it for us or be able to quickly generate one.
## Reproducing
Steps to reproduce:
1. Enter an invalid year in the year field
2. See error that contains regex
## Urgency
How urgent is this request? Please select the appropriate option below and/or provide details
- [x] This bug is blocking work currently in progress
- [ ] This bug is affecting work currently in progress but we have a workaround
- [ ] This bug is blocking work planned within the next few sprints
- [ ] This bug is not blocking any work
- [ ] Other
### Details
This is blocking us from shipping form 21P-0847 | non_priority | memorable date must not reveal regex to user when using pattern prop bug report i’ve searched for any related issues and avoided creating a duplicate issue what happened error message for memorable date reveals regex when that prop is used what i expected to happen i expect us to return a plain language error to the user if we need one from caia they should have it for us or be able to quickly generate one reproducing steps to reproduce enter an invalid year in the year field see error that contains regex urgency how urgent is this request please select the appropriate option below and or provide details this bug is blocking work currently in progress this bug is affecting work currently in progress but we have a workaround this bug is blocking work planned within the next few sprints this bug is not blocking any work other details this is blocking us from shipping form | 0 |
30,548 | 24,917,452,394 | IssuesEvent | 2022-10-30 15:18:03 | cmudig/draco2 | https://api.github.com/repos/cmudig/draco2 | closed | Binder link doesn't have necessary modules | bug infrastructure | When I launch binder from the readme and then run `debug_draco.ipynb`, I get an error.
<img width="744" alt="Screen Shot 2022-10-29 at 23 47 11" src="https://user-images.githubusercontent.com/589034/198861643-a184aa5e-7245-4323-9b9d-3a074c38fd0c.png">
It looks like the dependencies weren't installed automatically. | 1.0 | Binder link doesn't have necessary modules - When I launch binder from the readme and then run `debug_draco.ipynb`, I get an error.
<img width="744" alt="Screen Shot 2022-10-29 at 23 47 11" src="https://user-images.githubusercontent.com/589034/198861643-a184aa5e-7245-4323-9b9d-3a074c38fd0c.png">
It looks like the dependencies weren't installed automatically. | non_priority | binder link doesn t have necessary modules when i launch binder from the readme and then run debug draco ipynb i get an error img width alt screen shot at src it looks like the dependencies weren t installed automatically | 0 |
250,546 | 18,893,725,249 | IssuesEvent | 2021-11-15 15:43:29 | carbynestack/common | https://api.github.com/repos/carbynestack/common | closed | Add Describable base interface for CsFailureReason | documentation enhancement must have | Preparation for the parameter resolver in cli-ng. | 1.0 | Add Describable base interface for CsFailureReason - Preparation for the parameter resolver in cli-ng. | non_priority | add describable base interface for csfailurereason preparation for the parameter resolver in cli ng | 0 |
44,425 | 12,149,835,953 | IssuesEvent | 2020-04-24 16:51:21 | department-of-veterans-affairs/va.gov-cms | https://api.github.com/repos/department-of-veterans-affairs/va.gov-cms | closed | Number of revisions not limited on all content types | Defect | **Describe the defect**
When visiting /admin/config/content/revisions-autoclean there are several content types that have a limit of 0 set which translated to unlimited revisions. All should have some limit set.
As a site admin I want to know that the number of tracked revisions does not get out of hand and create a burden for the site in terms of size of the revisions table.
Also need to disable the cron processing since none of ours are set to expire on age, only count.
Acceptance Criteria
- [ ] Determine what the limits should be for each content type that does not have a limit.
- [ ] Disable the cron method.
- [ ] Create a limit for each type and export the config.
## Labels
- [/] Issue type (red) (defaults to "Defect")
- [ ] CMS subsystem (green)
- [ ] CMS practice area (blue)
- [/] CMS objective (orange) (not needed for bug tickets)
- [ ] CMS-supported product (black)
| 1.0 | Number of revisions not limited on all content types - **Describe the defect**
When visiting /admin/config/content/revisions-autoclean there are several content types that have a limit of 0 set which translated to unlimited revisions. All should have some limit set.
As a site admin I want to know that the number of tracked revisions does not get out of hand and create a burden for the site in terms of size of the revisions table.
Also need to disable the cron processing since none of ours are set to expire on age, only count.
Acceptance Criteria
- [ ] Determine what the limits should be for each content type that does not have a limit.
- [ ] Disable the cron method.
- [ ] Create a limit for each type and export the config.
## Labels
- [/] Issue type (red) (defaults to "Defect")
- [ ] CMS subsystem (green)
- [ ] CMS practice area (blue)
- [/] CMS objective (orange) (not needed for bug tickets)
- [ ] CMS-supported product (black)
| non_priority | number of revisions not limited on all content types describe the defect when visiting admin config content revisions autoclean there are several content types that have a limit of set which translated to unlimited revisions all should have some limit set as a site admin i want to know that the number of tracked revisions does not get out of hand and create a burden for the site in terms of size of the revisions table also need to disable the cron processing since none of ours are set to expire on age only count acceptance criteria determine what the limits should be for each content type that does not have a limit disable the cron method create a limit for each type and export the config labels issue type red defaults to defect cms subsystem green cms practice area blue cms objective orange not needed for bug tickets cms supported product black | 0 |
108,662 | 13,645,293,706 | IssuesEvent | 2020-09-25 20:30:19 | trezor/trezor-suite | https://api.github.com/repos/trezor/trezor-suite | closed | Dashboard: New design | Dashboard Design | **[Zeplin](https://app.zeplin.io/project/5ee87c00f6af719a645d14c3/styleguide/components?seid=5ee87ee70d418aba36701f2c)** and **[Zeplin](https://app.zeplin.io/project/5ee87c00f6af719a645d14c3/screen/5ee8c6352150d5b8fd0344c5)**
- [x] Table
- [x] Headers
- [x] Security tiles
- [x] News | 1.0 | Dashboard: New design - **[Zeplin](https://app.zeplin.io/project/5ee87c00f6af719a645d14c3/styleguide/components?seid=5ee87ee70d418aba36701f2c)** and **[Zeplin](https://app.zeplin.io/project/5ee87c00f6af719a645d14c3/screen/5ee8c6352150d5b8fd0344c5)**
- [x] Table
- [x] Headers
- [x] Security tiles
- [x] News | non_priority | dashboard new design and table headers security tiles news | 0 |
59,296 | 14,379,583,278 | IssuesEvent | 2020-12-02 00:42:15 | gate5/react-16.0.0 | https://api.github.com/repos/gate5/react-16.0.0 | opened | CVE-2017-16099 (High) detected in no-case-2.3.1.tgz, no-case-2.3.0.tgz | security vulnerability | ## CVE-2017-16099 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>no-case-2.3.1.tgz</b>, <b>no-case-2.3.0.tgz</b></p></summary>
<p>
<details><summary><b>no-case-2.3.1.tgz</b></p></summary>
<p>Remove case from a string</p>
<p>Library home page: <a href="https://registry.npmjs.org/no-case/-/no-case-2.3.1.tgz">https://registry.npmjs.org/no-case/-/no-case-2.3.1.tgz</a></p>
<p>Path to dependency file: react-16.0.0/fixtures/fiber-debugger/node_modules/no-case/package.json</p>
<p>Path to vulnerable library: react-16.0.0/fixtures/fiber-debugger/node_modules/no-case/package.json,react-16.0.0/fixtures/attribute-behavior/node_modules/no-case/package.json,react-16.0.0/fixtures/ssr/node_modules/no-case/package.json</p>
<p>
Dependency Hierarchy:
- react-scripts-0.9.5.tgz (Root Library)
- html-webpack-plugin-2.24.0.tgz
- html-minifier-3.4.2.tgz
- param-case-2.1.1.tgz
- :x: **no-case-2.3.1.tgz** (Vulnerable Library)
</details>
<details><summary><b>no-case-2.3.0.tgz</b></p></summary>
<p>Remove case from a string</p>
<p>Library home page: <a href="https://registry.npmjs.org/no-case/-/no-case-2.3.0.tgz">https://registry.npmjs.org/no-case/-/no-case-2.3.0.tgz</a></p>
<p>Path to dependency file: react-16.0.0/fixtures/dom/node_modules/no-case/package.json</p>
<p>Path to vulnerable library: react-16.0.0/fixtures/dom/node_modules/no-case/package.json</p>
<p>
Dependency Hierarchy:
- react-scripts-1.0.11.tgz (Root Library)
- html-webpack-plugin-2.29.0.tgz
- html-minifier-3.5.3.tgz
- param-case-2.1.0.tgz
- :x: **no-case-2.3.0.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/gate5/react-16.0.0/commit/2a806761a8d27ad65d559febfdab96cc7efdbee5">2a806761a8d27ad65d559febfdab96cc7efdbee5</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The no-case module is vulnerable to regular expression denial of service. When malicious untrusted user input is passed into no-case it can block the event loop causing a denial of service condition.
<p>Publish Date: 2018-06-07
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-16099>CVE-2017-16099</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.npmjs.com/advisories/529/versions">https://www.npmjs.com/advisories/529/versions</a></p>
<p>Release Date: 2018-06-07</p>
<p>Fix Resolution: 2.3.2</p>
</p>
</details>
<p></p>
| True | CVE-2017-16099 (High) detected in no-case-2.3.1.tgz, no-case-2.3.0.tgz - ## CVE-2017-16099 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>no-case-2.3.1.tgz</b>, <b>no-case-2.3.0.tgz</b></p></summary>
<p>
<details><summary><b>no-case-2.3.1.tgz</b></p></summary>
<p>Remove case from a string</p>
<p>Library home page: <a href="https://registry.npmjs.org/no-case/-/no-case-2.3.1.tgz">https://registry.npmjs.org/no-case/-/no-case-2.3.1.tgz</a></p>
<p>Path to dependency file: react-16.0.0/fixtures/fiber-debugger/node_modules/no-case/package.json</p>
<p>Path to vulnerable library: react-16.0.0/fixtures/fiber-debugger/node_modules/no-case/package.json,react-16.0.0/fixtures/attribute-behavior/node_modules/no-case/package.json,react-16.0.0/fixtures/ssr/node_modules/no-case/package.json</p>
<p>
Dependency Hierarchy:
- react-scripts-0.9.5.tgz (Root Library)
- html-webpack-plugin-2.24.0.tgz
- html-minifier-3.4.2.tgz
- param-case-2.1.1.tgz
- :x: **no-case-2.3.1.tgz** (Vulnerable Library)
</details>
<details><summary><b>no-case-2.3.0.tgz</b></p></summary>
<p>Remove case from a string</p>
<p>Library home page: <a href="https://registry.npmjs.org/no-case/-/no-case-2.3.0.tgz">https://registry.npmjs.org/no-case/-/no-case-2.3.0.tgz</a></p>
<p>Path to dependency file: react-16.0.0/fixtures/dom/node_modules/no-case/package.json</p>
<p>Path to vulnerable library: react-16.0.0/fixtures/dom/node_modules/no-case/package.json</p>
<p>
Dependency Hierarchy:
- react-scripts-1.0.11.tgz (Root Library)
- html-webpack-plugin-2.29.0.tgz
- html-minifier-3.5.3.tgz
- param-case-2.1.0.tgz
- :x: **no-case-2.3.0.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/gate5/react-16.0.0/commit/2a806761a8d27ad65d559febfdab96cc7efdbee5">2a806761a8d27ad65d559febfdab96cc7efdbee5</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The no-case module is vulnerable to regular expression denial of service. When malicious untrusted user input is passed into no-case it can block the event loop causing a denial of service condition.
<p>Publish Date: 2018-06-07
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-16099>CVE-2017-16099</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.npmjs.com/advisories/529/versions">https://www.npmjs.com/advisories/529/versions</a></p>
<p>Release Date: 2018-06-07</p>
<p>Fix Resolution: 2.3.2</p>
</p>
</details>
<p></p>
| non_priority | cve high detected in no case tgz no case tgz cve high severity vulnerability vulnerable libraries no case tgz no case tgz no case tgz remove case from a string library home page a href path to dependency file react fixtures fiber debugger node modules no case package json path to vulnerable library react fixtures fiber debugger node modules no case package json react fixtures attribute behavior node modules no case package json react fixtures ssr node modules no case package json dependency hierarchy react scripts tgz root library html webpack plugin tgz html minifier tgz param case tgz x no case tgz vulnerable library no case tgz remove case from a string library home page a href path to dependency file react fixtures dom node modules no case package json path to vulnerable library react fixtures dom node modules no case package json dependency hierarchy react scripts tgz root library html webpack plugin tgz html minifier tgz param case tgz x no case tgz vulnerable library found in head commit a href vulnerability details the no case module is vulnerable to regular expression denial of service when malicious untrusted user input is passed into no case it can block the event loop causing a denial of service condition publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution | 0 |
33,426 | 12,216,550,095 | IssuesEvent | 2020-05-01 15:22:27 | bsbtd/Teste | https://api.github.com/repos/bsbtd/Teste | opened | CVE-2012-6708 (Medium) detected in multiple libraries | security vulnerability | ## CVE-2012-6708 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>jquery-1.7.2.min.js</b>, <b>jquery-1.4.4.min.js</b>, <b>jquery-1.7.1.min.js</b>, <b>jquery-1.8.1.min.js</b></p></summary>
<p>
<details><summary><b>jquery-1.7.2.min.js</b></p></summary>
<p>JavaScript library for DOM operations</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/jquery/1.7.2/jquery.min.js">https://cdnjs.cloudflare.com/ajax/libs/jquery/1.7.2/jquery.min.js</a></p>
<p>Path to dependency file: /tmp/ws-scm/Teste/aws-mobile-appsync-chat-starter-angular/node_modules/jmespath/index.html</p>
<p>Path to vulnerable library: /Teste/aws-mobile-appsync-chat-starter-angular/node_modules/jmespath/index.html</p>
<p>
Dependency Hierarchy:
- :x: **jquery-1.7.2.min.js** (Vulnerable Library)
</details>
<details><summary><b>jquery-1.4.4.min.js</b></p></summary>
<p>JavaScript library for DOM operations</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/jquery/1.4.4/jquery.min.js">https://cdnjs.cloudflare.com/ajax/libs/jquery/1.4.4/jquery.min.js</a></p>
<p>Path to dependency file: /tmp/ws-scm/Teste/aws-mobile-appsync-chat-starter-angular/node_modules/selenium-webdriver/lib/test/data/draggableLists.html</p>
<p>Path to vulnerable library: /Teste/aws-mobile-appsync-chat-starter-angular/node_modules/selenium-webdriver/lib/test/data/js/jquery-1.4.4.min.js</p>
<p>
Dependency Hierarchy:
- :x: **jquery-1.4.4.min.js** (Vulnerable Library)
</details>
<details><summary><b>jquery-1.7.1.min.js</b></p></summary>
<p>JavaScript library for DOM operations</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/jquery/1.7.1/jquery.min.js">https://cdnjs.cloudflare.com/ajax/libs/jquery/1.7.1/jquery.min.js</a></p>
<p>Path to dependency file: /tmp/ws-scm/Teste/pro-table/node_modules/webpack-dev-server/node_modules/sockjs/examples/multiplex/index.html</p>
<p>Path to vulnerable library: /Teste/pro-table/node_modules/webpack-dev-server/node_modules/sockjs/examples/multiplex/index.html,/Teste/aws-mobile-appsync-chat-starter-angular/node_modules/sockjs/examples/echo/index.html,/Teste/pro-table/node_modules/webpack-dev-server/node_modules/sockjs/examples/hapi/html/index.html,/Teste/pro-table/node_modules/webpack-dev-server/node_modules/sockjs/examples/echo/index.html,/Teste/pro-table/node_modules/webpack-dev-server/node_modules/sockjs/examples/express-3.x/index.html,/Teste/aws-mobile-appsync-chat-starter-angular/node_modules/sockjs/examples/multiplex/index.html,/Teste/aws-mobile-appsync-chat-starter-angular/node_modules/sockjs/examples/hapi/html/index.html,/Teste/aws-mobile-appsync-chat-starter-angular/node_modules/sockjs/examples/express-3.x/index.html,/Teste/pro-table/node_modules/webpack-dev-server/node_modules/sockjs/examples/express/index.html</p>
<p>
Dependency Hierarchy:
- :x: **jquery-1.7.1.min.js** (Vulnerable Library)
</details>
<details><summary><b>jquery-1.8.1.min.js</b></p></summary>
<p>JavaScript library for DOM operations</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/jquery/1.8.1/jquery.min.js">https://cdnjs.cloudflare.com/ajax/libs/jquery/1.8.1/jquery.min.js</a></p>
<p>Path to dependency file: /tmp/ws-scm/Teste/pro-table/node_modules/redeyed/examples/browser/index.html</p>
<p>Path to vulnerable library: /Teste/pro-table/node_modules/redeyed/examples/browser/index.html</p>
<p>
Dependency Hierarchy:
- :x: **jquery-1.8.1.min.js** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/bsbtd/Teste/commit/50a539d66e7a2f790cf8a8d8d1471993698c9adc">50a539d66e7a2f790cf8a8d8d1471993698c9adc</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
jQuery before 1.9.0 is vulnerable to Cross-site Scripting (XSS) attacks. The jQuery(strInput) function does not differentiate selectors from HTML in a reliable fashion. In vulnerable versions, jQuery determined whether the input was HTML by looking for the '<' character anywhere in the string, giving attackers more flexibility when attempting to construct a malicious payload. In fixed versions, jQuery only deems the input to be HTML if it explicitly starts with the '<' character, limiting exploitability only to attackers who can control the beginning of a string, which is far less common.
<p>Publish Date: 2018-01-18
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2012-6708>CVE-2012-6708</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2012-6708">https://nvd.nist.gov/vuln/detail/CVE-2012-6708</a></p>
<p>Release Date: 2018-01-18</p>
<p>Fix Resolution: jQuery - v1.9.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2012-6708 (Medium) detected in multiple libraries - ## CVE-2012-6708 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>jquery-1.7.2.min.js</b>, <b>jquery-1.4.4.min.js</b>, <b>jquery-1.7.1.min.js</b>, <b>jquery-1.8.1.min.js</b></p></summary>
<p>
<details><summary><b>jquery-1.7.2.min.js</b></p></summary>
<p>JavaScript library for DOM operations</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/jquery/1.7.2/jquery.min.js">https://cdnjs.cloudflare.com/ajax/libs/jquery/1.7.2/jquery.min.js</a></p>
<p>Path to dependency file: /tmp/ws-scm/Teste/aws-mobile-appsync-chat-starter-angular/node_modules/jmespath/index.html</p>
<p>Path to vulnerable library: /Teste/aws-mobile-appsync-chat-starter-angular/node_modules/jmespath/index.html</p>
<p>
Dependency Hierarchy:
- :x: **jquery-1.7.2.min.js** (Vulnerable Library)
</details>
<details><summary><b>jquery-1.4.4.min.js</b></p></summary>
<p>JavaScript library for DOM operations</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/jquery/1.4.4/jquery.min.js">https://cdnjs.cloudflare.com/ajax/libs/jquery/1.4.4/jquery.min.js</a></p>
<p>Path to dependency file: /tmp/ws-scm/Teste/aws-mobile-appsync-chat-starter-angular/node_modules/selenium-webdriver/lib/test/data/draggableLists.html</p>
<p>Path to vulnerable library: /Teste/aws-mobile-appsync-chat-starter-angular/node_modules/selenium-webdriver/lib/test/data/js/jquery-1.4.4.min.js</p>
<p>
Dependency Hierarchy:
- :x: **jquery-1.4.4.min.js** (Vulnerable Library)
</details>
<details><summary><b>jquery-1.7.1.min.js</b></p></summary>
<p>JavaScript library for DOM operations</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/jquery/1.7.1/jquery.min.js">https://cdnjs.cloudflare.com/ajax/libs/jquery/1.7.1/jquery.min.js</a></p>
<p>Path to dependency file: /tmp/ws-scm/Teste/pro-table/node_modules/webpack-dev-server/node_modules/sockjs/examples/multiplex/index.html</p>
<p>Path to vulnerable library: /Teste/pro-table/node_modules/webpack-dev-server/node_modules/sockjs/examples/multiplex/index.html,/Teste/aws-mobile-appsync-chat-starter-angular/node_modules/sockjs/examples/echo/index.html,/Teste/pro-table/node_modules/webpack-dev-server/node_modules/sockjs/examples/hapi/html/index.html,/Teste/pro-table/node_modules/webpack-dev-server/node_modules/sockjs/examples/echo/index.html,/Teste/pro-table/node_modules/webpack-dev-server/node_modules/sockjs/examples/express-3.x/index.html,/Teste/aws-mobile-appsync-chat-starter-angular/node_modules/sockjs/examples/multiplex/index.html,/Teste/aws-mobile-appsync-chat-starter-angular/node_modules/sockjs/examples/hapi/html/index.html,/Teste/aws-mobile-appsync-chat-starter-angular/node_modules/sockjs/examples/express-3.x/index.html,/Teste/pro-table/node_modules/webpack-dev-server/node_modules/sockjs/examples/express/index.html</p>
<p>
Dependency Hierarchy:
- :x: **jquery-1.7.1.min.js** (Vulnerable Library)
</details>
<details><summary><b>jquery-1.8.1.min.js</b></p></summary>
<p>JavaScript library for DOM operations</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/jquery/1.8.1/jquery.min.js">https://cdnjs.cloudflare.com/ajax/libs/jquery/1.8.1/jquery.min.js</a></p>
<p>Path to dependency file: /tmp/ws-scm/Teste/pro-table/node_modules/redeyed/examples/browser/index.html</p>
<p>Path to vulnerable library: /Teste/pro-table/node_modules/redeyed/examples/browser/index.html</p>
<p>
Dependency Hierarchy:
- :x: **jquery-1.8.1.min.js** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/bsbtd/Teste/commit/50a539d66e7a2f790cf8a8d8d1471993698c9adc">50a539d66e7a2f790cf8a8d8d1471993698c9adc</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
jQuery before 1.9.0 is vulnerable to Cross-site Scripting (XSS) attacks. The jQuery(strInput) function does not differentiate selectors from HTML in a reliable fashion. In vulnerable versions, jQuery determined whether the input was HTML by looking for the '<' character anywhere in the string, giving attackers more flexibility when attempting to construct a malicious payload. In fixed versions, jQuery only deems the input to be HTML if it explicitly starts with the '<' character, limiting exploitability only to attackers who can control the beginning of a string, which is far less common.
<p>Publish Date: 2018-01-18
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2012-6708>CVE-2012-6708</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2012-6708">https://nvd.nist.gov/vuln/detail/CVE-2012-6708</a></p>
<p>Release Date: 2018-01-18</p>
<p>Fix Resolution: jQuery - v1.9.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve medium detected in multiple libraries cve medium severity vulnerability vulnerable libraries jquery min js jquery min js jquery min js jquery min js jquery min js javascript library for dom operations library home page a href path to dependency file tmp ws scm teste aws mobile appsync chat starter angular node modules jmespath index html path to vulnerable library teste aws mobile appsync chat starter angular node modules jmespath index html dependency hierarchy x jquery min js vulnerable library jquery min js javascript library for dom operations library home page a href path to dependency file tmp ws scm teste aws mobile appsync chat starter angular node modules selenium webdriver lib test data draggablelists html path to vulnerable library teste aws mobile appsync chat starter angular node modules selenium webdriver lib test data js jquery min js dependency hierarchy x jquery min js vulnerable library jquery min js javascript library for dom operations library home page a href path to dependency file tmp ws scm teste pro table node modules webpack dev server node modules sockjs examples multiplex index html path to vulnerable library teste pro table node modules webpack dev server node modules sockjs examples multiplex index html teste aws mobile appsync chat starter angular node modules sockjs examples echo index html teste pro table node modules webpack dev server node modules sockjs examples hapi html index html teste pro table node modules webpack dev server node modules sockjs examples echo index html teste pro table node modules webpack dev server node modules sockjs examples express x index html teste aws mobile appsync chat starter angular node modules sockjs examples multiplex index html teste aws mobile appsync chat starter angular node modules sockjs examples hapi html index html teste aws mobile appsync chat starter angular node modules sockjs examples express x index html teste pro table node modules webpack dev server node modules sockjs examples express index html dependency hierarchy x jquery min js vulnerable library jquery min js javascript library for dom operations library home page a href path to dependency file tmp ws scm teste pro table node modules redeyed examples browser index html path to vulnerable library teste pro table node modules redeyed examples browser index html dependency hierarchy x jquery min js vulnerable library found in head commit a href vulnerability details jquery before is vulnerable to cross site scripting xss attacks the jquery strinput function does not differentiate selectors from html in a reliable fashion in vulnerable versions jquery determined whether the input was html by looking for the character anywhere in the string giving attackers more flexibility when attempting to construct a malicious payload in fixed versions jquery only deems the input to be html if it explicitly starts with the character limiting exploitability only to attackers who can control the beginning of a string which is far less common publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope changed impact metrics confidentiality impact low integrity impact low availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution jquery step up your open source security game with whitesource | 0 |
147,925 | 23,294,108,494 | IssuesEvent | 2022-08-06 09:28:13 | zuri-training/WF-PriceCompare-24 | https://api.github.com/repos/zuri-training/WF-PriceCompare-24 | closed | design | Designers | created the wireframes along with olasbee, created and worked on the gadgets frames, pictures and labels to fashion- menswear page & fashion- females wear page, added pictures and labels to the landing page
| 1.0 | design - created the wireframes along with olasbee, created and worked on the gadgets frames, pictures and labels to fashion- menswear page & fashion- females wear page, added pictures and labels to the landing page
| non_priority | design created the wireframes along with olasbee created and worked on the gadgets frames pictures and labels to fashion menswear page fashion females wear page added pictures and labels to the landing page | 0 |
158,243 | 20,018,482,751 | IssuesEvent | 2022-02-01 14:23:11 | TIBCOSoftware/genxdm | https://api.github.com/repos/TIBCOSoftware/genxdm | closed | CVE-2022-23437 (High) detected in xercesImpl-2.12.1.jar | security vulnerability | ## CVE-2022-23437 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>xercesImpl-2.12.1.jar</b></p></summary>
<p>Xerces2 is the next generation of high performance, fully compliant XML parsers in the Apache Xerces family. This new version of Xerces introduces the Xerces Native Interface (XNI), a complete framework for building parser components and configurations that is extremely modular and easy to program.
The Apache Xerces2 parser is the reference implementation of XNI but other parser components, configurations, and parsers can be written using the Xerces Native Interface. For complete design and implementation documents, refer to the XNI Manual.
Xerces2 is a fully conforming XML Schema 1.0 processor. A partial experimental implementation of the XML Schema 1.1 Structures and Datatypes Working Drafts (December 2009) and an experimental implementation of the XML Schema Definition Language (XSD): Component Designators (SCD) Candidate Recommendation (January 2010) are provided for evaluation. For more information, refer to the XML Schema page.
Xerces2 also provides a complete implementation of the Document Object Model Level 3 Core and Load/Save W3C Recommendations and provides a complete implementation of the XML Inclusions (XInclude) W3C Recommendation. It also provides support for OASIS XML Catalogs v1.1.
Xerces2 is able to parse documents written according to the XML 1.1 Recommendation, except that it does not yet provide an option to enable normalization checking as described in section 2.13 of this specification. It also handles namespaces according to the XML Namespaces 1.1 Recommendation, and will correctly serialize XML 1.1 documents if the DOM level 3 load/save APIs are in use.</p>
<p>Library home page: <a href="https://xerces.apache.org/xerces2-j/">https://xerces.apache.org/xerces2-j/</a></p>
<p>Path to dependency file: /project/performance/pom.xml</p>
<p>Path to vulnerable library: /.m2/repository/xerces/xercesImpl/2.12.1/xercesImpl-2.12.1.jar</p>
<p>
Dependency Hierarchy:
- :x: **xercesImpl-2.12.1.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
There's a vulnerability within the Apache Xerces Java (XercesJ) XML parser when handling specially crafted XML document payloads. This causes, the XercesJ XML parser to wait in an infinite loop, which may sometimes consume system resources for prolonged duration. This vulnerability is present within XercesJ version 2.12.1 and the previous versions.
<p>Publish Date: 2022-01-24
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-23437>CVE-2022-23437</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-h65f-jvqw-m9fj">https://github.com/advisories/GHSA-h65f-jvqw-m9fj</a></p>
<p>Release Date: 2022-01-24</p>
<p>Fix Resolution: xerces:xercesImpl:2.12.2</p>
</p>
</details>
<p></p>
***
:rescue_worker_helmet: Automatic Remediation is available for this issue
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"xerces","packageName":"xercesImpl","packageVersion":"2.12.1","packageFilePaths":["/project/performance/pom.xml"],"isTransitiveDependency":false,"dependencyTree":"xerces:xercesImpl:2.12.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"xerces:xercesImpl:2.12.2","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2022-23437","vulnerabilityDetails":"There\u0027s a vulnerability within the Apache Xerces Java (XercesJ) XML parser when handling specially crafted XML document payloads. This causes, the XercesJ XML parser to wait in an infinite loop, which may sometimes consume system resources for prolonged duration. This vulnerability is present within XercesJ version 2.12.1 and the previous versions.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-23437","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}}</REMEDIATE> --> | True | CVE-2022-23437 (High) detected in xercesImpl-2.12.1.jar - ## CVE-2022-23437 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>xercesImpl-2.12.1.jar</b></p></summary>
<p>Xerces2 is the next generation of high performance, fully compliant XML parsers in the Apache Xerces family. This new version of Xerces introduces the Xerces Native Interface (XNI), a complete framework for building parser components and configurations that is extremely modular and easy to program.
The Apache Xerces2 parser is the reference implementation of XNI but other parser components, configurations, and parsers can be written using the Xerces Native Interface. For complete design and implementation documents, refer to the XNI Manual.
Xerces2 is a fully conforming XML Schema 1.0 processor. A partial experimental implementation of the XML Schema 1.1 Structures and Datatypes Working Drafts (December 2009) and an experimental implementation of the XML Schema Definition Language (XSD): Component Designators (SCD) Candidate Recommendation (January 2010) are provided for evaluation. For more information, refer to the XML Schema page.
Xerces2 also provides a complete implementation of the Document Object Model Level 3 Core and Load/Save W3C Recommendations and provides a complete implementation of the XML Inclusions (XInclude) W3C Recommendation. It also provides support for OASIS XML Catalogs v1.1.
Xerces2 is able to parse documents written according to the XML 1.1 Recommendation, except that it does not yet provide an option to enable normalization checking as described in section 2.13 of this specification. It also handles namespaces according to the XML Namespaces 1.1 Recommendation, and will correctly serialize XML 1.1 documents if the DOM level 3 load/save APIs are in use.</p>
<p>Library home page: <a href="https://xerces.apache.org/xerces2-j/">https://xerces.apache.org/xerces2-j/</a></p>
<p>Path to dependency file: /project/performance/pom.xml</p>
<p>Path to vulnerable library: /.m2/repository/xerces/xercesImpl/2.12.1/xercesImpl-2.12.1.jar</p>
<p>
Dependency Hierarchy:
- :x: **xercesImpl-2.12.1.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
There's a vulnerability within the Apache Xerces Java (XercesJ) XML parser when handling specially crafted XML document payloads. This causes, the XercesJ XML parser to wait in an infinite loop, which may sometimes consume system resources for prolonged duration. This vulnerability is present within XercesJ version 2.12.1 and the previous versions.
<p>Publish Date: 2022-01-24
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-23437>CVE-2022-23437</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-h65f-jvqw-m9fj">https://github.com/advisories/GHSA-h65f-jvqw-m9fj</a></p>
<p>Release Date: 2022-01-24</p>
<p>Fix Resolution: xerces:xercesImpl:2.12.2</p>
</p>
</details>
<p></p>
***
:rescue_worker_helmet: Automatic Remediation is available for this issue
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"xerces","packageName":"xercesImpl","packageVersion":"2.12.1","packageFilePaths":["/project/performance/pom.xml"],"isTransitiveDependency":false,"dependencyTree":"xerces:xercesImpl:2.12.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"xerces:xercesImpl:2.12.2","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2022-23437","vulnerabilityDetails":"There\u0027s a vulnerability within the Apache Xerces Java (XercesJ) XML parser when handling specially crafted XML document payloads. This causes, the XercesJ XML parser to wait in an infinite loop, which may sometimes consume system resources for prolonged duration. This vulnerability is present within XercesJ version 2.12.1 and the previous versions.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-23437","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}}</REMEDIATE> --> | non_priority | cve high detected in xercesimpl jar cve high severity vulnerability vulnerable library xercesimpl jar is the next generation of high performance fully compliant xml parsers in the apache xerces family this new version of xerces introduces the xerces native interface xni a complete framework for building parser components and configurations that is extremely modular and easy to program the apache parser is the reference implementation of xni but other parser components configurations and parsers can be written using the xerces native interface for complete design and implementation documents refer to the xni manual is a fully conforming xml schema processor a partial experimental implementation of the xml schema structures and datatypes working drafts december and an experimental implementation of the xml schema definition language xsd component designators scd candidate recommendation january are provided for evaluation for more information refer to the xml schema page also provides a complete implementation of the document object model level core and load save recommendations and provides a complete implementation of the xml inclusions xinclude recommendation it also provides support for oasis xml catalogs is able to parse documents written according to the xml recommendation except that it does not yet provide an option to enable normalization checking as described in section of this specification it also handles namespaces according to the xml namespaces recommendation and will correctly serialize xml documents if the dom level load save apis are in use library home page a href path to dependency file project performance pom xml path to vulnerable library repository xerces xercesimpl xercesimpl jar dependency hierarchy x xercesimpl jar vulnerable library found in base branch master vulnerability details there s a vulnerability within the apache xerces java xercesj xml parser when handling specially crafted xml document payloads this causes the xercesj xml parser to wait in an infinite loop which may sometimes consume system resources for prolonged duration this vulnerability is present within xercesj version and the previous versions publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution xerces xercesimpl rescue worker helmet automatic remediation is available for this issue isopenpronvulnerability true ispackagebased true isdefaultbranch true packages istransitivedependency false dependencytree xerces xercesimpl isminimumfixversionavailable true minimumfixversion xerces xercesimpl isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails there a vulnerability within the apache xerces java xercesj xml parser when handling specially crafted xml document payloads this causes the xercesj xml parser to wait in an infinite loop which may sometimes consume system resources for prolonged duration this vulnerability is present within xercesj version and the previous versions vulnerabilityurl | 0 |
39,284 | 8,621,748,501 | IssuesEvent | 2018-11-20 18:13:46 | autoforce/APIcasso | https://api.github.com/repos/autoforce/APIcasso | closed | Fix "dangerous_send" issue in app/controllers/apicasso/crud_controller.rb | codeclimate enhancement security | User controlled method execution
https://codeclimate.com/github/autoforce/APIcasso/app/controllers/apicasso/crud_controller.rb#issue_5be5c81ae7e0a2000100003a | 1.0 | Fix "dangerous_send" issue in app/controllers/apicasso/crud_controller.rb - User controlled method execution
https://codeclimate.com/github/autoforce/APIcasso/app/controllers/apicasso/crud_controller.rb#issue_5be5c81ae7e0a2000100003a | non_priority | fix dangerous send issue in app controllers apicasso crud controller rb user controlled method execution | 0 |
110,324 | 9,441,926,120 | IssuesEvent | 2019-04-15 04:16:45 | humera987/FXLabs-Test-Automation | https://api.github.com/repos/humera987/FXLabs-Test-Automation | opened | Vulnerability [ABAC_Level2] : POST:/api/v1/orgs/{orgId}/users/{userId}/reset-password | ApiTest2 ApiTest2 | Project : ApiTest2
Template : ApiV1OrgsOrgidUsersUseridResetPasswordPostUseraCreateOrgorgplanbusinessUsercDisallowAbact2
Run Id : <html><a href=https://18.144.40.113/#/app/projects/8a80808f6a06f0be016a1f28449d67e3/jobs/8a80808f6a06f0be016a1f2b09126f7b/runs/8a80808f6a06f0be016a1f335e847f69>8a80808f6a06f0be016a1f335e847f69</a></html>
Job : job
Env : Default
Category : ABAC_Level2
Tags : [FX Top 10 - API Vulnerability, Data_Access_Control]
Severity : Major
Region : FX_HYD
Result : fail
Status Code : 401
Headers : {WWW-Authenticate=[Basic realm="Realm", Basic realm="Realm"], X-Content-Type-Options=[nosniff], X-XSS-Protection=[1; mode=block], Cache-Control=[no-cache, no-store, max-age=0, must-revalidate], Pragma=[no-cache], Expires=[0], X-Frame-Options=[DENY], Content-Length=[0], Date=[Mon, 15 Apr 2019 04:16:41 GMT]}
Endpoint : http://13.56.210.25/api/v1/api/v1/orgs//users//reset-password
Request :
{
"confirmPassword" : "bL9WpP1H",
"createdBy" : "",
"createdDate" : "",
"email" : "jimmie.stark@hotmail.com",
"id" : "",
"inactive" : false,
"modifiedBy" : "",
"modifiedDate" : "",
"name" : "bL9WpP1H",
"orgId" : "bL9WpP1H",
"orgRole" : "ENTERPRISE_ADMIN",
"password" : "fadUH3HDOKT$",
"username" : "selena.schuppe",
"version" : ""
}
Response :
Logs :
com.fxlabs.fxt.bot.assertions.AssertionLogger@5b3857d3
--- FX Bot --- | 2.0 | Vulnerability [ABAC_Level2] : POST:/api/v1/orgs/{orgId}/users/{userId}/reset-password - Project : ApiTest2
Template : ApiV1OrgsOrgidUsersUseridResetPasswordPostUseraCreateOrgorgplanbusinessUsercDisallowAbact2
Run Id : <html><a href=https://18.144.40.113/#/app/projects/8a80808f6a06f0be016a1f28449d67e3/jobs/8a80808f6a06f0be016a1f2b09126f7b/runs/8a80808f6a06f0be016a1f335e847f69>8a80808f6a06f0be016a1f335e847f69</a></html>
Job : job
Env : Default
Category : ABAC_Level2
Tags : [FX Top 10 - API Vulnerability, Data_Access_Control]
Severity : Major
Region : FX_HYD
Result : fail
Status Code : 401
Headers : {WWW-Authenticate=[Basic realm="Realm", Basic realm="Realm"], X-Content-Type-Options=[nosniff], X-XSS-Protection=[1; mode=block], Cache-Control=[no-cache, no-store, max-age=0, must-revalidate], Pragma=[no-cache], Expires=[0], X-Frame-Options=[DENY], Content-Length=[0], Date=[Mon, 15 Apr 2019 04:16:41 GMT]}
Endpoint : http://13.56.210.25/api/v1/api/v1/orgs//users//reset-password
Request :
{
"confirmPassword" : "bL9WpP1H",
"createdBy" : "",
"createdDate" : "",
"email" : "jimmie.stark@hotmail.com",
"id" : "",
"inactive" : false,
"modifiedBy" : "",
"modifiedDate" : "",
"name" : "bL9WpP1H",
"orgId" : "bL9WpP1H",
"orgRole" : "ENTERPRISE_ADMIN",
"password" : "fadUH3HDOKT$",
"username" : "selena.schuppe",
"version" : ""
}
Response :
Logs :
com.fxlabs.fxt.bot.assertions.AssertionLogger@5b3857d3
--- FX Bot --- | non_priority | vulnerability post api orgs orgid users userid reset password project template run id a href job job env default category abac tags severity major region fx hyd result fail status code headers www authenticate x content type options x xss protection cache control pragma expires x frame options content length date endpoint request confirmpassword createdby createddate email jimmie stark hotmail com id inactive false modifiedby modifieddate name orgid orgrole enterprise admin password username selena schuppe version response logs com fxlabs fxt bot assertions assertionlogger fx bot | 0 |
29,510 | 13,127,892,483 | IssuesEvent | 2020-08-06 11:15:14 | terraform-providers/terraform-provider-azurerm | https://api.github.com/repos/terraform-providers/terraform-provider-azurerm | closed | Bug/Feature to improve deployment reliability with issue resulting in "Error occurred reading http.Response#Body - Error = 'context deadline exceeded'" | question service/virtual-machine | <!---
Please note the following potential times when an issue might be in Terraform core:
* [Configuration Language](https://www.terraform.io/docs/configuration/index.html) or resource ordering issues
* [State](https://www.terraform.io/docs/state/index.html) and [State Backend](https://www.terraform.io/docs/backends/index.html) issues
* [Provisioner](https://www.terraform.io/docs/provisioners/index.html) issues
* [Registry](https://registry.terraform.io/) issues
* Spans resources across multiple providers
If you are running into one of these scenarios, we recommend opening an issue in the [Terraform core repository](https://github.com/hashicorp/terraform/) instead.
--->
<!--- Please keep this note for the community --->
### Community Note
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment
<!--- Thank you for keeping this note for the community --->
### Terraform (and AzureRM Provider) Version
The issue has been observed on version 2.14
### Affected Resource(s)
All resources should be affected with this issue, but it can easily be reproduced with a simply Linux VM deployment
### Terraform Configuration Files
resource "azurerm_resource_group" "example" {
location = "westus2"
name = "testing_only"
}
resource "azurerm_virtual_network" "example" {
name = "example-network"
address_space = ["10.0.0.0/16"]
location = azurerm_resource_group.example.location
resource_group_name = azurerm_resource_group.example.name
}
resource "azurerm_subnet" "example" {
name = "internal"
resource_group_name = azurerm_resource_group.example.name
virtual_network_name = azurerm_virtual_network.example.name
address_prefix = "10.0.2.0/24"
}
resource "azurerm_network_interface" "example" {
name = "example-nic"
location = azurerm_resource_group.example.location
resource_group_name = azurerm_resource_group.example.name
ip_configuration {
name = "internal"
subnet_id = azurerm_subnet.example.id
private_ip_address_allocation = "Dynamic"
}
}
resource "azurerm_linux_virtual_machine" "cac" {
name = "cac-vm"
location = azurerm_resource_group.example.location
resource_group_name = azurerm_resource_group.example.name
size = "Standard_DS2_v2"
admin_username = "admin234"
admin_password = "StRoNgPaSsWoRd11#"
computer_name = "vm-cac"
disable_password_authentication = false
network_interface_ids = [azurerm_network_interface.example.id]
source_image_reference {
publisher = "Canonical"
offer = "UbuntuServer"
sku = "18.04-LTS"
version = "latest"
}
os_disk {
name = "ac-vm-osdisk"
caching = "ReadWrite"
storage_account_type = "Standard_LRS"
disk_size_gb = 50
}
}
### Debug Output
https://gist.github.com/amonnphillipatquest/b5abe97af44957e42730bf18b6b1bdd4
results in the following in the console:
Error: Error retrieving Linux Virtual Machine "cac-vm" (Resource Group "testing_only"): compute.VirtualMachinesClient#Get: Failure responding to request: StatusCode=200 -- Original Error: Error occurred reading http.Response#Body - Error = 'context deadline exceeded'
### Panic Output
None.
### Expected Behavior
We have all seen numerous errors where a resource seems to take a long time to deploy. When you take a look at the resource group in the UI you can see the resource, and it looks like it is in a usable state. In the case of a VM I can SSH to the machine etc, so the resource in question has indeed been deployed. Terraform however shows the message 'still creating' in the log. More often than not the deployment eventually times out.
You can even turn on logging (TF_LOG=TRACE) and observe the successful response from the Azure REST API, further pointing to something being wrong in the Terraform AzureRM plugin.
I hacked together some additional logging within the plugin to see where within that function the code stalled. Within the function resourceLinuxVirtualMachineCreate several calls are made to the Azure REST API, one of the calls of course is to create the resource. This almost always succeeds. The next call to the Azure REST API however sometimes does not.
The expected behavior is for the VM to have been deployed successfully, and the plugin should detect that this is so. Within the function resourceLinuxVirtualMachineCreate the call client.CreateOrUpdate, returns successfully. The call to wait for the response via a future future.WaitForCompletionRef handles the response properly. The next call to get the resource JSON from the Azure REST API should detect cases where the API is taking too long, and retry the request.
### Actual Behavior
The VM has been deployed successfully via the call in the plugin function called resourceLinuxVirtualMachineCreate. The call to wait for the response is ok (via the line
if err := future.WaitForCompletionRef(ctx, client.Client); err != nil { ...
The very next line of code however to get the resource JSON object via the call:
read, err := client.Get(ctx, resourceGroup, name, "")
This call sometimes does not return in a timely manner and so the deployment eventually times out (wasting hours of development time for us per day BTW). There is nothing we can do here to make the Azure REST APIs more robust (thanks MS!), but we can have a short timeout for the second call mentioned, as the resource is already created, and there is not much reason why the call in question should respond within a few seconds. We should also make this call retry several times after each time out period. This should make deployments a little more robust.
Ideally this change should be implemented in a way that all resources have this retry mechanism.
### Steps to Reproduce
1. `terraform apply`
### Important Factoids
None that I am aware of
### References
* #0000
| 1.0 | Bug/Feature to improve deployment reliability with issue resulting in "Error occurred reading http.Response#Body - Error = 'context deadline exceeded'" - <!---
Please note the following potential times when an issue might be in Terraform core:
* [Configuration Language](https://www.terraform.io/docs/configuration/index.html) or resource ordering issues
* [State](https://www.terraform.io/docs/state/index.html) and [State Backend](https://www.terraform.io/docs/backends/index.html) issues
* [Provisioner](https://www.terraform.io/docs/provisioners/index.html) issues
* [Registry](https://registry.terraform.io/) issues
* Spans resources across multiple providers
If you are running into one of these scenarios, we recommend opening an issue in the [Terraform core repository](https://github.com/hashicorp/terraform/) instead.
--->
<!--- Please keep this note for the community --->
### Community Note
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment
<!--- Thank you for keeping this note for the community --->
### Terraform (and AzureRM Provider) Version
The issue has been observed on version 2.14
### Affected Resource(s)
All resources should be affected with this issue, but it can easily be reproduced with a simply Linux VM deployment
### Terraform Configuration Files
resource "azurerm_resource_group" "example" {
location = "westus2"
name = "testing_only"
}
resource "azurerm_virtual_network" "example" {
name = "example-network"
address_space = ["10.0.0.0/16"]
location = azurerm_resource_group.example.location
resource_group_name = azurerm_resource_group.example.name
}
resource "azurerm_subnet" "example" {
name = "internal"
resource_group_name = azurerm_resource_group.example.name
virtual_network_name = azurerm_virtual_network.example.name
address_prefix = "10.0.2.0/24"
}
resource "azurerm_network_interface" "example" {
name = "example-nic"
location = azurerm_resource_group.example.location
resource_group_name = azurerm_resource_group.example.name
ip_configuration {
name = "internal"
subnet_id = azurerm_subnet.example.id
private_ip_address_allocation = "Dynamic"
}
}
resource "azurerm_linux_virtual_machine" "cac" {
name = "cac-vm"
location = azurerm_resource_group.example.location
resource_group_name = azurerm_resource_group.example.name
size = "Standard_DS2_v2"
admin_username = "admin234"
admin_password = "StRoNgPaSsWoRd11#"
computer_name = "vm-cac"
disable_password_authentication = false
network_interface_ids = [azurerm_network_interface.example.id]
source_image_reference {
publisher = "Canonical"
offer = "UbuntuServer"
sku = "18.04-LTS"
version = "latest"
}
os_disk {
name = "ac-vm-osdisk"
caching = "ReadWrite"
storage_account_type = "Standard_LRS"
disk_size_gb = 50
}
}
### Debug Output
https://gist.github.com/amonnphillipatquest/b5abe97af44957e42730bf18b6b1bdd4
results in the following in the console:
Error: Error retrieving Linux Virtual Machine "cac-vm" (Resource Group "testing_only"): compute.VirtualMachinesClient#Get: Failure responding to request: StatusCode=200 -- Original Error: Error occurred reading http.Response#Body - Error = 'context deadline exceeded'
### Panic Output
None.
### Expected Behavior
We have all seen numerous errors where a resource seems to take a long time to deploy. When you take a look at the resource group in the UI you can see the resource, and it looks like it is in a usable state. In the case of a VM I can SSH to the machine etc, so the resource in question has indeed been deployed. Terraform however shows the message 'still creating' in the log. More often than not the deployment eventually times out.
You can even turn on logging (TF_LOG=TRACE) and observe the successful response from the Azure REST API, further pointing to something being wrong in the Terraform AzureRM plugin.
I hacked together some additional logging within the plugin to see where within that function the code stalled. Within the function resourceLinuxVirtualMachineCreate several calls are made to the Azure REST API, one of the calls of course is to create the resource. This almost always succeeds. The next call to the Azure REST API however sometimes does not.
The expected behavior is for the VM to have been deployed successfully, and the plugin should detect that this is so. Within the function resourceLinuxVirtualMachineCreate the call client.CreateOrUpdate, returns successfully. The call to wait for the response via a future future.WaitForCompletionRef handles the response properly. The next call to get the resource JSON from the Azure REST API should detect cases where the API is taking too long, and retry the request.
### Actual Behavior
The VM has been deployed successfully via the call in the plugin function called resourceLinuxVirtualMachineCreate. The call to wait for the response is ok (via the line
if err := future.WaitForCompletionRef(ctx, client.Client); err != nil { ...
The very next line of code however to get the resource JSON object via the call:
read, err := client.Get(ctx, resourceGroup, name, "")
This call sometimes does not return in a timely manner and so the deployment eventually times out (wasting hours of development time for us per day BTW). There is nothing we can do here to make the Azure REST APIs more robust (thanks MS!), but we can have a short timeout for the second call mentioned, as the resource is already created, and there is not much reason why the call in question should respond within a few seconds. We should also make this call retry several times after each time out period. This should make deployments a little more robust.
Ideally this change should be implemented in a way that all resources have this retry mechanism.
### Steps to Reproduce
1. `terraform apply`
### Important Factoids
None that I am aware of
### References
* #0000
| non_priority | bug feature to improve deployment reliability with issue resulting in error occurred reading http response body error context deadline exceeded please note the following potential times when an issue might be in terraform core or resource ordering issues and issues issues issues spans resources across multiple providers if you are running into one of these scenarios we recommend opening an issue in the instead community note please vote on this issue by adding a 👍 to the original issue to help the community and maintainers prioritize this request please do not leave or me too comments they generate extra noise for issue followers and do not help prioritize the request if you are interested in working on this issue or have submitted a pull request please leave a comment terraform and azurerm provider version the issue has been observed on version affected resource s all resources should be affected with this issue but it can easily be reproduced with a simply linux vm deployment terraform configuration files resource azurerm resource group example location name testing only resource azurerm virtual network example name example network address space location azurerm resource group example location resource group name azurerm resource group example name resource azurerm subnet example name internal resource group name azurerm resource group example name virtual network name azurerm virtual network example name address prefix resource azurerm network interface example name example nic location azurerm resource group example location resource group name azurerm resource group example name ip configuration name internal subnet id azurerm subnet example id private ip address allocation dynamic resource azurerm linux virtual machine cac name cac vm location azurerm resource group example location resource group name azurerm resource group example name size standard admin username admin password computer name vm cac disable password authentication false network interface ids source image reference publisher canonical offer ubuntuserver sku lts version latest os disk name ac vm osdisk caching readwrite storage account type standard lrs disk size gb debug output results in the following in the console error error retrieving linux virtual machine cac vm resource group testing only compute virtualmachinesclient get failure responding to request statuscode original error error occurred reading http response body error context deadline exceeded panic output none expected behavior we have all seen numerous errors where a resource seems to take a long time to deploy when you take a look at the resource group in the ui you can see the resource and it looks like it is in a usable state in the case of a vm i can ssh to the machine etc so the resource in question has indeed been deployed terraform however shows the message still creating in the log more often than not the deployment eventually times out you can even turn on logging tf log trace and observe the successful response from the azure rest api further pointing to something being wrong in the terraform azurerm plugin i hacked together some additional logging within the plugin to see where within that function the code stalled within the function resourcelinuxvirtualmachinecreate several calls are made to the azure rest api one of the calls of course is to create the resource this almost always succeeds the next call to the azure rest api however sometimes does not the expected behavior is for the vm to have been deployed successfully and the plugin should detect that this is so within the function resourcelinuxvirtualmachinecreate the call client createorupdate returns successfully the call to wait for the response via a future future waitforcompletionref handles the response properly the next call to get the resource json from the azure rest api should detect cases where the api is taking too long and retry the request actual behavior the vm has been deployed successfully via the call in the plugin function called resourcelinuxvirtualmachinecreate the call to wait for the response is ok via the line if err future waitforcompletionref ctx client client err nil the very next line of code however to get the resource json object via the call read err client get ctx resourcegroup name this call sometimes does not return in a timely manner and so the deployment eventually times out wasting hours of development time for us per day btw there is nothing we can do here to make the azure rest apis more robust thanks ms but we can have a short timeout for the second call mentioned as the resource is already created and there is not much reason why the call in question should respond within a few seconds we should also make this call retry several times after each time out period this should make deployments a little more robust ideally this change should be implemented in a way that all resources have this retry mechanism steps to reproduce terraform apply important factoids none that i am aware of references | 0 |
81,484 | 23,474,212,148 | IssuesEvent | 2022-08-17 03:10:06 | quinchs/EdgeDB.Net | https://api.github.com/repos/quinchs/EdgeDB.Net | closed | Autogenerated node resolution | Query builder | ## Summary
Since the query builder can generate extra nodes for given context, these nodes need to always track their reference. Take a look at the given query:
```cs
var query = QueryBuilder.For(people, person => QueryBuilder.Insert(person, true));
```
This query will generate an insert statement with an autogenerated select statement selecting out the default shape of `Person`. Heres a simple representation of the generated nodes:
```
FOR
{
SELECT { INSERT }
}
```
With the way autogenerated nodes behave, the user defined node (INSERT) will be globalized into a with statement and the autogenerated node (SELECT) will be the main body of the query. With the above example, the FOR node will only iterate over the autogenerated node (SELECT) and the insert statement will not be called with the FOR nodes iteration values. There are 2 ways to solve this:
#### Solution 1: Autogenerated nodes wrap their parents
Any autogenerated nodes will no longer control globalization of their parent, they will only be able to add on top of their parent like so:
```
AUTOGENERATED (USER_DEFINED)
```
given our example above, the select/insert query would look something like this:
```
FOR x IN {...}
UNION (SELECT (INSERT Person {...}) { name, email})
```
Testing this approach, this seems like a valid take at the problem as this query compiles and runs fine. There may be other example of node combinations that may not work due to contextual attachment of types.
#### Solution 2: Autogenerated nodes wrap their target nodes parent tree
Autogenerated nodes would work up the parent tree of their parent node to wrap whatever is wrapping their parent node. With our example above, the query may look somthing like so:
```
WITH
x := (FOR y IN {...} UNION (INSERT Person {...}))
SELECT x { name, email}
```
The autogenerated node (SELECT) will select out the parent of the insert (FOR in this case) with the autogenerated shape. With this approach there can be unexpected results as the parent node tree can contain any type of node; for example, how would a query like this work?:
```cs
QueryBuilder.Select(QueryBuilder.Insert(new Person {...}, true));
```
The insert node has a `true` parameter for autogenerating the shape, so lets express the nodes here:
```
SELECT
{
SELECT { INSERT }
}
```
Following our defined rule above, our query would look like this:
```
WITH
x := (SELECT (INSERT Person {...}) { name, email })
SELECT x { name, email }
```
A check can be issued for this duplication of nodes and we can remove duplicate query nodes compared by their context. With this approach, each autogenerated node is put into it's own scope to prevent pollution of type conflicts.
| 1.0 | Autogenerated node resolution - ## Summary
Since the query builder can generate extra nodes for given context, these nodes need to always track their reference. Take a look at the given query:
```cs
var query = QueryBuilder.For(people, person => QueryBuilder.Insert(person, true));
```
This query will generate an insert statement with an autogenerated select statement selecting out the default shape of `Person`. Heres a simple representation of the generated nodes:
```
FOR
{
SELECT { INSERT }
}
```
With the way autogenerated nodes behave, the user defined node (INSERT) will be globalized into a with statement and the autogenerated node (SELECT) will be the main body of the query. With the above example, the FOR node will only iterate over the autogenerated node (SELECT) and the insert statement will not be called with the FOR nodes iteration values. There are 2 ways to solve this:
#### Solution 1: Autogenerated nodes wrap their parents
Any autogenerated nodes will no longer control globalization of their parent, they will only be able to add on top of their parent like so:
```
AUTOGENERATED (USER_DEFINED)
```
given our example above, the select/insert query would look something like this:
```
FOR x IN {...}
UNION (SELECT (INSERT Person {...}) { name, email})
```
Testing this approach, this seems like a valid take at the problem as this query compiles and runs fine. There may be other example of node combinations that may not work due to contextual attachment of types.
#### Solution 2: Autogenerated nodes wrap their target nodes parent tree
Autogenerated nodes would work up the parent tree of their parent node to wrap whatever is wrapping their parent node. With our example above, the query may look somthing like so:
```
WITH
x := (FOR y IN {...} UNION (INSERT Person {...}))
SELECT x { name, email}
```
The autogenerated node (SELECT) will select out the parent of the insert (FOR in this case) with the autogenerated shape. With this approach there can be unexpected results as the parent node tree can contain any type of node; for example, how would a query like this work?:
```cs
QueryBuilder.Select(QueryBuilder.Insert(new Person {...}, true));
```
The insert node has a `true` parameter for autogenerating the shape, so lets express the nodes here:
```
SELECT
{
SELECT { INSERT }
}
```
Following our defined rule above, our query would look like this:
```
WITH
x := (SELECT (INSERT Person {...}) { name, email })
SELECT x { name, email }
```
A check can be issued for this duplication of nodes and we can remove duplicate query nodes compared by their context. With this approach, each autogenerated node is put into it's own scope to prevent pollution of type conflicts.
| non_priority | autogenerated node resolution summary since the query builder can generate extra nodes for given context these nodes need to always track their reference take a look at the given query cs var query querybuilder for people person querybuilder insert person true this query will generate an insert statement with an autogenerated select statement selecting out the default shape of person heres a simple representation of the generated nodes for select insert with the way autogenerated nodes behave the user defined node insert will be globalized into a with statement and the autogenerated node select will be the main body of the query with the above example the for node will only iterate over the autogenerated node select and the insert statement will not be called with the for nodes iteration values there are ways to solve this solution autogenerated nodes wrap their parents any autogenerated nodes will no longer control globalization of their parent they will only be able to add on top of their parent like so autogenerated user defined given our example above the select insert query would look something like this for x in union select insert person name email testing this approach this seems like a valid take at the problem as this query compiles and runs fine there may be other example of node combinations that may not work due to contextual attachment of types solution autogenerated nodes wrap their target nodes parent tree autogenerated nodes would work up the parent tree of their parent node to wrap whatever is wrapping their parent node with our example above the query may look somthing like so with x for y in union insert person select x name email the autogenerated node select will select out the parent of the insert for in this case with the autogenerated shape with this approach there can be unexpected results as the parent node tree can contain any type of node for example how would a query like this work cs querybuilder select querybuilder insert new person true the insert node has a true parameter for autogenerating the shape so lets express the nodes here select select insert following our defined rule above our query would look like this with x select insert person name email select x name email a check can be issued for this duplication of nodes and we can remove duplicate query nodes compared by their context with this approach each autogenerated node is put into it s own scope to prevent pollution of type conflicts | 0 |
22,049 | 7,112,351,934 | IssuesEvent | 2018-01-17 16:46:19 | elastic/elasticsearch | https://api.github.com/repos/elastic/elasticsearch | closed | Build is buggy for java 9. | :Core build | Try compiling with java 9:
First you will hit this. This can be fixed by using `assertEquals`, which also simplifies the test.
```
/home/rmuir/workspace/elasticsearch/core/src/test/java/org/elasticsearch/threadpool/ScalingThreadPoolTests.java:180: error: method invoked with incorrect number of arguments; expected 2, found 0
assertThat(stats(threadPool, threadPoolName).getThreads(), equalTo(128));
^
/home/rmuir/workspace/elasticsearch/core/src/test/java/org/elasticsearch/threadpool/ScalingThreadPoolTests.java:196: error: method invoked with incorrect number of arguments; expected 2, found 0
assertThat(stats(threadPool, threadPoolName).getCompleted(), equalTo(128L));
^
```
Next problem is that I am unsure `-source/-target` settings are being passed at all. Because I see class files referencing java 9 StringConcatFactory.
Next problem is that forbidden-apis screams, presumably because its being run in the wrong JVM (not the JAVA_HOME that is set, but the java 8 one running gradle itself). It sees StringConcatFactory and fails the build:
```
Caused by: org.gradle.internal.UncheckedException: de.thetaphi.forbiddenapis.ForbiddenApiException: Check for forbidden API calls failed: java.lang.ClassNotFoundException: java.lang.invoke.StringConcatFactory
at org.gradle.internal.UncheckedException.throwAsUncheckedException(UncheckedException.java:45)
at org.gradle.internal.reflect.JavaMethod.invoke(JavaMethod.java:78)
at org.gradle.api.internal.project.taskfactory.AnnotationProcessingTaskFactory$StandardTaskAction.doExecute(AnnotationProcessingTaskFactory.java:227)
at org.gradle.api.internal.project.taskfactory.AnnotationProcessingTaskFactory$StandardTaskAction.execute(AnnotationProcessingTaskFactory.java:220)
at org.gradle.api.internal.project.taskfactory.AnnotationProcessingTaskFactory$StandardTaskAction.execute(AnnotationProcessingTaskFactory.java:209)
at org.gradle.api.internal.AbstractTask$TaskActionWrapper.execute(AbstractTask.java:585)
at org.gradle.api.internal.AbstractTask$TaskActionWrapper.execute(AbstractTask.java:568)
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeAction(ExecuteActionsTaskExecuter.java:80)
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:61)
... 68 more
Caused by: de.thetaphi.forbiddenapis.ForbiddenApiException: Check for forbidden API calls failed: java.lang.ClassNotFoundException: java.lang.invoke.StringConcatFactory
at de.thetaphi.forbiddenapis.Checker.run(Checker.java:550)
at de.thetaphi.forbiddenapis.gradle.CheckForbiddenApis.checkForbidden(CheckForbiddenApis.java:551)
at org.gradle.internal.reflect.JavaMethod.invoke(JavaMethod.java:75)
... 75 more
Caused by: java.lang.ClassNotFoundException: java.lang.invoke.StringConcatFactory
at de.thetaphi.forbiddenapis.Checker.getClassFromClassLoader(Checker.java:264)
at de.thetaphi.forbiddenapis.Checker.lookupRelatedClass(Checker.java:277)
at de.thetaphi.forbiddenapis.ClassScanner$2.checkMethodAccess(ClassScanner.java:349)
at de.thetaphi.forbiddenapis.ClassScanner$2.checkHandle(ClassScanner.java:411)
at de.thetaphi.forbiddenapis.ClassScanner$2.visitInvokeDynamicInsn(ClassScanner.java:497)
at de.thetaphi.forbiddenapis.asm.ClassReader.a(Unknown Source)
at de.thetaphi.forbiddenapis.asm.ClassReader.b(Unknown Source)
at de.thetaphi.forbiddenapis.asm.ClassReader.accept(Unknown Source)
at de.thetaphi.forbiddenapis.asm.ClassReader.accept(Unknown Source)
at de.thetaphi.forbiddenapis.Checker.checkClass(Checker.java:528)
at de.thetaphi.forbiddenapis.Checker.run(Checker.java:545)
... 77 more
BUILD FAILED
```
| 1.0 | Build is buggy for java 9. - Try compiling with java 9:
First you will hit this. This can be fixed by using `assertEquals`, which also simplifies the test.
```
/home/rmuir/workspace/elasticsearch/core/src/test/java/org/elasticsearch/threadpool/ScalingThreadPoolTests.java:180: error: method invoked with incorrect number of arguments; expected 2, found 0
assertThat(stats(threadPool, threadPoolName).getThreads(), equalTo(128));
^
/home/rmuir/workspace/elasticsearch/core/src/test/java/org/elasticsearch/threadpool/ScalingThreadPoolTests.java:196: error: method invoked with incorrect number of arguments; expected 2, found 0
assertThat(stats(threadPool, threadPoolName).getCompleted(), equalTo(128L));
^
```
Next problem is that I am unsure `-source/-target` settings are being passed at all. Because I see class files referencing java 9 StringConcatFactory.
Next problem is that forbidden-apis screams, presumably because its being run in the wrong JVM (not the JAVA_HOME that is set, but the java 8 one running gradle itself). It sees StringConcatFactory and fails the build:
```
Caused by: org.gradle.internal.UncheckedException: de.thetaphi.forbiddenapis.ForbiddenApiException: Check for forbidden API calls failed: java.lang.ClassNotFoundException: java.lang.invoke.StringConcatFactory
at org.gradle.internal.UncheckedException.throwAsUncheckedException(UncheckedException.java:45)
at org.gradle.internal.reflect.JavaMethod.invoke(JavaMethod.java:78)
at org.gradle.api.internal.project.taskfactory.AnnotationProcessingTaskFactory$StandardTaskAction.doExecute(AnnotationProcessingTaskFactory.java:227)
at org.gradle.api.internal.project.taskfactory.AnnotationProcessingTaskFactory$StandardTaskAction.execute(AnnotationProcessingTaskFactory.java:220)
at org.gradle.api.internal.project.taskfactory.AnnotationProcessingTaskFactory$StandardTaskAction.execute(AnnotationProcessingTaskFactory.java:209)
at org.gradle.api.internal.AbstractTask$TaskActionWrapper.execute(AbstractTask.java:585)
at org.gradle.api.internal.AbstractTask$TaskActionWrapper.execute(AbstractTask.java:568)
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeAction(ExecuteActionsTaskExecuter.java:80)
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:61)
... 68 more
Caused by: de.thetaphi.forbiddenapis.ForbiddenApiException: Check for forbidden API calls failed: java.lang.ClassNotFoundException: java.lang.invoke.StringConcatFactory
at de.thetaphi.forbiddenapis.Checker.run(Checker.java:550)
at de.thetaphi.forbiddenapis.gradle.CheckForbiddenApis.checkForbidden(CheckForbiddenApis.java:551)
at org.gradle.internal.reflect.JavaMethod.invoke(JavaMethod.java:75)
... 75 more
Caused by: java.lang.ClassNotFoundException: java.lang.invoke.StringConcatFactory
at de.thetaphi.forbiddenapis.Checker.getClassFromClassLoader(Checker.java:264)
at de.thetaphi.forbiddenapis.Checker.lookupRelatedClass(Checker.java:277)
at de.thetaphi.forbiddenapis.ClassScanner$2.checkMethodAccess(ClassScanner.java:349)
at de.thetaphi.forbiddenapis.ClassScanner$2.checkHandle(ClassScanner.java:411)
at de.thetaphi.forbiddenapis.ClassScanner$2.visitInvokeDynamicInsn(ClassScanner.java:497)
at de.thetaphi.forbiddenapis.asm.ClassReader.a(Unknown Source)
at de.thetaphi.forbiddenapis.asm.ClassReader.b(Unknown Source)
at de.thetaphi.forbiddenapis.asm.ClassReader.accept(Unknown Source)
at de.thetaphi.forbiddenapis.asm.ClassReader.accept(Unknown Source)
at de.thetaphi.forbiddenapis.Checker.checkClass(Checker.java:528)
at de.thetaphi.forbiddenapis.Checker.run(Checker.java:545)
... 77 more
BUILD FAILED
```
| non_priority | build is buggy for java try compiling with java first you will hit this this can be fixed by using assertequals which also simplifies the test home rmuir workspace elasticsearch core src test java org elasticsearch threadpool scalingthreadpooltests java error method invoked with incorrect number of arguments expected found assertthat stats threadpool threadpoolname getthreads equalto home rmuir workspace elasticsearch core src test java org elasticsearch threadpool scalingthreadpooltests java error method invoked with incorrect number of arguments expected found assertthat stats threadpool threadpoolname getcompleted equalto next problem is that i am unsure source target settings are being passed at all because i see class files referencing java stringconcatfactory next problem is that forbidden apis screams presumably because its being run in the wrong jvm not the java home that is set but the java one running gradle itself it sees stringconcatfactory and fails the build caused by org gradle internal uncheckedexception de thetaphi forbiddenapis forbiddenapiexception check for forbidden api calls failed java lang classnotfoundexception java lang invoke stringconcatfactory at org gradle internal uncheckedexception throwasuncheckedexception uncheckedexception java at org gradle internal reflect javamethod invoke javamethod java at org gradle api internal project taskfactory annotationprocessingtaskfactory standardtaskaction doexecute annotationprocessingtaskfactory java at org gradle api internal project taskfactory annotationprocessingtaskfactory standardtaskaction execute annotationprocessingtaskfactory java at org gradle api internal project taskfactory annotationprocessingtaskfactory standardtaskaction execute annotationprocessingtaskfactory java at org gradle api internal abstracttask taskactionwrapper execute abstracttask java at org gradle api internal abstracttask taskactionwrapper execute abstracttask java at org gradle api internal tasks execution executeactionstaskexecuter executeaction executeactionstaskexecuter java at org gradle api internal tasks execution executeactionstaskexecuter executeactions executeactionstaskexecuter java more caused by de thetaphi forbiddenapis forbiddenapiexception check for forbidden api calls failed java lang classnotfoundexception java lang invoke stringconcatfactory at de thetaphi forbiddenapis checker run checker java at de thetaphi forbiddenapis gradle checkforbiddenapis checkforbidden checkforbiddenapis java at org gradle internal reflect javamethod invoke javamethod java more caused by java lang classnotfoundexception java lang invoke stringconcatfactory at de thetaphi forbiddenapis checker getclassfromclassloader checker java at de thetaphi forbiddenapis checker lookuprelatedclass checker java at de thetaphi forbiddenapis classscanner checkmethodaccess classscanner java at de thetaphi forbiddenapis classscanner checkhandle classscanner java at de thetaphi forbiddenapis classscanner visitinvokedynamicinsn classscanner java at de thetaphi forbiddenapis asm classreader a unknown source at de thetaphi forbiddenapis asm classreader b unknown source at de thetaphi forbiddenapis asm classreader accept unknown source at de thetaphi forbiddenapis asm classreader accept unknown source at de thetaphi forbiddenapis checker checkclass checker java at de thetaphi forbiddenapis checker run checker java more build failed | 0 |
80,682 | 7,753,743,754 | IssuesEvent | 2018-05-31 02:30:28 | ElementsProject/lightning | https://api.github.com/repos/ElementsProject/lightning | closed | Travis should test in parallel | testing | Our tests run much faster in parallel, particularly due to polling delays, etc. I run -n10 on my laptop (without valgrind) with no problems.
That would allow us to re-enable some non-developer tests, for example. | 1.0 | Travis should test in parallel - Our tests run much faster in parallel, particularly due to polling delays, etc. I run -n10 on my laptop (without valgrind) with no problems.
That would allow us to re-enable some non-developer tests, for example. | non_priority | travis should test in parallel our tests run much faster in parallel particularly due to polling delays etc i run on my laptop without valgrind with no problems that would allow us to re enable some non developer tests for example | 0 |
1,571 | 6,572,329,951 | IssuesEvent | 2017-09-11 01:26:32 | ansible/ansible-modules-extras | https://api.github.com/repos/ansible/ansible-modules-extras | closed | lxc_container: provide option to make automatic container restarts optional | affects_2.1 cloud feature_idea waiting_on_maintainer | <!--- Verify first that your issue/request is not already reported in GitHub -->
##### ISSUE TYPE
<!--- Pick one below and delete the rest: -->
- Feature Idea
##### COMPONENT NAME
<!--- Name of the plugin/module/task -->
lxc_container
##### ANSIBLE VERSION
<!--- Paste verbatim output from “ansible --version” between quotes below -->
```
ansible 2.1.0.0
config file =
configured module search path = Default w/o overrides
```
##### CONFIGURATION
<!---
Mention any settings you have changed/added/removed in ansible.cfg
(or using the ANSIBLE_* environment variables).
-->
None
##### OS / ENVIRONMENT
<!---
Mention the OS you are running Ansible from, and the OS you are
managing, or say “N/A” for anything that is not platform-specific.
-->
N/A
##### SUMMARY
<!--- Explain the problem briefly -->
When the container_config is changed (and some other options are implemented), the module actions a container restart. It would be great if that behaviour could be optional so that it is possible to use handlers/tasks to action a restart at a later time.
##### STEPS TO REPRODUCE
<!---
For bugs, show exactly how to reproduce the problem.
For new features, show how the feature would be used.
-->
N/A
<!--- Paste example playbooks or commands between quotes below -->
```
N/A
```
<!--- You can also paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!--- What did you expect to happen when running the steps above? -->
N/A
##### ACTUAL RESULTS
<!--- What actually happened? If possible run with high verbosity (-vvvv) -->
<!--- Paste verbatim command output between quotes below -->
```
N/A
```
| True | lxc_container: provide option to make automatic container restarts optional - <!--- Verify first that your issue/request is not already reported in GitHub -->
##### ISSUE TYPE
<!--- Pick one below and delete the rest: -->
- Feature Idea
##### COMPONENT NAME
<!--- Name of the plugin/module/task -->
lxc_container
##### ANSIBLE VERSION
<!--- Paste verbatim output from “ansible --version” between quotes below -->
```
ansible 2.1.0.0
config file =
configured module search path = Default w/o overrides
```
##### CONFIGURATION
<!---
Mention any settings you have changed/added/removed in ansible.cfg
(or using the ANSIBLE_* environment variables).
-->
None
##### OS / ENVIRONMENT
<!---
Mention the OS you are running Ansible from, and the OS you are
managing, or say “N/A” for anything that is not platform-specific.
-->
N/A
##### SUMMARY
<!--- Explain the problem briefly -->
When the container_config is changed (and some other options are implemented), the module actions a container restart. It would be great if that behaviour could be optional so that it is possible to use handlers/tasks to action a restart at a later time.
##### STEPS TO REPRODUCE
<!---
For bugs, show exactly how to reproduce the problem.
For new features, show how the feature would be used.
-->
N/A
<!--- Paste example playbooks or commands between quotes below -->
```
N/A
```
<!--- You can also paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!--- What did you expect to happen when running the steps above? -->
N/A
##### ACTUAL RESULTS
<!--- What actually happened? If possible run with high verbosity (-vvvv) -->
<!--- Paste verbatim command output between quotes below -->
```
N/A
```
| non_priority | lxc container provide option to make automatic container restarts optional issue type feature idea component name lxc container ansible version ansible config file configured module search path default w o overrides configuration mention any settings you have changed added removed in ansible cfg or using the ansible environment variables none os environment mention the os you are running ansible from and the os you are managing or say “n a” for anything that is not platform specific n a summary when the container config is changed and some other options are implemented the module actions a container restart it would be great if that behaviour could be optional so that it is possible to use handlers tasks to action a restart at a later time steps to reproduce for bugs show exactly how to reproduce the problem for new features show how the feature would be used n a n a expected results n a actual results n a | 0 |
208,756 | 16,136,439,836 | IssuesEvent | 2021-04-29 12:28:38 | spring-projects/spring-data-commons | https://api.github.com/repos/spring-projects/spring-data-commons | closed | Table of contents sometimes locates in wrong section (confusion between subsections without id-s) [DATACMNS-1814] | type: bug type: documentation | **[Chealer](https://jira.spring.io/secure/ViewProfile.jspa?name=JIRAUSER50525)** opened **[DATACMNS-1814](https://jira.spring.io/browse/DATACMNS-1814?redirect=false)** and commented
The table of contents at the left of the Spring Data JPA Reference Documentation dynamically changes to reflect the precise subsection being shown. The subsections of sections not displaying do not display.
The mechanism to detect position in the document appears to be malfunctioning, as I realized that moving forward in the document, the ToC would indicate the opposite. This happened when I was going from section 4 to section 5.
When displaying the end of 4.8.3 and the beginning of 5, the ToC correctly contains:
1. [Preface](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#preface)
1. [1. Project Metadata](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#project)
2. [2. New & Noteworthy](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#new-features)
3. [3. Dependencies](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#dependencies)
4. [4. Working with Spring Data Repositories](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#repositories)
1. [4.1. Core concepts](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#repositories.core-concepts)
2. [4.2. Query methods](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#repositories.query-methods)
3. [4.3. Defining Repository Interfaces](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#repositories.definition)
4. [4.4. Defining Query Methods](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#repositories.query-methods.details)
5. [4.5. Creating Repository Instances](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#repositories.create-instances)
6. [4.6. Custom Implementations for Spring Data Repositories](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#repositories.custom-implementations)
7. [4.7. Publishing Events from Aggregate Roots](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#core.domain-events)
8. [4.8. Spring Data Extensions](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#core.extensions)
#### [4.8.1. Querydsl Extension](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#core.extensions.querydsl)
#### [4.8.2. Web support](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#core.web)
#### [4.8.3. Repository Populators](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#core.repository-populators)
1. [Reference Documentation](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#reference)
1. [5. JPA Repositories](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#jpa.repositories)
2. [Appendix](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#appendix)
1. [Appendix A: Namespace reference](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#repositories.namespace-reference)
2. [Appendix B: Populators namespace reference](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#populator.namespace-reference)
3. [Appendix C: Repository query keywords](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#repository-query-keywords)
4. [Appendix D: Repository query return types](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#repository-query-return-types)
5. [Appendix E: Frequently Asked Questions](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#faq)
6. [Appendix F: Glossary](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#glossary)
But after pressing Page down, it displays as if I had went back to 4.5.1:
1. [Preface](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#preface)
1. [1. Project Metadata](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#project)
2. [2. New & Noteworthy](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#new-features)
3. [3. Dependencies](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#dependencies)
4. [4. Working with Spring Data Repositories](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#repositories)
1. [4.1. Core concepts](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#repositories.core-concepts)
2. [4.2. Query methods](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#repositories.query-methods)
3. [4.3. Defining Repository Interfaces](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#repositories.definition)
4. [4.4. Defining Query Methods](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#repositories.query-methods.details)
5. [4.5. Creating Repository Instances](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#repositories.create-instances)
#### [4.5.1. XML configuration](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#repositories.create-instances.spring)
##### [Using filters](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#)
#### [4.5.2. JavaConfig](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#repositories.create-instances.java-config)
#### [4.5.3. Standalone usage](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#repositories.create-instances.standalone)
1. [4.6. Custom Implementations for Spring Data Repositories](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#repositories.custom-implementations)
1. [4.7. Publishing Events from Aggregate Roots](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#core.domain-events)
1. [4.8. Spring Data Extensions](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#core.extensions)
1. [Reference Documentation](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#reference)
1. [5. JPA Repositories](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#jpa.repositories)
2. [Appendix](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#appendix)
1. [Appendix A: Namespace reference](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#repositories.namespace-reference)
2. [Appendix B: Populators namespace reference](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#populator.namespace-reference)
3. [Appendix C: Repository query keywords](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#repository-query-keywords)
4. [Appendix D: Repository query return types](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#repository-query-return-types)
5. [Appendix E: Frequently Asked Questions](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#faq)
6. [Appendix F: Glossary](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#glossary)
This happens whether using Google Chrome 85 or Firefox 81, -but only when the viewport is sufficiently high. This can happen at 1153 pixels of height, but probably not when just a little less-. The difference between the Spring ToC correct and Spring ToC incorrect screenshots is exactly one Page Up/Down.
It should also be noted that the link for Using filters (in 4.5.1) is broken (it brings to the document's start)
---
**Affects:** 2.3.4 (Neumann SR4)
**Reference URL:** https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#core.repository-populators
**Attachments:**
- [Spring ToC correct.png](https://jira.spring.io/secure/attachment/28823/Spring+ToC+correct.png) (_206.18 kB_)
- [Spring ToC incorrect.png](https://jira.spring.io/secure/attachment/28822/Spring+ToC+incorrect.png) (_242.29 kB_)
**Referenced from:** pull request https://github.com/spring-projects/spring-data-commons/pull/470
**Backported to:** [2.3.5 (Neumann SR5)](https://github.com/spring-projects/spring-data-commons/milestone/200?closed=1), [2.2.11 (Moore SR11)](https://github.com/spring-projects/spring-data-commons/milestone/199?closed=1)
| 1.0 | Table of contents sometimes locates in wrong section (confusion between subsections without id-s) [DATACMNS-1814] - **[Chealer](https://jira.spring.io/secure/ViewProfile.jspa?name=JIRAUSER50525)** opened **[DATACMNS-1814](https://jira.spring.io/browse/DATACMNS-1814?redirect=false)** and commented
The table of contents at the left of the Spring Data JPA Reference Documentation dynamically changes to reflect the precise subsection being shown. The subsections of sections not displaying do not display.
The mechanism to detect position in the document appears to be malfunctioning, as I realized that moving forward in the document, the ToC would indicate the opposite. This happened when I was going from section 4 to section 5.
When displaying the end of 4.8.3 and the beginning of 5, the ToC correctly contains:
1. [Preface](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#preface)
1. [1. Project Metadata](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#project)
2. [2. New & Noteworthy](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#new-features)
3. [3. Dependencies](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#dependencies)
4. [4. Working with Spring Data Repositories](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#repositories)
1. [4.1. Core concepts](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#repositories.core-concepts)
2. [4.2. Query methods](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#repositories.query-methods)
3. [4.3. Defining Repository Interfaces](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#repositories.definition)
4. [4.4. Defining Query Methods](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#repositories.query-methods.details)
5. [4.5. Creating Repository Instances](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#repositories.create-instances)
6. [4.6. Custom Implementations for Spring Data Repositories](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#repositories.custom-implementations)
7. [4.7. Publishing Events from Aggregate Roots](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#core.domain-events)
8. [4.8. Spring Data Extensions](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#core.extensions)
#### [4.8.1. Querydsl Extension](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#core.extensions.querydsl)
#### [4.8.2. Web support](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#core.web)
#### [4.8.3. Repository Populators](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#core.repository-populators)
1. [Reference Documentation](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#reference)
1. [5. JPA Repositories](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#jpa.repositories)
2. [Appendix](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#appendix)
1. [Appendix A: Namespace reference](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#repositories.namespace-reference)
2. [Appendix B: Populators namespace reference](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#populator.namespace-reference)
3. [Appendix C: Repository query keywords](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#repository-query-keywords)
4. [Appendix D: Repository query return types](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#repository-query-return-types)
5. [Appendix E: Frequently Asked Questions](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#faq)
6. [Appendix F: Glossary](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#glossary)
But after pressing Page down, it displays as if I had went back to 4.5.1:
1. [Preface](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#preface)
1. [1. Project Metadata](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#project)
2. [2. New & Noteworthy](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#new-features)
3. [3. Dependencies](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#dependencies)
4. [4. Working with Spring Data Repositories](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#repositories)
1. [4.1. Core concepts](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#repositories.core-concepts)
2. [4.2. Query methods](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#repositories.query-methods)
3. [4.3. Defining Repository Interfaces](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#repositories.definition)
4. [4.4. Defining Query Methods](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#repositories.query-methods.details)
5. [4.5. Creating Repository Instances](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#repositories.create-instances)
#### [4.5.1. XML configuration](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#repositories.create-instances.spring)
##### [Using filters](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#)
#### [4.5.2. JavaConfig](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#repositories.create-instances.java-config)
#### [4.5.3. Standalone usage](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#repositories.create-instances.standalone)
1. [4.6. Custom Implementations for Spring Data Repositories](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#repositories.custom-implementations)
1. [4.7. Publishing Events from Aggregate Roots](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#core.domain-events)
1. [4.8. Spring Data Extensions](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#core.extensions)
1. [Reference Documentation](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#reference)
1. [5. JPA Repositories](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#jpa.repositories)
2. [Appendix](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#appendix)
1. [Appendix A: Namespace reference](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#repositories.namespace-reference)
2. [Appendix B: Populators namespace reference](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#populator.namespace-reference)
3. [Appendix C: Repository query keywords](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#repository-query-keywords)
4. [Appendix D: Repository query return types](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#repository-query-return-types)
5. [Appendix E: Frequently Asked Questions](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#faq)
6. [Appendix F: Glossary](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#glossary)
This happens whether using Google Chrome 85 or Firefox 81, -but only when the viewport is sufficiently high. This can happen at 1153 pixels of height, but probably not when just a little less-. The difference between the Spring ToC correct and Spring ToC incorrect screenshots is exactly one Page Up/Down.
It should also be noted that the link for Using filters (in 4.5.1) is broken (it brings to the document's start)
---
**Affects:** 2.3.4 (Neumann SR4)
**Reference URL:** https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#core.repository-populators
**Attachments:**
- [Spring ToC correct.png](https://jira.spring.io/secure/attachment/28823/Spring+ToC+correct.png) (_206.18 kB_)
- [Spring ToC incorrect.png](https://jira.spring.io/secure/attachment/28822/Spring+ToC+incorrect.png) (_242.29 kB_)
**Referenced from:** pull request https://github.com/spring-projects/spring-data-commons/pull/470
**Backported to:** [2.3.5 (Neumann SR5)](https://github.com/spring-projects/spring-data-commons/milestone/200?closed=1), [2.2.11 (Moore SR11)](https://github.com/spring-projects/spring-data-commons/milestone/199?closed=1)
| non_priority | table of contents sometimes locates in wrong section confusion between subsections without id s opened and commented the table of contents at the left of the spring data jpa reference documentation dynamically changes to reflect the precise subsection being shown the subsections of sections not displaying do not display the mechanism to detect position in the document appears to be malfunctioning as i realized that moving forward in the document the toc would indicate the opposite this happened when i was going from section to section when displaying the end of and the beginning of the toc correctly contains but after pressing page down it displays as if i had went back to this happens whether using google chrome or firefox but only when the viewport is sufficiently high this can happen at pixels of height but probably not when just a little less the difference between the spring toc correct and spring toc incorrect screenshots is exactly one page up down it should also be noted that the link for using filters in is broken it brings to the document s start affects neumann reference url attachments kb kb referenced from pull request backported to | 0 |
131,695 | 28,007,448,694 | IssuesEvent | 2023-03-27 16:07:35 | tarantool/tarantool | https://api.github.com/repos/tarantool/tarantool | opened | Internal helper tuple_extract_key_raw helper extracts wrong key | code health | When I added a fair test:
```diff
diff --git a/test/unit/key_def.c b/test/unit/key_def.c
index 65f579ca4..286b26461 100644
--- a/test/unit/key_def.c
+++ b/test/unit/key_def.c
@@ -292,14 +292,43 @@ test_tuple_extract_key_raw_slowpath_nullable(void)
check_plan();
}
+static void
+test_tuple_extract_key_raw_my_case(void)
+{
+ plan(1);
+ header();
+
+ struct key_def *def = test_key_def_new(
+ "[{%s%u%s%s%s%b}{%s%u%s%s%s%b}]",
+ "field", 1, "type", "unsigned", "is_nullable", 1,
+ "field", 2, "type", "unsigned", "is_nullable", 1);
+ fail_if(def == NULL);
+ struct tuple *tuple = test_tuple_new("[%u]", 10);
+ fail_if(tuple == NULL);
+ char *key = test_key_new("[NILNIL]");
+ fail_if(key == NULL);
+
+ size_t region_svp = region_used(&fiber()->gc);
+ test_check_tuple_extract_key_raw(def, tuple, key);
+
+ key_def_delete(def);
+ tuple_delete(tuple);
+ free(key);
+ region_truncate(&fiber()->gc, region_svp);
+
+ footer();
+ check_plan();
+}
+
static int
test_main(void)
{
- plan(2);
+ plan(3);
header();
test_func_compare_with_key();
test_tuple_extract_key_raw_slowpath_nullable();
+ test_tuple_extract_key_raw_my_case();
footer();
return check_plan();
```
I got an error : `not ok 1 - Extracted key of tuple [10] is [80, 80], expected [null, null]`. Fortunately, it does not affect tarantool now - AFAICS, tuple extractors are used with `key_def`s that have at least one field.
Also, I'v fixed another [problem](https://github.com/tarantool/tarantool/commit/5fc454dbec69190a31b3405ac2888265d273c508) with raw extractor earlier. I think we should cover key extractors with unit tests because these helpers are fundamental for tarantool, and it shouldn't be difficult since we already have infrastructure for key_def tests. | 1.0 | Internal helper tuple_extract_key_raw helper extracts wrong key - When I added a fair test:
```diff
diff --git a/test/unit/key_def.c b/test/unit/key_def.c
index 65f579ca4..286b26461 100644
--- a/test/unit/key_def.c
+++ b/test/unit/key_def.c
@@ -292,14 +292,43 @@ test_tuple_extract_key_raw_slowpath_nullable(void)
check_plan();
}
+static void
+test_tuple_extract_key_raw_my_case(void)
+{
+ plan(1);
+ header();
+
+ struct key_def *def = test_key_def_new(
+ "[{%s%u%s%s%s%b}{%s%u%s%s%s%b}]",
+ "field", 1, "type", "unsigned", "is_nullable", 1,
+ "field", 2, "type", "unsigned", "is_nullable", 1);
+ fail_if(def == NULL);
+ struct tuple *tuple = test_tuple_new("[%u]", 10);
+ fail_if(tuple == NULL);
+ char *key = test_key_new("[NILNIL]");
+ fail_if(key == NULL);
+
+ size_t region_svp = region_used(&fiber()->gc);
+ test_check_tuple_extract_key_raw(def, tuple, key);
+
+ key_def_delete(def);
+ tuple_delete(tuple);
+ free(key);
+ region_truncate(&fiber()->gc, region_svp);
+
+ footer();
+ check_plan();
+}
+
static int
test_main(void)
{
- plan(2);
+ plan(3);
header();
test_func_compare_with_key();
test_tuple_extract_key_raw_slowpath_nullable();
+ test_tuple_extract_key_raw_my_case();
footer();
return check_plan();
```
I got an error : `not ok 1 - Extracted key of tuple [10] is [80, 80], expected [null, null]`. Fortunately, it does not affect tarantool now - AFAICS, tuple extractors are used with `key_def`s that have at least one field.
Also, I'v fixed another [problem](https://github.com/tarantool/tarantool/commit/5fc454dbec69190a31b3405ac2888265d273c508) with raw extractor earlier. I think we should cover key extractors with unit tests because these helpers are fundamental for tarantool, and it shouldn't be difficult since we already have infrastructure for key_def tests. | non_priority | internal helper tuple extract key raw helper extracts wrong key when i added a fair test diff diff git a test unit key def c b test unit key def c index a test unit key def c b test unit key def c test tuple extract key raw slowpath nullable void check plan static void test tuple extract key raw my case void plan header struct key def def test key def new field type unsigned is nullable field type unsigned is nullable fail if def null struct tuple tuple test tuple new fail if tuple null char key test key new fail if key null size t region svp region used fiber gc test check tuple extract key raw def tuple key key def delete def tuple delete tuple free key region truncate fiber gc region svp footer check plan static int test main void plan plan header test func compare with key test tuple extract key raw slowpath nullable test tuple extract key raw my case footer return check plan i got an error not ok extracted key of tuple is expected fortunately it does not affect tarantool now afaics tuple extractors are used with key def s that have at least one field also i v fixed another with raw extractor earlier i think we should cover key extractors with unit tests because these helpers are fundamental for tarantool and it shouldn t be difficult since we already have infrastructure for key def tests | 0 |
217,955 | 16,745,385,424 | IssuesEvent | 2021-06-11 14:54:42 | nilisha-jais/Musicophilia | https://api.github.com/repos/nilisha-jais/Musicophilia | opened | Add Badges and Contributors | documentation | ## 📚 Documentation
**Update README**
There must a proper readme file, currently it is not design properly.
I would like to arrange it in proper way and add few more sections to it i.e. shields badges and contributors
The contribution steps are also having inappropriate design.
## Add relevant screenshot or video (if any)
Here is the sample of Readme I'd recently made: [Click Here](https://github.com/akshitadixit/VCallZer#vcallzer-)
Please assign me this issue under LGM-SOC'21
| 1.0 | Add Badges and Contributors - ## 📚 Documentation
**Update README**
There must a proper readme file, currently it is not design properly.
I would like to arrange it in proper way and add few more sections to it i.e. shields badges and contributors
The contribution steps are also having inappropriate design.
## Add relevant screenshot or video (if any)
Here is the sample of Readme I'd recently made: [Click Here](https://github.com/akshitadixit/VCallZer#vcallzer-)
Please assign me this issue under LGM-SOC'21
| non_priority | add badges and contributors 📚 documentation update readme there must a proper readme file currently it is not design properly i would like to arrange it in proper way and add few more sections to it i e shields badges and contributors the contribution steps are also having inappropriate design add relevant screenshot or video if any here is the sample of readme i d recently made please assign me this issue under lgm soc | 0 |
263,518 | 19,913,933,569 | IssuesEvent | 2022-01-25 20:13:46 | EkaterinaKokh/Ekaterina-Kokh-TKI-111 | https://api.github.com/repos/EkaterinaKokh/Ekaterina-Kokh-TKI-111 | closed | Задание 1-3 | documentation enhancement | **Задание 1-3**
Создать консольное приложение для решения задачи, представленной в таблице. Данные для решения вводит пользователь. Помните, что ввод необходимо проверять на правильность (только числа). Вывести результат вычислений на экран. При необходимости дополнить свой отчёт поясняющими формулами, помогающими решить задачу.
| 1.0 | Задание 1-3 - **Задание 1-3**
Создать консольное приложение для решения задачи, представленной в таблице. Данные для решения вводит пользователь. Помните, что ввод необходимо проверять на правильность (только числа). Вывести результат вычислений на экран. При необходимости дополнить свой отчёт поясняющими формулами, помогающими решить задачу.
| non_priority | задание задание создать консольное приложение для решения задачи представленной в таблице данные для решения вводит пользователь помните что ввод необходимо проверять на правильность только числа вывести результат вычислений на экран при необходимости дополнить свой отчёт поясняющими формулами помогающими решить задачу | 0 |
139,101 | 18,840,211,280 | IssuesEvent | 2021-11-11 08:39:44 | rammatzkvosky/Home-assignment | https://api.github.com/repos/rammatzkvosky/Home-assignment | opened | CVE-2019-17267 (High) detected in jackson-databind-2.8.7.jar | security vulnerability | ## CVE-2019-17267 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jackson-databind-2.8.7.jar</b></p></summary>
<p>General data-binding functionality for Jackson: works on core streaming API</p>
<p>Library home page: <a href="http://github.com/FasterXML/jackson">http://github.com/FasterXML/jackson</a></p>
<p>Path to dependency file: Home-assignment/pom.xml</p>
<p>Path to vulnerable library: itory/com/fasterxml/jackson/core/jackson-databind/2.8.7/jackson-databind-2.8.7.jar</p>
<p>
Dependency Hierarchy:
- :x: **jackson-databind-2.8.7.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/rammatzkvosky/Home-assignment/commit/994eb8c8e34df13ffb792b62ec4c8e5c05738834">994eb8c8e34df13ffb792b62ec4c8e5c05738834</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
A Polymorphic Typing issue was discovered in FasterXML jackson-databind before 2.9.10. It is related to net.sf.ehcache.hibernate.EhcacheJtaTransactionManagerLookup.
<p>Publish Date: 2019-10-07
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-17267>CVE-2019-17267</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/FasterXML/jackson-databind/issues/2460">https://github.com/FasterXML/jackson-databind/issues/2460</a></p>
<p>Release Date: 2019-10-07</p>
<p>Fix Resolution: com.fasterxml.jackson.core:jackson-databind:2.8.11.5,2.9.10</p>
</p>
</details>
<p></p>
***
:rescue_worker_helmet: Automatic Remediation is available for this issue
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"com.fasterxml.jackson.core","packageName":"jackson-databind","packageVersion":"2.8.7","packageFilePaths":["/pom.xml"],"isTransitiveDependency":false,"dependencyTree":"com.fasterxml.jackson.core:jackson-databind:2.8.7","isMinimumFixVersionAvailable":true,"minimumFixVersion":"com.fasterxml.jackson.core:jackson-databind:2.8.11.5,2.9.10"}],"baseBranches":["main"],"vulnerabilityIdentifier":"CVE-2019-17267","vulnerabilityDetails":"A Polymorphic Typing issue was discovered in FasterXML jackson-databind before 2.9.10. It is related to net.sf.ehcache.hibernate.EhcacheJtaTransactionManagerLookup.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-17267","cvss3Severity":"high","cvss3Score":"9.8","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> --> | True | CVE-2019-17267 (High) detected in jackson-databind-2.8.7.jar - ## CVE-2019-17267 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jackson-databind-2.8.7.jar</b></p></summary>
<p>General data-binding functionality for Jackson: works on core streaming API</p>
<p>Library home page: <a href="http://github.com/FasterXML/jackson">http://github.com/FasterXML/jackson</a></p>
<p>Path to dependency file: Home-assignment/pom.xml</p>
<p>Path to vulnerable library: itory/com/fasterxml/jackson/core/jackson-databind/2.8.7/jackson-databind-2.8.7.jar</p>
<p>
Dependency Hierarchy:
- :x: **jackson-databind-2.8.7.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/rammatzkvosky/Home-assignment/commit/994eb8c8e34df13ffb792b62ec4c8e5c05738834">994eb8c8e34df13ffb792b62ec4c8e5c05738834</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
A Polymorphic Typing issue was discovered in FasterXML jackson-databind before 2.9.10. It is related to net.sf.ehcache.hibernate.EhcacheJtaTransactionManagerLookup.
<p>Publish Date: 2019-10-07
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-17267>CVE-2019-17267</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/FasterXML/jackson-databind/issues/2460">https://github.com/FasterXML/jackson-databind/issues/2460</a></p>
<p>Release Date: 2019-10-07</p>
<p>Fix Resolution: com.fasterxml.jackson.core:jackson-databind:2.8.11.5,2.9.10</p>
</p>
</details>
<p></p>
***
:rescue_worker_helmet: Automatic Remediation is available for this issue
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"com.fasterxml.jackson.core","packageName":"jackson-databind","packageVersion":"2.8.7","packageFilePaths":["/pom.xml"],"isTransitiveDependency":false,"dependencyTree":"com.fasterxml.jackson.core:jackson-databind:2.8.7","isMinimumFixVersionAvailable":true,"minimumFixVersion":"com.fasterxml.jackson.core:jackson-databind:2.8.11.5,2.9.10"}],"baseBranches":["main"],"vulnerabilityIdentifier":"CVE-2019-17267","vulnerabilityDetails":"A Polymorphic Typing issue was discovered in FasterXML jackson-databind before 2.9.10. It is related to net.sf.ehcache.hibernate.EhcacheJtaTransactionManagerLookup.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-17267","cvss3Severity":"high","cvss3Score":"9.8","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> --> | non_priority | cve high detected in jackson databind jar cve high severity vulnerability vulnerable library jackson databind jar general data binding functionality for jackson works on core streaming api library home page a href path to dependency file home assignment pom xml path to vulnerable library itory com fasterxml jackson core jackson databind jackson databind jar dependency hierarchy x jackson databind jar vulnerable library found in head commit a href found in base branch main vulnerability details a polymorphic typing issue was discovered in fasterxml jackson databind before it is related to net sf ehcache hibernate ehcachejtatransactionmanagerlookup publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution com fasterxml jackson core jackson databind rescue worker helmet automatic remediation is available for this issue isopenpronvulnerability true ispackagebased true isdefaultbranch true packages istransitivedependency false dependencytree com fasterxml jackson core jackson databind isminimumfixversionavailable true minimumfixversion com fasterxml jackson core jackson databind basebranches vulnerabilityidentifier cve vulnerabilitydetails a polymorphic typing issue was discovered in fasterxml jackson databind before it is related to net sf ehcache hibernate ehcachejtatransactionmanagerlookup vulnerabilityurl | 0 |
232,877 | 18,921,189,631 | IssuesEvent | 2021-11-17 02:00:44 | dotnet/aspnetcore | https://api.github.com/repos/dotnet/aspnetcore | closed | WebApplicationFactory does not resolve the custom configured SQL Provider, but the one from Startup | investigate Needs: Author Feedback :heavy_check_mark: Resolution: Answered Status: Resolved feature-mvc-testing area-web-frameworks | <!--
More information on our issue management policies can be found here: https://aka.ms/aspnet/issue-policies
Please keep in mind that the GitHub issue tracker is not intended as a general support forum, but for reporting **non-security** bugs and feature requests.
If you believe you have an issue that affects the SECURITY of the platform, please do NOT create an issue and instead email your issue details to secure@microsoft.com. Your report may be eligible for our [bug bounty](https://www.microsoft.com/en-us/msrc/bounty-dot-net-core) but ONLY if it is reported through email.
For other types of questions, consider using [StackOverflow](https://stackoverflow.com).
-->
### Describe the bug
#### WebApplicationFactory does not resolve the custom configured SQL Provider, but the one from Startup.
In the repository that reproduces this issue, the Startup class registers a DbContext with SQL Server, and the tests fixture registers it as in Memory. When the test is executed, instead of using the InMemory provider, it uses the SQL Provider. The code follows this [documentation ](https://docs.microsoft.com/en-us/aspnet/core/test/integration-tests?view=aspnetcore-5.0) just to make sure the issue is reproduced correctly.
The problem can be fixed if either `CreateHostBuilder` creates an `IWebHostBuilder` and not an `IHostBuilder`, or if the CreateHosts from WebApplicationFactory are overridden to create a IWebHostBuilder, such as in this [class](https://github.com/code4romania/monitorizare-vot/pull/376/files#diff-8dc711acfe80e86a5b54053e8dcf4b96130c8d59655120b8fee9a87f91cf87ba)
```csharp
protected override IWebHostBuilder CreateWebHostBuilder()
=> WebHost.CreateDefaultBuilder(null).UseStartup<Startup>();
protected override IHostBuilder CreateHostBuilder() => null;
```
### To Reproduce
<!--
We ❤ code! Point us to a minimalistic repro project hosted in a GitHub repo.
For a repro project, create a new ASP.NET Core project using the template of your your choice, apply the minimum required code to result in the issue you're observing.
We will close this issue if:
- the repro project you share with us is complex. We can't investigate custom projects, so don't point us to such, please.
- if we will not be able to repro the behavior you're reporting
-->
https://github.com/adrianiftode/ASP.NET-IntegrationTests-Issue
### Exceptions (if any)
<!--
Include the exception you get when facing this issue
-->
### Further technical details
- ASP.NET Core version - 5.0
- Include the output of `dotnet --info`
```
.NET SDK (reflecting any global.json):
Version: 5.0.101
Commit: d05174dc5a
Runtime Environment:
OS Name: Windows
OS Version: 10.0.18362
OS Platform: Windows
RID: win10-x64
Base Path: C:\Program Files\dotnet\sdk\5.0.101\
Host (useful for support):
Version: 5.0.1
Commit: b02e13abab
.NET SDKs installed:
2.1.102 [C:\Program Files\dotnet\sdk]
2.1.518 [C:\Program Files\dotnet\sdk]
3.1.201 [C:\Program Files\dotnet\sdk]
3.1.302 [C:\Program Files\dotnet\sdk]
5.0.101 [C:\Program Files\dotnet\sdk]
.NET runtimes installed:
Microsoft.AspNetCore.All 2.1.22 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.1.23 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.App 2.1.22 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.1.23 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 3.1.3 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 3.1.6 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 3.1.10 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 5.0.1 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 2.0.6 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.22 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.23 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 3.1.3 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 3.1.6 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 3.1.10 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 5.0.1 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.WindowsDesktop.App 3.1.3 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 3.1.6 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 3.1.10 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 5.0.1 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
```
- The IDE (VS / VS Code/ VS4Mac) you're running on, and its version
VS -
Microsoft Visual Studio Professional 2019
Version 16.8.3 | 1.0 | WebApplicationFactory does not resolve the custom configured SQL Provider, but the one from Startup - <!--
More information on our issue management policies can be found here: https://aka.ms/aspnet/issue-policies
Please keep in mind that the GitHub issue tracker is not intended as a general support forum, but for reporting **non-security** bugs and feature requests.
If you believe you have an issue that affects the SECURITY of the platform, please do NOT create an issue and instead email your issue details to secure@microsoft.com. Your report may be eligible for our [bug bounty](https://www.microsoft.com/en-us/msrc/bounty-dot-net-core) but ONLY if it is reported through email.
For other types of questions, consider using [StackOverflow](https://stackoverflow.com).
-->
### Describe the bug
#### WebApplicationFactory does not resolve the custom configured SQL Provider, but the one from Startup.
In the repository that reproduces this issue, the Startup class registers a DbContext with SQL Server, and the tests fixture registers it as in Memory. When the test is executed, instead of using the InMemory provider, it uses the SQL Provider. The code follows this [documentation ](https://docs.microsoft.com/en-us/aspnet/core/test/integration-tests?view=aspnetcore-5.0) just to make sure the issue is reproduced correctly.
The problem can be fixed if either `CreateHostBuilder` creates an `IWebHostBuilder` and not an `IHostBuilder`, or if the CreateHosts from WebApplicationFactory are overridden to create a IWebHostBuilder, such as in this [class](https://github.com/code4romania/monitorizare-vot/pull/376/files#diff-8dc711acfe80e86a5b54053e8dcf4b96130c8d59655120b8fee9a87f91cf87ba)
```csharp
protected override IWebHostBuilder CreateWebHostBuilder()
=> WebHost.CreateDefaultBuilder(null).UseStartup<Startup>();
protected override IHostBuilder CreateHostBuilder() => null;
```
### To Reproduce
<!--
We ❤ code! Point us to a minimalistic repro project hosted in a GitHub repo.
For a repro project, create a new ASP.NET Core project using the template of your your choice, apply the minimum required code to result in the issue you're observing.
We will close this issue if:
- the repro project you share with us is complex. We can't investigate custom projects, so don't point us to such, please.
- if we will not be able to repro the behavior you're reporting
-->
https://github.com/adrianiftode/ASP.NET-IntegrationTests-Issue
### Exceptions (if any)
<!--
Include the exception you get when facing this issue
-->
### Further technical details
- ASP.NET Core version - 5.0
- Include the output of `dotnet --info`
```
.NET SDK (reflecting any global.json):
Version: 5.0.101
Commit: d05174dc5a
Runtime Environment:
OS Name: Windows
OS Version: 10.0.18362
OS Platform: Windows
RID: win10-x64
Base Path: C:\Program Files\dotnet\sdk\5.0.101\
Host (useful for support):
Version: 5.0.1
Commit: b02e13abab
.NET SDKs installed:
2.1.102 [C:\Program Files\dotnet\sdk]
2.1.518 [C:\Program Files\dotnet\sdk]
3.1.201 [C:\Program Files\dotnet\sdk]
3.1.302 [C:\Program Files\dotnet\sdk]
5.0.101 [C:\Program Files\dotnet\sdk]
.NET runtimes installed:
Microsoft.AspNetCore.All 2.1.22 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.1.23 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.App 2.1.22 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.1.23 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 3.1.3 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 3.1.6 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 3.1.10 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 5.0.1 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 2.0.6 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.22 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.23 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 3.1.3 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 3.1.6 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 3.1.10 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 5.0.1 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.WindowsDesktop.App 3.1.3 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 3.1.6 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 3.1.10 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 5.0.1 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
```
- The IDE (VS / VS Code/ VS4Mac) you're running on, and its version
VS -
Microsoft Visual Studio Professional 2019
Version 16.8.3 | non_priority | webapplicationfactory does not resolve the custom configured sql provider but the one from startup more information on our issue management policies can be found here please keep in mind that the github issue tracker is not intended as a general support forum but for reporting non security bugs and feature requests if you believe you have an issue that affects the security of the platform please do not create an issue and instead email your issue details to secure microsoft com your report may be eligible for our but only if it is reported through email for other types of questions consider using describe the bug webapplicationfactory does not resolve the custom configured sql provider but the one from startup in the repository that reproduces this issue the startup class registers a dbcontext with sql server and the tests fixture registers it as in memory when the test is executed instead of using the inmemory provider it uses the sql provider the code follows this just to make sure the issue is reproduced correctly the problem can be fixed if either createhostbuilder creates an iwebhostbuilder and not an ihostbuilder or if the createhosts from webapplicationfactory are overridden to create a iwebhostbuilder such as in this csharp protected override iwebhostbuilder createwebhostbuilder webhost createdefaultbuilder null usestartup protected override ihostbuilder createhostbuilder null to reproduce we ❤ code point us to a minimalistic repro project hosted in a github repo for a repro project create a new asp net core project using the template of your your choice apply the minimum required code to result in the issue you re observing we will close this issue if the repro project you share with us is complex we can t investigate custom projects so don t point us to such please if we will not be able to repro the behavior you re reporting exceptions if any include the exception you get when facing this issue further technical details asp net core version include the output of dotnet info net sdk reflecting any global json version commit runtime environment os name windows os version os platform windows rid base path c program files dotnet sdk host useful for support version commit net sdks installed net runtimes installed microsoft aspnetcore all microsoft aspnetcore all microsoft aspnetcore app microsoft aspnetcore app microsoft aspnetcore app microsoft aspnetcore app microsoft aspnetcore app microsoft aspnetcore app microsoft netcore app microsoft netcore app microsoft netcore app microsoft netcore app microsoft netcore app microsoft netcore app microsoft netcore app microsoft windowsdesktop app microsoft windowsdesktop app microsoft windowsdesktop app microsoft windowsdesktop app the ide vs vs code you re running on and its version vs microsoft visual studio professional version | 0 |
1,146 | 3,391,555,186 | IssuesEvent | 2015-11-30 15:58:22 | giantswarm/cli | https://api.github.com/repos/giantswarm/cli | reopened | Warning if variable is not resolved | area/service-definition kind/feature | If a variable could not be resolved during the creation of application, the creation should be aborted or the user warned.
Original Author: @luebken
Created at 06-01-2015 10:48:40
Gitlab: [giantswarm/cli!217](https://git.giantswarm.io/giantswarm/cli/issues/217)
<!---
@huboard:{"order":1.4296875,"milestone_order":21,"custom_state":"archived"}
-->
| 1.0 | Warning if variable is not resolved - If a variable could not be resolved during the creation of application, the creation should be aborted or the user warned.
Original Author: @luebken
Created at 06-01-2015 10:48:40
Gitlab: [giantswarm/cli!217](https://git.giantswarm.io/giantswarm/cli/issues/217)
<!---
@huboard:{"order":1.4296875,"milestone_order":21,"custom_state":"archived"}
-->
| non_priority | warning if variable is not resolved if a variable could not be resolved during the creation of application the creation should be aborted or the user warned original author luebken created at gitlab huboard order milestone order custom state archived | 0 |
426,810 | 29,661,051,062 | IssuesEvent | 2023-06-10 06:35:20 | JohnSnowLabs/spark-nlp | https://api.github.com/repos/JohnSnowLabs/spark-nlp | closed | Quickstart guide is for an older version | documentation | ### Link to the documentation pages (if available)
https://github.com/JohnSnowLabs/spark-nlp/blob/master/examples/python/quick_start.ipynb
### How could the documentation be improved?
When I run the initial suggestion, it throws an exception:
```
import sparknlp
spark = sparknlp.start()
print("Spark NLP version: ", sparknlp.version())
print("Apache Spark version: ", spark.version)
```
I get the following version number:
```
Spark NLP version: 4.4.3
Apache Spark version: 3.4.0
```
I get the following error when trying to run the basic initialization:
```
>>> pipeline = PretrainedPipeline('recognize_entities_dl', 'en')
recognize_entities_dl download started this may take some time.
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/u/nlp/anaconda/main/anaconda3/envs/stanza-1.2/lib/python3.7/site-packages/sparknlp/pretrained/pretrained_pipeline.py", line 54, in __init__
self.model = ResourceDownloader().downloadPipeline(name, lang, remote_loc)
File "/u/nlp/anaconda/main/anaconda3/envs/stanza-1.2/lib/python3.7/site-packages/sparknlp/pretrained/resource_downloader.py", line 142, in downloadPipeline
file_size = _internal._GetResourceSize(name, language, remote_loc).apply()
File "/u/nlp/anaconda/main/anaconda3/envs/stanza-1.2/lib/python3.7/site-packages/sparknlp/internal/__init__.py", line 380, in __init__
"com.johnsnowlabs.nlp.pretrained.PythonResourceDownloader.getDownloadSize", name, language, remote_loc)
File "/u/nlp/anaconda/main/anaconda3/envs/stanza-1.2/lib/python3.7/site-packages/sparknlp/internal/extended_java_wrapper.py", line 27, in __init__
self._java_obj = self.new_java_obj(java_obj, *args)
File "/u/nlp/anaconda/main/anaconda3/envs/stanza-1.2/lib/python3.7/site-packages/sparknlp/internal/extended_java_wrapper.py", line 37, in new_java_obj
return self._new_java_obj(java_class, *args)
File "/u/nlp/anaconda/main/anaconda3/envs/stanza-1.2/lib/python3.7/site-packages/pyspark/ml/wrapper.py", line 86, in _new_java_obj
return java_obj(*java_args)
TypeError: 'JavaPackage' object is not callable
>>>
```
This is on python 3.7.9 from the command line | 1.0 | Quickstart guide is for an older version - ### Link to the documentation pages (if available)
https://github.com/JohnSnowLabs/spark-nlp/blob/master/examples/python/quick_start.ipynb
### How could the documentation be improved?
When I run the initial suggestion, it throws an exception:
```
import sparknlp
spark = sparknlp.start()
print("Spark NLP version: ", sparknlp.version())
print("Apache Spark version: ", spark.version)
```
I get the following version number:
```
Spark NLP version: 4.4.3
Apache Spark version: 3.4.0
```
I get the following error when trying to run the basic initialization:
```
>>> pipeline = PretrainedPipeline('recognize_entities_dl', 'en')
recognize_entities_dl download started this may take some time.
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/u/nlp/anaconda/main/anaconda3/envs/stanza-1.2/lib/python3.7/site-packages/sparknlp/pretrained/pretrained_pipeline.py", line 54, in __init__
self.model = ResourceDownloader().downloadPipeline(name, lang, remote_loc)
File "/u/nlp/anaconda/main/anaconda3/envs/stanza-1.2/lib/python3.7/site-packages/sparknlp/pretrained/resource_downloader.py", line 142, in downloadPipeline
file_size = _internal._GetResourceSize(name, language, remote_loc).apply()
File "/u/nlp/anaconda/main/anaconda3/envs/stanza-1.2/lib/python3.7/site-packages/sparknlp/internal/__init__.py", line 380, in __init__
"com.johnsnowlabs.nlp.pretrained.PythonResourceDownloader.getDownloadSize", name, language, remote_loc)
File "/u/nlp/anaconda/main/anaconda3/envs/stanza-1.2/lib/python3.7/site-packages/sparknlp/internal/extended_java_wrapper.py", line 27, in __init__
self._java_obj = self.new_java_obj(java_obj, *args)
File "/u/nlp/anaconda/main/anaconda3/envs/stanza-1.2/lib/python3.7/site-packages/sparknlp/internal/extended_java_wrapper.py", line 37, in new_java_obj
return self._new_java_obj(java_class, *args)
File "/u/nlp/anaconda/main/anaconda3/envs/stanza-1.2/lib/python3.7/site-packages/pyspark/ml/wrapper.py", line 86, in _new_java_obj
return java_obj(*java_args)
TypeError: 'JavaPackage' object is not callable
>>>
```
This is on python 3.7.9 from the command line | non_priority | quickstart guide is for an older version link to the documentation pages if available how could the documentation be improved when i run the initial suggestion it throws an exception import sparknlp spark sparknlp start print spark nlp version sparknlp version print apache spark version spark version i get the following version number spark nlp version apache spark version i get the following error when trying to run the basic initialization pipeline pretrainedpipeline recognize entities dl en recognize entities dl download started this may take some time traceback most recent call last file line in file u nlp anaconda main envs stanza lib site packages sparknlp pretrained pretrained pipeline py line in init self model resourcedownloader downloadpipeline name lang remote loc file u nlp anaconda main envs stanza lib site packages sparknlp pretrained resource downloader py line in downloadpipeline file size internal getresourcesize name language remote loc apply file u nlp anaconda main envs stanza lib site packages sparknlp internal init py line in init com johnsnowlabs nlp pretrained pythonresourcedownloader getdownloadsize name language remote loc file u nlp anaconda main envs stanza lib site packages sparknlp internal extended java wrapper py line in init self java obj self new java obj java obj args file u nlp anaconda main envs stanza lib site packages sparknlp internal extended java wrapper py line in new java obj return self new java obj java class args file u nlp anaconda main envs stanza lib site packages pyspark ml wrapper py line in new java obj return java obj java args typeerror javapackage object is not callable this is on python from the command line | 0 |
25,838 | 12,304,641,705 | IssuesEvent | 2020-05-11 20:51:18 | Azure/azure-sdk-for-js | https://api.github.com/repos/Azure/azure-sdk-for-js | closed | [Service Bus] Peeking into an empty session-enabled queue throws an error | Client Service Bus | Peeking into an empty session-enabled queue would run into either of the following errors..
1. OperationTimeoutError: Unable to create the amqp receiver 'unpartitioned-queue-sessions-794f89be-3282-8b48-8ae0-a8af43c3ce36' on amqp session 'local-1_remote-1_connection-2' due to operation timeout.
2. MessagingError: Received an incorrect sessionId 'undefined' while creating the receiver 'unpartitioned-queue-sessions-86662b2b-acdc-1045-8ad4-fa3ab8807871'.
Not completely sure if this is due to opening multiple connections or multiple receivers (might be a drawback of the 2-client API). Need to revisit and investigate once the API with Top-level client is finalized and implemented.
https://dev.azure.com/azure-sdk/internal/_build/results?buildId=281562&view=logs&j=a556eced-ff92-56f9-81ae-670d7020e9e7&t=19299f15-c0e5-5217-5db1-bd33a9df4882
Commit to repro - 98563ca33c640fe3e93500da2bbf105373ae0cc0 | 1.0 | [Service Bus] Peeking into an empty session-enabled queue throws an error - Peeking into an empty session-enabled queue would run into either of the following errors..
1. OperationTimeoutError: Unable to create the amqp receiver 'unpartitioned-queue-sessions-794f89be-3282-8b48-8ae0-a8af43c3ce36' on amqp session 'local-1_remote-1_connection-2' due to operation timeout.
2. MessagingError: Received an incorrect sessionId 'undefined' while creating the receiver 'unpartitioned-queue-sessions-86662b2b-acdc-1045-8ad4-fa3ab8807871'.
Not completely sure if this is due to opening multiple connections or multiple receivers (might be a drawback of the 2-client API). Need to revisit and investigate once the API with Top-level client is finalized and implemented.
https://dev.azure.com/azure-sdk/internal/_build/results?buildId=281562&view=logs&j=a556eced-ff92-56f9-81ae-670d7020e9e7&t=19299f15-c0e5-5217-5db1-bd33a9df4882
Commit to repro - 98563ca33c640fe3e93500da2bbf105373ae0cc0 | non_priority | peeking into an empty session enabled queue throws an error peeking into an empty session enabled queue would run into either of the following errors operationtimeouterror unable to create the amqp receiver unpartitioned queue sessions on amqp session local remote connection due to operation timeout messagingerror received an incorrect sessionid undefined while creating the receiver unpartitioned queue sessions acdc not completely sure if this is due to opening multiple connections or multiple receivers might be a drawback of the client api need to revisit and investigate once the api with top level client is finalized and implemented commit to repro | 0 |
126,538 | 17,070,770,196 | IssuesEvent | 2021-07-07 13:05:40 | nushell/nushell | https://api.github.com/repos/nushell/nushell | closed | Add 'explore' functionality | Stale delight enhancement needs-design | We have (or possibly had, past-tense) an `enter` command that allows you to cd/ls your way around the inside of an object. This is pretty cool functionality, but it needs a better home than something that mimics the open command.
It may make sense as a sink:
```
open Cargo.toml | explore
```
Where you are put into an interactive mode (possibly with curses-style abilities as well). Putting this issue here as a reminder to revisit functionality that's interesting but hasn't yet found the right home. | 1.0 | Add 'explore' functionality - We have (or possibly had, past-tense) an `enter` command that allows you to cd/ls your way around the inside of an object. This is pretty cool functionality, but it needs a better home than something that mimics the open command.
It may make sense as a sink:
```
open Cargo.toml | explore
```
Where you are put into an interactive mode (possibly with curses-style abilities as well). Putting this issue here as a reminder to revisit functionality that's interesting but hasn't yet found the right home. | non_priority | add explore functionality we have or possibly had past tense an enter command that allows you to cd ls your way around the inside of an object this is pretty cool functionality but it needs a better home than something that mimics the open command it may make sense as a sink open cargo toml explore where you are put into an interactive mode possibly with curses style abilities as well putting this issue here as a reminder to revisit functionality that s interesting but hasn t yet found the right home | 0 |
191,304 | 22,215,740,561 | IssuesEvent | 2022-06-08 01:18:49 | rlennon/whitesource_bolt_demo | https://api.github.com/repos/rlennon/whitesource_bolt_demo | opened | CVE-2021-43307 (Medium) detected in semver-regex-2.0.0.tgz | security vulnerability | ## CVE-2021-43307 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>semver-regex-2.0.0.tgz</b></p></summary>
<p>Regular expression for matching semver versions</p>
<p>Library home page: <a href="https://registry.npmjs.org/semver-regex/-/semver-regex-2.0.0.tgz">https://registry.npmjs.org/semver-regex/-/semver-regex-2.0.0.tgz</a></p>
<p>Path to dependency file: /portainer-develop/portainer-develop/package.json</p>
<p>Path to vulnerable library: /portainer-develop/portainer-develop/node_modules/semver-regex/package.json</p>
<p>
Dependency Hierarchy:
- husky-4.2.5.tgz (Root Library)
- find-versions-3.2.0.tgz
- :x: **semver-regex-2.0.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/rlennon/whitesource_bolt_demo/commit/ec9d972edb7fb1ea028782bd0f770272d89e0c60">ec9d972edb7fb1ea028782bd0f770272d89e0c60</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
An exponential ReDoS (Regular Expression Denial of Service) can be triggered in the semver-regex npm package, when an attacker is able to supply arbitrary input to the test() method
<p>Publish Date: 2022-06-02
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-43307>CVE-2021-43307</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.9</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://research.jfrog.com/vulnerabilities/semver-regex-redos-xray-211349/">https://research.jfrog.com/vulnerabilities/semver-regex-redos-xray-211349/</a></p>
<p>Release Date: 2021-11-03</p>
<p>Fix Resolution (semver-regex): 3.1.4</p>
<p>Direct dependency fix Resolution (husky): 4.3.7</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2021-43307 (Medium) detected in semver-regex-2.0.0.tgz - ## CVE-2021-43307 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>semver-regex-2.0.0.tgz</b></p></summary>
<p>Regular expression for matching semver versions</p>
<p>Library home page: <a href="https://registry.npmjs.org/semver-regex/-/semver-regex-2.0.0.tgz">https://registry.npmjs.org/semver-regex/-/semver-regex-2.0.0.tgz</a></p>
<p>Path to dependency file: /portainer-develop/portainer-develop/package.json</p>
<p>Path to vulnerable library: /portainer-develop/portainer-develop/node_modules/semver-regex/package.json</p>
<p>
Dependency Hierarchy:
- husky-4.2.5.tgz (Root Library)
- find-versions-3.2.0.tgz
- :x: **semver-regex-2.0.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/rlennon/whitesource_bolt_demo/commit/ec9d972edb7fb1ea028782bd0f770272d89e0c60">ec9d972edb7fb1ea028782bd0f770272d89e0c60</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
An exponential ReDoS (Regular Expression Denial of Service) can be triggered in the semver-regex npm package, when an attacker is able to supply arbitrary input to the test() method
<p>Publish Date: 2022-06-02
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-43307>CVE-2021-43307</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.9</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://research.jfrog.com/vulnerabilities/semver-regex-redos-xray-211349/">https://research.jfrog.com/vulnerabilities/semver-regex-redos-xray-211349/</a></p>
<p>Release Date: 2021-11-03</p>
<p>Fix Resolution (semver-regex): 3.1.4</p>
<p>Direct dependency fix Resolution (husky): 4.3.7</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve medium detected in semver regex tgz cve medium severity vulnerability vulnerable library semver regex tgz regular expression for matching semver versions library home page a href path to dependency file portainer develop portainer develop package json path to vulnerable library portainer develop portainer develop node modules semver regex package json dependency hierarchy husky tgz root library find versions tgz x semver regex tgz vulnerable library found in head commit a href found in base branch main vulnerability details an exponential redos regular expression denial of service can be triggered in the semver regex npm package when an attacker is able to supply arbitrary input to the test method publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution semver regex direct dependency fix resolution husky step up your open source security game with mend | 0 |
208,047 | 23,546,632,861 | IssuesEvent | 2022-08-21 07:55:58 | ghc-dev/Amber-Burgess | https://api.github.com/repos/ghc-dev/Amber-Burgess | closed | log4j-core-2.8.2.jar: 3 vulnerabilities (highest severity is: 10.0) - autoclosed | security vulnerability | <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>log4j-core-2.8.2.jar</b></p></summary>
<p>The Apache Log4j Implementation</p>
<p>Library home page: <a href="https://logging.apache.org/log4j/2.x/log4j-core/">https://logging.apache.org/log4j/2.x/log4j-core/</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /ository/org/apache/logging/log4j/log4j-core/2.8.2/log4j-core-2.8.2.jar</p>
<p>
<p>Found in HEAD commit: <a href="https://github.com/ghc-dev/Amber-Burgess/commit/02a1040e226c3bb0efcdef55d785cfd6485033b8">02a1040e226c3bb0efcdef55d785cfd6485033b8</a></p></details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | --- | --- |
| [CVE-2021-44228](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-44228) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 10.0 | log4j-core-2.8.2.jar | Direct | 2.12.2 | ✅ |
| [CVE-2021-45046](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-45046) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 9.0 | log4j-core-2.8.2.jar | Direct | 2.12.2 | ✅ |
| [CVE-2020-9488](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-9488) | <img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Low | 3.7 | log4j-core-2.8.2.jar | Direct | 2.12.2 | ✅ |
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-44228</summary>
### Vulnerable Library - <b>log4j-core-2.8.2.jar</b></p>
<p>The Apache Log4j Implementation</p>
<p>Library home page: <a href="https://logging.apache.org/log4j/2.x/log4j-core/">https://logging.apache.org/log4j/2.x/log4j-core/</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /ository/org/apache/logging/log4j/log4j-core/2.8.2/log4j-core-2.8.2.jar</p>
<p>
Dependency Hierarchy:
- :x: **log4j-core-2.8.2.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/ghc-dev/Amber-Burgess/commit/02a1040e226c3bb0efcdef55d785cfd6485033b8">02a1040e226c3bb0efcdef55d785cfd6485033b8</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Apache Log4j2 2.0-beta9 through 2.15.0 (excluding security releases 2.12.2, 2.12.3, and 2.3.1) JNDI features used in configuration, log messages, and parameters do not protect against attacker controlled LDAP and other JNDI related endpoints. An attacker who can control log messages or log message parameters can execute arbitrary code loaded from LDAP servers when message lookup substitution is enabled. From log4j 2.15.0, this behavior has been disabled by default. From version 2.16.0 (along with 2.12.2, 2.12.3, and 2.3.1), this functionality has been completely removed. Note that this vulnerability is specific to log4j-core and does not affect log4net, log4cxx, or other Apache Logging Services projects.
<p>Publish Date: 2021-12-10
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-44228>CVE-2021-44228</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>10.0</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://logging.apache.org/log4j/2.x/security.html">https://logging.apache.org/log4j/2.x/security.html</a></p>
<p>Release Date: 2021-12-10</p>
<p>Fix Resolution: 2.12.2</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-45046</summary>
### Vulnerable Library - <b>log4j-core-2.8.2.jar</b></p>
<p>The Apache Log4j Implementation</p>
<p>Library home page: <a href="https://logging.apache.org/log4j/2.x/log4j-core/">https://logging.apache.org/log4j/2.x/log4j-core/</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /ository/org/apache/logging/log4j/log4j-core/2.8.2/log4j-core-2.8.2.jar</p>
<p>
Dependency Hierarchy:
- :x: **log4j-core-2.8.2.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/ghc-dev/Amber-Burgess/commit/02a1040e226c3bb0efcdef55d785cfd6485033b8">02a1040e226c3bb0efcdef55d785cfd6485033b8</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
It was found that the fix to address CVE-2021-44228 in Apache Log4j 2.15.0 was incomplete in certain non-default configurations. This could allows attackers with control over Thread Context Map (MDC) input data when the logging configuration uses a non-default Pattern Layout with either a Context Lookup (for example, $${ctx:loginId}) or a Thread Context Map pattern (%X, %mdc, or %MDC) to craft malicious input data using a JNDI Lookup pattern resulting in an information leak and remote code execution in some environments and local code execution in all environments. Log4j 2.16.0 (Java 8) and 2.12.2 (Java 7) fix this issue by removing support for message lookup patterns and disabling JNDI functionality by default.
<p>Publish Date: 2021-12-14
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-45046>CVE-2021-45046</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>9.0</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://logging.apache.org/log4j/2.x/security.html">https://logging.apache.org/log4j/2.x/security.html</a></p>
<p>Release Date: 2021-12-14</p>
<p>Fix Resolution: 2.12.2</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> CVE-2020-9488</summary>
### Vulnerable Library - <b>log4j-core-2.8.2.jar</b></p>
<p>The Apache Log4j Implementation</p>
<p>Library home page: <a href="https://logging.apache.org/log4j/2.x/log4j-core/">https://logging.apache.org/log4j/2.x/log4j-core/</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /ository/org/apache/logging/log4j/log4j-core/2.8.2/log4j-core-2.8.2.jar</p>
<p>
Dependency Hierarchy:
- :x: **log4j-core-2.8.2.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/ghc-dev/Amber-Burgess/commit/02a1040e226c3bb0efcdef55d785cfd6485033b8">02a1040e226c3bb0efcdef55d785cfd6485033b8</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Improper validation of certificate with host mismatch in Apache Log4j SMTP appender. This could allow an SMTPS connection to be intercepted by a man-in-the-middle attack which could leak any log messages sent through that appender.
<p>Publish Date: 2020-04-27
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-9488>CVE-2020-9488</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>3.7</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://issues.apache.org/jira/browse/LOG4J2-2819">https://issues.apache.org/jira/browse/LOG4J2-2819</a></p>
<p>Release Date: 2020-04-27</p>
<p>Fix Resolution: 2.12.2</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details>
***
<p>:rescue_worker_helmet: Automatic Remediation is available for this issue.</p> | True | log4j-core-2.8.2.jar: 3 vulnerabilities (highest severity is: 10.0) - autoclosed - <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>log4j-core-2.8.2.jar</b></p></summary>
<p>The Apache Log4j Implementation</p>
<p>Library home page: <a href="https://logging.apache.org/log4j/2.x/log4j-core/">https://logging.apache.org/log4j/2.x/log4j-core/</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /ository/org/apache/logging/log4j/log4j-core/2.8.2/log4j-core-2.8.2.jar</p>
<p>
<p>Found in HEAD commit: <a href="https://github.com/ghc-dev/Amber-Burgess/commit/02a1040e226c3bb0efcdef55d785cfd6485033b8">02a1040e226c3bb0efcdef55d785cfd6485033b8</a></p></details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | --- | --- |
| [CVE-2021-44228](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-44228) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 10.0 | log4j-core-2.8.2.jar | Direct | 2.12.2 | ✅ |
| [CVE-2021-45046](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-45046) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 9.0 | log4j-core-2.8.2.jar | Direct | 2.12.2 | ✅ |
| [CVE-2020-9488](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-9488) | <img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Low | 3.7 | log4j-core-2.8.2.jar | Direct | 2.12.2 | ✅ |
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-44228</summary>
### Vulnerable Library - <b>log4j-core-2.8.2.jar</b></p>
<p>The Apache Log4j Implementation</p>
<p>Library home page: <a href="https://logging.apache.org/log4j/2.x/log4j-core/">https://logging.apache.org/log4j/2.x/log4j-core/</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /ository/org/apache/logging/log4j/log4j-core/2.8.2/log4j-core-2.8.2.jar</p>
<p>
Dependency Hierarchy:
- :x: **log4j-core-2.8.2.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/ghc-dev/Amber-Burgess/commit/02a1040e226c3bb0efcdef55d785cfd6485033b8">02a1040e226c3bb0efcdef55d785cfd6485033b8</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Apache Log4j2 2.0-beta9 through 2.15.0 (excluding security releases 2.12.2, 2.12.3, and 2.3.1) JNDI features used in configuration, log messages, and parameters do not protect against attacker controlled LDAP and other JNDI related endpoints. An attacker who can control log messages or log message parameters can execute arbitrary code loaded from LDAP servers when message lookup substitution is enabled. From log4j 2.15.0, this behavior has been disabled by default. From version 2.16.0 (along with 2.12.2, 2.12.3, and 2.3.1), this functionality has been completely removed. Note that this vulnerability is specific to log4j-core and does not affect log4net, log4cxx, or other Apache Logging Services projects.
<p>Publish Date: 2021-12-10
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-44228>CVE-2021-44228</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>10.0</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://logging.apache.org/log4j/2.x/security.html">https://logging.apache.org/log4j/2.x/security.html</a></p>
<p>Release Date: 2021-12-10</p>
<p>Fix Resolution: 2.12.2</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-45046</summary>
### Vulnerable Library - <b>log4j-core-2.8.2.jar</b></p>
<p>The Apache Log4j Implementation</p>
<p>Library home page: <a href="https://logging.apache.org/log4j/2.x/log4j-core/">https://logging.apache.org/log4j/2.x/log4j-core/</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /ository/org/apache/logging/log4j/log4j-core/2.8.2/log4j-core-2.8.2.jar</p>
<p>
Dependency Hierarchy:
- :x: **log4j-core-2.8.2.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/ghc-dev/Amber-Burgess/commit/02a1040e226c3bb0efcdef55d785cfd6485033b8">02a1040e226c3bb0efcdef55d785cfd6485033b8</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
It was found that the fix to address CVE-2021-44228 in Apache Log4j 2.15.0 was incomplete in certain non-default configurations. This could allows attackers with control over Thread Context Map (MDC) input data when the logging configuration uses a non-default Pattern Layout with either a Context Lookup (for example, $${ctx:loginId}) or a Thread Context Map pattern (%X, %mdc, or %MDC) to craft malicious input data using a JNDI Lookup pattern resulting in an information leak and remote code execution in some environments and local code execution in all environments. Log4j 2.16.0 (Java 8) and 2.12.2 (Java 7) fix this issue by removing support for message lookup patterns and disabling JNDI functionality by default.
<p>Publish Date: 2021-12-14
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-45046>CVE-2021-45046</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>9.0</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://logging.apache.org/log4j/2.x/security.html">https://logging.apache.org/log4j/2.x/security.html</a></p>
<p>Release Date: 2021-12-14</p>
<p>Fix Resolution: 2.12.2</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> CVE-2020-9488</summary>
### Vulnerable Library - <b>log4j-core-2.8.2.jar</b></p>
<p>The Apache Log4j Implementation</p>
<p>Library home page: <a href="https://logging.apache.org/log4j/2.x/log4j-core/">https://logging.apache.org/log4j/2.x/log4j-core/</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /ository/org/apache/logging/log4j/log4j-core/2.8.2/log4j-core-2.8.2.jar</p>
<p>
Dependency Hierarchy:
- :x: **log4j-core-2.8.2.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/ghc-dev/Amber-Burgess/commit/02a1040e226c3bb0efcdef55d785cfd6485033b8">02a1040e226c3bb0efcdef55d785cfd6485033b8</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Improper validation of certificate with host mismatch in Apache Log4j SMTP appender. This could allow an SMTPS connection to be intercepted by a man-in-the-middle attack which could leak any log messages sent through that appender.
<p>Publish Date: 2020-04-27
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-9488>CVE-2020-9488</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>3.7</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://issues.apache.org/jira/browse/LOG4J2-2819">https://issues.apache.org/jira/browse/LOG4J2-2819</a></p>
<p>Release Date: 2020-04-27</p>
<p>Fix Resolution: 2.12.2</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details>
***
<p>:rescue_worker_helmet: Automatic Remediation is available for this issue.</p> | non_priority | core jar vulnerabilities highest severity is autoclosed vulnerable library core jar the apache implementation library home page a href path to dependency file pom xml path to vulnerable library ository org apache logging core core jar found in head commit a href vulnerabilities cve severity cvss dependency type fixed in remediation available high core jar direct high core jar direct low core jar direct details cve vulnerable library core jar the apache implementation library home page a href path to dependency file pom xml path to vulnerable library ository org apache logging core core jar dependency hierarchy x core jar vulnerable library found in head commit a href found in base branch main vulnerability details apache through excluding security releases and jndi features used in configuration log messages and parameters do not protect against attacker controlled ldap and other jndi related endpoints an attacker who can control log messages or log message parameters can execute arbitrary code loaded from ldap servers when message lookup substitution is enabled from this behavior has been disabled by default from version along with and this functionality has been completely removed note that this vulnerability is specific to core and does not affect or other apache logging services projects publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope changed impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution rescue worker helmet automatic remediation is available for this issue cve vulnerable library core jar the apache implementation library home page a href path to dependency file pom xml path to vulnerable library ository org apache logging core core jar dependency hierarchy x core jar vulnerable library found in head commit a href found in base branch main vulnerability details it was found that the fix to address cve in apache was incomplete in certain non default configurations this could allows attackers with control over thread context map mdc input data when the logging configuration uses a non default pattern layout with either a context lookup for example ctx loginid or a thread context map pattern x mdc or mdc to craft malicious input data using a jndi lookup pattern resulting in an information leak and remote code execution in some environments and local code execution in all environments java and java fix this issue by removing support for message lookup patterns and disabling jndi functionality by default publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required none user interaction none scope changed impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution rescue worker helmet automatic remediation is available for this issue cve vulnerable library core jar the apache implementation library home page a href path to dependency file pom xml path to vulnerable library ository org apache logging core core jar dependency hierarchy x core jar vulnerable library found in head commit a href found in base branch main vulnerability details improper validation of certificate with host mismatch in apache smtp appender this could allow an smtps connection to be intercepted by a man in the middle attack which could leak any log messages sent through that appender publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required none user interaction none scope unchanged impact metrics confidentiality impact low integrity impact none availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution rescue worker helmet automatic remediation is available for this issue rescue worker helmet automatic remediation is available for this issue | 0 |
24,655 | 6,557,939,341 | IssuesEvent | 2017-09-06 19:21:52 | CUAHSI/HydroCatalog | https://api.github.com/repos/CUAHSI/HydroCatalog | opened | Title overprint on service description page | CodePlex | <b>twhitvine[CodePlex]</b> <br />Long service titles are overprint on the service description page. See
See
http://hiscentral.cuahsi.org/pub_network.aspx?n=272
Screenshot from Firefox 15.0.1 attached. Same in Chrome.
| 1.0 | Title overprint on service description page - <b>twhitvine[CodePlex]</b> <br />Long service titles are overprint on the service description page. See
See
http://hiscentral.cuahsi.org/pub_network.aspx?n=272
Screenshot from Firefox 15.0.1 attached. Same in Chrome.
| non_priority | title overprint on service description page twhitvine long service titles are overprint on the service description page see see screenshot from firefox attached same in chrome | 0 |
254,933 | 27,448,451,348 | IssuesEvent | 2023-03-02 15:45:27 | elastic/integrations | https://api.github.com/repos/elastic/integrations | reopened | [Cloud Security] [Vulnerability Management] Add mappings for CloudFormation templates | Team:Cloud Security 8.8 candidate | ### Motivation
As part of the vulnerability management architecture, we are going to introduce a new elastic-agent deployment method, a CloudFormation template that provisions an EC2 instance with an elastic-agent installed.
The template will reside in an S3 bucket, and this task it's about defining a strategy to map the s3 bucket and implement a function in Kibana that retrieves an s3 URL to the current CloudFormation template for vulnerability management.
### Suggestion
Example of how templates will be stored in the s3 bucket (`cspm-cloudformation-templates`):
```
.
|-- cspm-cloudformation-templates
|-- vuln-mgmt/
|-- template-1.0.0.yaml
|-- template-1.0.1.yaml
```
In Kibana, each version branch will have a hard-coded mapping that points to the exact template version it needs to deploy for every feature.
For example, Kibana version branch 8.8 will hold the following map:
```
vuln_mgmt: 1.0.0
```
And as the template gets updated, the main branch will hold a similar mapping pointing to the new version:
```
vuln_mgmt: 1.0.1
```
Pros:
Easier development process as you can have a manual e2e test before you update Kibana to use the latest template.
Also, it will decouple our templates from the stack version. The benefit here is the ability to have a different template version for Kibana patch/snapshot/BC versions. Which makes it more aligned with the release process of elastic products.
Cons:
It requires us to manually open a PR to kibana for every update to the Cloudformation template in order to edit the version number Kibana points to.
### Definition of Done
- A function retrieving the current s3 URL for the vulnerability CloudFormation is created.
- A mapping for CloudFormation templates is created.
### Tasks
- Research what the s3 URL base will be
- Create a mapping for the CloudFormation templates containing vuln-mgmt
- Create a function to get the CloudFormation template for vulnerability management.
### Related
- https://github.com/elastic/security-team/issues/5700
- https://github.com/elastic/sre/issues/1480 | True | [Cloud Security] [Vulnerability Management] Add mappings for CloudFormation templates - ### Motivation
As part of the vulnerability management architecture, we are going to introduce a new elastic-agent deployment method, a CloudFormation template that provisions an EC2 instance with an elastic-agent installed.
The template will reside in an S3 bucket, and this task it's about defining a strategy to map the s3 bucket and implement a function in Kibana that retrieves an s3 URL to the current CloudFormation template for vulnerability management.
### Suggestion
Example of how templates will be stored in the s3 bucket (`cspm-cloudformation-templates`):
```
.
|-- cspm-cloudformation-templates
|-- vuln-mgmt/
|-- template-1.0.0.yaml
|-- template-1.0.1.yaml
```
In Kibana, each version branch will have a hard-coded mapping that points to the exact template version it needs to deploy for every feature.
For example, Kibana version branch 8.8 will hold the following map:
```
vuln_mgmt: 1.0.0
```
And as the template gets updated, the main branch will hold a similar mapping pointing to the new version:
```
vuln_mgmt: 1.0.1
```
Pros:
Easier development process as you can have a manual e2e test before you update Kibana to use the latest template.
Also, it will decouple our templates from the stack version. The benefit here is the ability to have a different template version for Kibana patch/snapshot/BC versions. Which makes it more aligned with the release process of elastic products.
Cons:
It requires us to manually open a PR to kibana for every update to the Cloudformation template in order to edit the version number Kibana points to.
### Definition of Done
- A function retrieving the current s3 URL for the vulnerability CloudFormation is created.
- A mapping for CloudFormation templates is created.
### Tasks
- Research what the s3 URL base will be
- Create a mapping for the CloudFormation templates containing vuln-mgmt
- Create a function to get the CloudFormation template for vulnerability management.
### Related
- https://github.com/elastic/security-team/issues/5700
- https://github.com/elastic/sre/issues/1480 | non_priority | add mappings for cloudformation templates motivation as part of the vulnerability management architecture we are going to introduce a new elastic agent deployment method a cloudformation template that provisions an instance with an elastic agent installed the template will reside in an bucket and this task it s about defining a strategy to map the bucket and implement a function in kibana that retrieves an url to the current cloudformation template for vulnerability management suggestion example of how templates will be stored in the bucket cspm cloudformation templates cspm cloudformation templates vuln mgmt template yaml template yaml in kibana each version branch will have a hard coded mapping that points to the exact template version it needs to deploy for every feature for example kibana version branch will hold the following map vuln mgmt and as the template gets updated the main branch will hold a similar mapping pointing to the new version vuln mgmt pros easier development process as you can have a manual test before you update kibana to use the latest template also it will decouple our templates from the stack version the benefit here is the ability to have a different template version for kibana patch snapshot bc versions which makes it more aligned with the release process of elastic products cons it requires us to manually open a pr to kibana for every update to the cloudformation template in order to edit the version number kibana points to definition of done a function retrieving the current url for the vulnerability cloudformation is created a mapping for cloudformation templates is created tasks research what the url base will be create a mapping for the cloudformation templates containing vuln mgmt create a function to get the cloudformation template for vulnerability management related | 0 |
154,711 | 12,226,100,608 | IssuesEvent | 2020-05-03 09:14:44 | GTNewHorizons/GT-New-Horizons-Modpack | https://api.github.com/repos/GTNewHorizons/GT-New-Horizons-Modpack | closed | Tesla's Last Testament casings name displayed wrong | FixedInDev GT++ need to be tested | #### Which modpack version are you using?
2.0.8.3
#
#### What happened?
Casings name in the tooltip are displayed improperly
#
#### What do you suggest instead/what changes do you propose?
Fix naming in mod files to be displayed properly | 1.0 | Tesla's Last Testament casings name displayed wrong - #### Which modpack version are you using?
2.0.8.3
#
#### What happened?
Casings name in the tooltip are displayed improperly
#
#### What do you suggest instead/what changes do you propose?
Fix naming in mod files to be displayed properly | non_priority | tesla s last testament casings name displayed wrong which modpack version are you using what happened casings name in the tooltip are displayed improperly what do you suggest instead what changes do you propose fix naming in mod files to be displayed properly | 0 |
68,636 | 21,773,226,244 | IssuesEvent | 2022-05-13 11:13:28 | vector-im/element-web | https://api.github.com/repos/vector-im/element-web | closed | can't build on Slackware GNU/Linux: builds for Debian! | T-Defect X-Needs-Info | ### Steps to reproduce
yarn install
yarn run fetch --importkey
yarn run fetch --cfgdir ""
yarn run build
### Outcome
#### What did you expect?
SlackBuild a txz.
#### What happened instead?
d@cosmos:~/math/src/network/chat/element-desktop-1.10.12$ yarn install
yarn run fetch --importkey
yarn run fetch --cfgdir ""
yarn run build
yarn install v1.22.10
[1/4] Resolving packages...
[2/4] Fetching packages...
info fsevents@2.3.2: The platform "linux" is incompatible with this module.
info "fsevents@2.3.2" is an optional dependency and failed compatibility check. Excluding it from installation.
info dmg-license@1.0.11: The platform "linux" is incompatible with this module.
info "dmg-license@1.0.11" is an optional dependency and failed compatibility check. Excluding it from installation.
info iconv-corefoundation@1.1.7: The platform "linux" is incompatible with this module.
info "iconv-corefoundation@1.1.7" is an optional dependency and failed compatibility check. Excluding it from installation.
[3/4] Linking dependencies...
warning " > eslint-plugin-matrix-org@0.4.0" has unmet peer dependency "eslint-plugin-jsx-a11y@^6.5.1".
warning " > ts-node@10.7.0" has unmet peer dependency "@types/node@*".
[4/4] Building fresh packages...
yarn run v1.22.10
$ yarn run mkdirs && node scripts/fetch-package.js --importkey
$ mkdirp packages deploys
Key imported!
yarn run v1.22.10
$ yarn run mkdirs && node scripts/fetch-package.js --cfgdir ''
$ mkdirp packages deploys
Downloading https://github.com/vector-im/element-web/releases/download/v1.10.12/element-v1.10.12.tar.gz...
Downloading https://github.com/vector-im/element-web/releases/download/v1.10.12/element-v1.10.12.tar.gz.asc...
packages/element-v1.10.12.tar.gz downloaded and verified
Skipping config file
Pack deploys/element-v1.10.12 -> webapp.asar
Done!
yarn run v1.22.10
$ yarn run build:ts && yarn run build:res && electron-builder
$ tsc
$ node scripts/copy-res.js
• electron-builder version=22.11.4 os=5.17.6
• loaded configuration file=package.json ("build" field)
• writing effective config file=dist/builder-effective-config.yaml
• packaging platform=linux arch=x64 electron=17.4.0 appOutDir=dist/linux-unpacked
• building target=deb arch=x64 file=dist/element-desktop_1.10.12_amd64.deb
### Operating system
Slackware64 15.1-current
### Application version
element-desktop-1.10.12
### How did you install the app?
_No response_
### Homeserver
_No response_
### Will you send logs?
Yes | 1.0 | can't build on Slackware GNU/Linux: builds for Debian! - ### Steps to reproduce
yarn install
yarn run fetch --importkey
yarn run fetch --cfgdir ""
yarn run build
### Outcome
#### What did you expect?
SlackBuild a txz.
#### What happened instead?
d@cosmos:~/math/src/network/chat/element-desktop-1.10.12$ yarn install
yarn run fetch --importkey
yarn run fetch --cfgdir ""
yarn run build
yarn install v1.22.10
[1/4] Resolving packages...
[2/4] Fetching packages...
info fsevents@2.3.2: The platform "linux" is incompatible with this module.
info "fsevents@2.3.2" is an optional dependency and failed compatibility check. Excluding it from installation.
info dmg-license@1.0.11: The platform "linux" is incompatible with this module.
info "dmg-license@1.0.11" is an optional dependency and failed compatibility check. Excluding it from installation.
info iconv-corefoundation@1.1.7: The platform "linux" is incompatible with this module.
info "iconv-corefoundation@1.1.7" is an optional dependency and failed compatibility check. Excluding it from installation.
[3/4] Linking dependencies...
warning " > eslint-plugin-matrix-org@0.4.0" has unmet peer dependency "eslint-plugin-jsx-a11y@^6.5.1".
warning " > ts-node@10.7.0" has unmet peer dependency "@types/node@*".
[4/4] Building fresh packages...
yarn run v1.22.10
$ yarn run mkdirs && node scripts/fetch-package.js --importkey
$ mkdirp packages deploys
Key imported!
yarn run v1.22.10
$ yarn run mkdirs && node scripts/fetch-package.js --cfgdir ''
$ mkdirp packages deploys
Downloading https://github.com/vector-im/element-web/releases/download/v1.10.12/element-v1.10.12.tar.gz...
Downloading https://github.com/vector-im/element-web/releases/download/v1.10.12/element-v1.10.12.tar.gz.asc...
packages/element-v1.10.12.tar.gz downloaded and verified
Skipping config file
Pack deploys/element-v1.10.12 -> webapp.asar
Done!
yarn run v1.22.10
$ yarn run build:ts && yarn run build:res && electron-builder
$ tsc
$ node scripts/copy-res.js
• electron-builder version=22.11.4 os=5.17.6
• loaded configuration file=package.json ("build" field)
• writing effective config file=dist/builder-effective-config.yaml
• packaging platform=linux arch=x64 electron=17.4.0 appOutDir=dist/linux-unpacked
• building target=deb arch=x64 file=dist/element-desktop_1.10.12_amd64.deb
### Operating system
Slackware64 15.1-current
### Application version
element-desktop-1.10.12
### How did you install the app?
_No response_
### Homeserver
_No response_
### Will you send logs?
Yes | non_priority | can t build on slackware gnu linux builds for debian steps to reproduce yarn install yarn run fetch importkey yarn run fetch cfgdir yarn run build outcome what did you expect slackbuild a txz what happened instead d cosmos math src network chat element desktop yarn install yarn run fetch importkey yarn run fetch cfgdir yarn run build yarn install resolving packages fetching packages info fsevents the platform linux is incompatible with this module info fsevents is an optional dependency and failed compatibility check excluding it from installation info dmg license the platform linux is incompatible with this module info dmg license is an optional dependency and failed compatibility check excluding it from installation info iconv corefoundation the platform linux is incompatible with this module info iconv corefoundation is an optional dependency and failed compatibility check excluding it from installation linking dependencies warning eslint plugin matrix org has unmet peer dependency eslint plugin jsx warning ts node has unmet peer dependency types node building fresh packages yarn run yarn run mkdirs node scripts fetch package js importkey mkdirp packages deploys key imported yarn run yarn run mkdirs node scripts fetch package js cfgdir mkdirp packages deploys downloading downloading packages element tar gz downloaded and verified skipping config file pack deploys element webapp asar done yarn run yarn run build ts yarn run build res electron builder tsc node scripts copy res js • electron builder version os • loaded configuration file package json build field • writing effective config file dist builder effective config yaml • packaging platform linux arch electron appoutdir dist linux unpacked • building target deb arch file dist element desktop deb operating system current application version element desktop how did you install the app no response homeserver no response will you send logs yes | 0 |
95,626 | 12,026,555,626 | IssuesEvent | 2020-04-12 14:40:25 | erikstacy/Time-Keeper | https://api.github.com/repos/erikstacy/Time-Keeper | closed | Color in the top bar of the Main Screen cards | design | Get rid of the Icons on the bar of each card. Then take the color of the old Icon and make that the background color of the top bar of the card. | 1.0 | Color in the top bar of the Main Screen cards - Get rid of the Icons on the bar of each card. Then take the color of the old Icon and make that the background color of the top bar of the card. | non_priority | color in the top bar of the main screen cards get rid of the icons on the bar of each card then take the color of the old icon and make that the background color of the top bar of the card | 0 |
96,170 | 27,768,096,647 | IssuesEvent | 2023-03-16 12:50:25 | spack/spack | https://api.github.com/repos/spack/spack | opened | Installation issue: libx11 fails at configure stage with `error: spack/lib/spack/env/cpp defines unix with or without -undef. I don't know what to do.` | build-error | ### Steps to reproduce the issue
```console
$ $ spack spec -I libx11@1.7.0 %gcc@12.1.0
Input spec
--------------------------------
- libx11@1.7.0%gcc@12.1.0
Concretized
--------------------------------
- libx11@1.7.0%gcc@12.1.0 build_system=autotools arch=linux-ubuntu22.04-skylake
[+] ^inputproto@2.3.2%gcc@12.1.0 build_system=autotools arch=linux-ubuntu22.04-skylake
[+] ^kbproto@1.0.7%gcc@12.1.0 build_system=autotools arch=linux-ubuntu22.04-skylake
[+] ^libxcb@1.14%gcc@12.1.0 build_system=autotools arch=linux-ubuntu22.04-skylake
[+] ^libpthread-stubs@0.4%gcc@12.1.0 build_system=autotools arch=linux-ubuntu22.04-skylake
[+] ^libxau@1.0.8%gcc@12.1.0 build_system=autotools arch=linux-ubuntu22.04-skylake
[+] ^libxdmcp@1.1.2%gcc@12.1.0 build_system=autotools arch=linux-ubuntu22.04-skylake
[+] ^libbsd@0.11.7%gcc@12.1.0 build_system=autotools arch=linux-ubuntu22.04-skylake
[+] ^libmd@1.0.4%gcc@12.1.0 build_system=autotools arch=linux-ubuntu22.04-skylake
[+] ^xcb-proto@1.14.1%gcc@12.1.0 build_system=autotools arch=linux-ubuntu22.04-skylake
[+] ^perl@5.36.0%gcc@12.1.0+cpanm+open+shared+threads build_system=generic arch=linux-ubuntu22.04-skylake
[+] ^berkeley-db@18.1.40%gcc@12.1.0+cxx~docs+stl build_system=autotools patches=26090f4,b231fcc arch=linux-ubuntu22.04-skylake
[+] ^bzip2@1.0.8%gcc@12.1.0~debug~pic+shared build_system=generic arch=linux-ubuntu22.04-skylake
[+] ^diffutils@3.8%gcc@12.1.0 build_system=autotools arch=linux-ubuntu22.04-skylake
[+] ^libiconv@1.17%gcc@12.1.0 build_system=autotools libs=shared,static arch=linux-ubuntu22.04-skylake
[+] ^gdbm@1.23%gcc@12.1.0 build_system=autotools arch=linux-ubuntu22.04-skylake
[+] ^readline@8.2%gcc@12.1.0 build_system=autotools patches=bbf97f1 arch=linux-ubuntu22.04-skylake
[+] ^ncurses@6.4%gcc@12.1.0~symlinks+termlib abi=none build_system=autotools arch=linux-ubuntu22.04-skylake
[+] ^zlib@1.2.13%gcc@12.1.0+optimize+pic+shared build_system=makefile arch=linux-ubuntu22.04-skylake
[+] ^pkgconf@1.8.0%gcc@12.1.0 build_system=autotools arch=linux-ubuntu22.04-skylake
[+] ^util-macros@1.19.3%gcc@12.1.0 build_system=autotools arch=linux-ubuntu22.04-skylake
[+] ^xextproto@7.3.0%gcc@12.1.0 build_system=autotools arch=linux-ubuntu22.04-skylake
[+] ^xproto@7.0.31%gcc@12.1.0 build_system=autotools arch=linux-ubuntu22.04-skylake
[+] ^xtrans@1.3.5%gcc@12.1.0 build_system=autotools arch=linux-ubuntu22.04-skylake
...
```
### Error message
<details><summary>Error message</summary><pre>
==> Error: ProcessError: Command exited with status 1:
'/tmp/mivkov/spack-stage/spack-stage-libx11-1.7.0-m67dhw4zpdelmecnl5z5qfpbehxtclk6/spack-src/configure' '--prefix=/home/mivkov/local/spack/opt/spack/linux-ubuntu22.04-skylake/oneapi-2022.2.1/libx11-1.7.0-m67dhw4zpdelmecnl5z5qfpbehxtclk6'
1 error found in build log:
137 checking if /home/mivkov/local/spack/lib/spack/env/cpp requires -undef... cpp: fatal error: no input files
138 compilation terminated.
139 cpp: fatal error: no input files
140 compilation terminated.
141 cpp: fatal error: no input files
142 compilation terminated.
>> 143 configure: error: /home/mivkov/local/spack/lib/spack/env/cpp defines unix with or without -undef. I don't know what to do.
</pre></details>
### Information on your system
$ spack debug report
* **Spack:** 0.19.1 (14d1fa7c559fee5332e4aee4398b75daaff33466)
* **Python:** 3.10.6
* **Platform:** linux-ubuntu22.04-skylake
* **Concretizer:** clingo
modules.yaml
------------------------------
```
modules:
prefix_inspections:
lib:
- LD_LIBRARY_PATH
lib64:
- LD_LIBRARY_PATH
default:
enable:
- lmod
lmod:
hash_length: 0
hierarchy:
- 'mpi'
core_compilers:
- gcc@12.1.0
all:
environment:
set:
'{name}_ROOT': '{prefix}'
grackle:
suffixes:
^hdf5@1.12.2: 'hdf5@1.12.2'
^hdf5@1.13.1: 'hdf5@1.13.1'
grackle-float:
suffixes:
^hdf5@1.12.2: 'hdf5@1.12.2'
blacklist:
- ant
- autoconf
- autoconf-archive
- automake
- berkeley-db
- binutils
- bison
- boost
- bzip2
- cmake
- curl
- diffutils
- double-conversion
- eigen
- expat
- findutils
- flex
- freetype
- gdbm
- gettext
- git
- glproto
- gnutls
- gmp
- hwloc
- help2man
- inputproto
- isl
- jsoncpp
- kbproto
- libaec
- libarchive
- libbsd
- libedit
- libevent
- libfabric
- libffi
- libidn2
- libice
- libiconv
- libjpeg-turbo
- libmd
- libogg
- libpciaccess
- libpng
- libpthread-stubs
- libsigsegv
- libsm
- libszip
- libtheora
- libtool
- libunwind
- libuv
- libxau
- libxcb
- libxdmcp
- libxml2
- libunistring
- lmod
- lua-luafilesystem
- lua-luaposix
- lua
- lz4
- lzo
- m4
- mbedtls
- meson
- mpc
- mpfr
- nasm
- ncurses
- nettle
- ninja
- openjdk
- openssl
- openssh
- patchelf
- pcre
- pcre2
- perl
- perl-data-dumper
- pigz
- pkgconf
- pmix
- proj
- python
- py-mako
- py-markupsafe
- py-pip
- py-setuptools
- py-wheel
- randrproto
- readline
- re2c
- renderproto
- rhash
- sqlite
- tar
- tcl
- texinfo
- unzip
- util-linux-uuid
- util-macros
- xcb-proto
- xextproto
- xproto
- xtrans
- xz
- yaksa
- zlib
- zstd
```
packages.yaml
----------------------------
```
packages:
gettext:
externals:
- spec: gettext@0.21
prefix: /usr
buildable: false
all:
compiler: [gcc@12.1.0]
providers:
mpi: [openmpi, mpich]
fftw:
variants: ~mpi
git:
externals:
- spec: git@2.34.1
buildable: false
hdf5:
variants: +cxx+fortran+hl+szip+threadsafe
openmpi:
variants: +thread_multiple+debug
openssl:
externals:
- spec: openssl@3.0.2
prefix: /usr
buildable: false
python:
externals:
- spec: python@3.10.6
prefix: /usr
buildable: false
vtk:
variants: -mpi
automake:
externals:
- spec: automake@1.16.5
prefix: /usr
buildable: false
autoconf:
externals:
- spec: autoconf@2.71
prefix: /usr
buildable: false
cmake:
externals:
- spec: cmake@3.23.1
prefix: /usr
buildable: false
libtool:
externals:
- spec: libtool@2.4.6
prefix: /usr
buildable: false
m4:
externals:
- spec: m4@1.4.18
prefix: /usr
buildable: false
llvm:
externals:
- spec: llvm@14.0.0
prefix: /usr
buildable: false
```
compilers.yaml
-----------------------
compilers:
- compiler:
spec: clang@14.0.0
paths:
cc: /usr/bin/clang
cxx: /usr/bin/clang++
f77: null
fc: null
flags: {}
operating_system: ubuntu22.04
target: x86_64
modules: []
environment: {}
extra_rpaths: []
- compiler:
spec: gcc@11.3.0
paths:
cc: /usr/bin/gcc-11
cpp: /usr/bin/cpp-11
cxx: /usr/bin/g++-11
f77: /usr/bin/gfortran-11
fc: /usr/bin/gfortran-11
flags: {}
operating_system: ubuntu22.04
target: x86_64
modules: []
environment: {}
extra_rpaths: []
- compiler:
spec: gcc@12.1.0
paths:
cc: /usr/bin/gcc-12
cpp: /usr/bin/cpp-12
cxx: /usr/bin/g++-12
f77: /usr/bin/gfortran-12
fc: /usr/bin/gfortran-12
flags: {}
operating_system: ubuntu22.04
target: x86_64
modules: []
environment: {}
extra_rpaths: []
- compiler:
spec: dpcpp@2022.2.1
paths:
cc: /home/mivkov/local/spack/opt/spack/linux-ubuntu22.04-skylake/gcc-12.1.0/intel-oneapi-compilers-2022.2.1-malnhriz2vh3cbo6rk2mvncapu4kunwp/compiler/2022.2.1/linux/bin/icx
cxx: /home/mivkov/local/spack/opt/spack/linux-ubuntu22.04-skylake/gcc-12.1.0/intel-oneapi-compilers-2022.2.1-malnhriz2vh3cbo6rk2mvncapu4kunwp/compiler/2022.2.1/linux/bin/dpcpp
f77: /home/mivkov/local/spack/opt/spack/linux-ubuntu22.04-skylake/gcc-12.1.0/intel-oneapi-compilers-2022.2.1-malnhriz2vh3cbo6rk2mvncapu4kunwp/compiler/2022.2.1/linux/bin/ifx
fc: /home/mivkov/local/spack/opt/spack/linux-ubuntu22.04-skylake/gcc-12.1.0/intel-oneapi-compilers-2022.2.1-malnhriz2vh3cbo6rk2mvncapu4kunwp/compiler/2022.2.1/linux/bin/ifx
flags: {}
operating_system: ubuntu22.04
target: x86_64
modules: []
environment: {}
extra_rpaths: []
- compiler:
spec: intel@2021.7.1
paths:
cc: /home/mivkov/local/spack/opt/spack/linux-ubuntu22.04-skylake/gcc-12.1.0/intel-oneapi-compilers-2022.2.1-malnhriz2vh3cbo6rk2mvncapu4kunwp/compiler/2022.2.1/linux/bin/intel64/icc
cxx: /home/mivkov/local/spack/opt/spack/linux-ubuntu22.04-skylake/gcc-12.1.0/intel-oneapi-compilers-2022.2.1-malnhriz2vh3cbo6rk2mvncapu4kunwp/compiler/2022.2.1/linux/bin/intel64/icpc
f77: /home/mivkov/local/spack/opt/spack/linux-ubuntu22.04-skylake/gcc-12.1.0/intel-oneapi-compilers-2022.2.1-malnhriz2vh3cbo6rk2mvncapu4kunwp/compiler/2022.2.1/linux/bin/intel64/ifort
fc: /home/mivkov/local/spack/opt/spack/linux-ubuntu22.04-skylake/gcc-12.1.0/intel-oneapi-compilers-2022.2.1-malnhriz2vh3cbo6rk2mvncapu4kunwp/compiler/2022.2.1/linux/bin/intel64/ifort
flags: {}
operating_system: ubuntu22.04
target: x86_64
modules: []
environment: {}
extra_rpaths: []
- compiler:
spec: oneapi@2022.2.1
paths:
cc: /home/mivkov/local/spack/opt/spack/linux-ubuntu22.04-skylake/gcc-12.1.0/intel-oneapi-compilers-2022.2.1-malnhriz2vh3cbo6rk2mvncapu4kunwp/compiler/2022.2.1/linux/bin/icx
cxx: /home/mivkov/local/spack/opt/spack/linux-ubuntu22.04-skylake/gcc-12.1.0/intel-oneapi-compilers-2022.2.1-malnhriz2vh3cbo6rk2mvncapu4kunwp/compiler/2022.2.1/linux/bin/icpx
f77: /home/mivkov/local/spack/opt/spack/linux-ubuntu22.04-skylake/gcc-12.1.0/intel-oneapi-compilers-2022.2.1-malnhriz2vh3cbo6rk2mvncapu4kunwp/compiler/2022.2.1/linux/bin/ifx
fc: /home/mivkov/local/spack/opt/spack/linux-ubuntu22.04-skylake/gcc-12.1.0/intel-oneapi-compilers-2022.2.1-malnhriz2vh3cbo6rk2mvncapu4kunwp/compiler/2022.2.1/linux/bin/ifx
flags: {}
operating_system: ubuntu22.04
target: x86_64
modules: []
environment: {}
extra_rpaths: []
```
### Additional information
[spack-configure-args.txt](https://github.com/spack/spack/files/10990844/spack-configure-args.txt)
[spack-build-out.txt](https://github.com/spack/spack/files/10990846/spack-build-out.txt)
[spack-build-env-mods.txt](https://github.com/spack/spack/files/10990847/spack-build-env-mods.txt)
[spack-build-env.txt](https://github.com/spack/spack/files/10990848/spack-build-env.txt)
[spack-build-02-configure-out.txt](https://github.com/spack/spack/files/10990849/spack-build-02-configure-out.txt)
[spack-build-01-autoreconf-out.txt](https://github.com/spack/spack/files/10990850/spack-build-01-autoreconf-out.txt)
Additional Info
--------------------------
- This occurs when letting spack install autotools itself, as well as when I'm using my system's autotools (as is currently set up in my `packages.yaml` file)
- Happens as well when I try compiling using the `intel-oneapi-compilers/2022.2.1` compiler suite instead of my system's gcc@12.1.0
### General information
- [X] I have run `spack debug report` and reported the version of Spack/Python/Platform
- [X] I have run `spack maintainers <name-of-the-package>` and **@mentioned** any maintainers
- [X] I have uploaded the build log and environment files
- [X] I have searched the issues of this repo and believe this is not a duplicate | 1.0 | Installation issue: libx11 fails at configure stage with `error: spack/lib/spack/env/cpp defines unix with or without -undef. I don't know what to do.` - ### Steps to reproduce the issue
```console
$ $ spack spec -I libx11@1.7.0 %gcc@12.1.0
Input spec
--------------------------------
- libx11@1.7.0%gcc@12.1.0
Concretized
--------------------------------
- libx11@1.7.0%gcc@12.1.0 build_system=autotools arch=linux-ubuntu22.04-skylake
[+] ^inputproto@2.3.2%gcc@12.1.0 build_system=autotools arch=linux-ubuntu22.04-skylake
[+] ^kbproto@1.0.7%gcc@12.1.0 build_system=autotools arch=linux-ubuntu22.04-skylake
[+] ^libxcb@1.14%gcc@12.1.0 build_system=autotools arch=linux-ubuntu22.04-skylake
[+] ^libpthread-stubs@0.4%gcc@12.1.0 build_system=autotools arch=linux-ubuntu22.04-skylake
[+] ^libxau@1.0.8%gcc@12.1.0 build_system=autotools arch=linux-ubuntu22.04-skylake
[+] ^libxdmcp@1.1.2%gcc@12.1.0 build_system=autotools arch=linux-ubuntu22.04-skylake
[+] ^libbsd@0.11.7%gcc@12.1.0 build_system=autotools arch=linux-ubuntu22.04-skylake
[+] ^libmd@1.0.4%gcc@12.1.0 build_system=autotools arch=linux-ubuntu22.04-skylake
[+] ^xcb-proto@1.14.1%gcc@12.1.0 build_system=autotools arch=linux-ubuntu22.04-skylake
[+] ^perl@5.36.0%gcc@12.1.0+cpanm+open+shared+threads build_system=generic arch=linux-ubuntu22.04-skylake
[+] ^berkeley-db@18.1.40%gcc@12.1.0+cxx~docs+stl build_system=autotools patches=26090f4,b231fcc arch=linux-ubuntu22.04-skylake
[+] ^bzip2@1.0.8%gcc@12.1.0~debug~pic+shared build_system=generic arch=linux-ubuntu22.04-skylake
[+] ^diffutils@3.8%gcc@12.1.0 build_system=autotools arch=linux-ubuntu22.04-skylake
[+] ^libiconv@1.17%gcc@12.1.0 build_system=autotools libs=shared,static arch=linux-ubuntu22.04-skylake
[+] ^gdbm@1.23%gcc@12.1.0 build_system=autotools arch=linux-ubuntu22.04-skylake
[+] ^readline@8.2%gcc@12.1.0 build_system=autotools patches=bbf97f1 arch=linux-ubuntu22.04-skylake
[+] ^ncurses@6.4%gcc@12.1.0~symlinks+termlib abi=none build_system=autotools arch=linux-ubuntu22.04-skylake
[+] ^zlib@1.2.13%gcc@12.1.0+optimize+pic+shared build_system=makefile arch=linux-ubuntu22.04-skylake
[+] ^pkgconf@1.8.0%gcc@12.1.0 build_system=autotools arch=linux-ubuntu22.04-skylake
[+] ^util-macros@1.19.3%gcc@12.1.0 build_system=autotools arch=linux-ubuntu22.04-skylake
[+] ^xextproto@7.3.0%gcc@12.1.0 build_system=autotools arch=linux-ubuntu22.04-skylake
[+] ^xproto@7.0.31%gcc@12.1.0 build_system=autotools arch=linux-ubuntu22.04-skylake
[+] ^xtrans@1.3.5%gcc@12.1.0 build_system=autotools arch=linux-ubuntu22.04-skylake
...
```
### Error message
<details><summary>Error message</summary><pre>
==> Error: ProcessError: Command exited with status 1:
'/tmp/mivkov/spack-stage/spack-stage-libx11-1.7.0-m67dhw4zpdelmecnl5z5qfpbehxtclk6/spack-src/configure' '--prefix=/home/mivkov/local/spack/opt/spack/linux-ubuntu22.04-skylake/oneapi-2022.2.1/libx11-1.7.0-m67dhw4zpdelmecnl5z5qfpbehxtclk6'
1 error found in build log:
137 checking if /home/mivkov/local/spack/lib/spack/env/cpp requires -undef... cpp: fatal error: no input files
138 compilation terminated.
139 cpp: fatal error: no input files
140 compilation terminated.
141 cpp: fatal error: no input files
142 compilation terminated.
>> 143 configure: error: /home/mivkov/local/spack/lib/spack/env/cpp defines unix with or without -undef. I don't know what to do.
</pre></details>
### Information on your system
$ spack debug report
* **Spack:** 0.19.1 (14d1fa7c559fee5332e4aee4398b75daaff33466)
* **Python:** 3.10.6
* **Platform:** linux-ubuntu22.04-skylake
* **Concretizer:** clingo
modules.yaml
------------------------------
```
modules:
prefix_inspections:
lib:
- LD_LIBRARY_PATH
lib64:
- LD_LIBRARY_PATH
default:
enable:
- lmod
lmod:
hash_length: 0
hierarchy:
- 'mpi'
core_compilers:
- gcc@12.1.0
all:
environment:
set:
'{name}_ROOT': '{prefix}'
grackle:
suffixes:
^hdf5@1.12.2: 'hdf5@1.12.2'
^hdf5@1.13.1: 'hdf5@1.13.1'
grackle-float:
suffixes:
^hdf5@1.12.2: 'hdf5@1.12.2'
blacklist:
- ant
- autoconf
- autoconf-archive
- automake
- berkeley-db
- binutils
- bison
- boost
- bzip2
- cmake
- curl
- diffutils
- double-conversion
- eigen
- expat
- findutils
- flex
- freetype
- gdbm
- gettext
- git
- glproto
- gnutls
- gmp
- hwloc
- help2man
- inputproto
- isl
- jsoncpp
- kbproto
- libaec
- libarchive
- libbsd
- libedit
- libevent
- libfabric
- libffi
- libidn2
- libice
- libiconv
- libjpeg-turbo
- libmd
- libogg
- libpciaccess
- libpng
- libpthread-stubs
- libsigsegv
- libsm
- libszip
- libtheora
- libtool
- libunwind
- libuv
- libxau
- libxcb
- libxdmcp
- libxml2
- libunistring
- lmod
- lua-luafilesystem
- lua-luaposix
- lua
- lz4
- lzo
- m4
- mbedtls
- meson
- mpc
- mpfr
- nasm
- ncurses
- nettle
- ninja
- openjdk
- openssl
- openssh
- patchelf
- pcre
- pcre2
- perl
- perl-data-dumper
- pigz
- pkgconf
- pmix
- proj
- python
- py-mako
- py-markupsafe
- py-pip
- py-setuptools
- py-wheel
- randrproto
- readline
- re2c
- renderproto
- rhash
- sqlite
- tar
- tcl
- texinfo
- unzip
- util-linux-uuid
- util-macros
- xcb-proto
- xextproto
- xproto
- xtrans
- xz
- yaksa
- zlib
- zstd
```
packages.yaml
----------------------------
```
packages:
gettext:
externals:
- spec: gettext@0.21
prefix: /usr
buildable: false
all:
compiler: [gcc@12.1.0]
providers:
mpi: [openmpi, mpich]
fftw:
variants: ~mpi
git:
externals:
- spec: git@2.34.1
buildable: false
hdf5:
variants: +cxx+fortran+hl+szip+threadsafe
openmpi:
variants: +thread_multiple+debug
openssl:
externals:
- spec: openssl@3.0.2
prefix: /usr
buildable: false
python:
externals:
- spec: python@3.10.6
prefix: /usr
buildable: false
vtk:
variants: -mpi
automake:
externals:
- spec: automake@1.16.5
prefix: /usr
buildable: false
autoconf:
externals:
- spec: autoconf@2.71
prefix: /usr
buildable: false
cmake:
externals:
- spec: cmake@3.23.1
prefix: /usr
buildable: false
libtool:
externals:
- spec: libtool@2.4.6
prefix: /usr
buildable: false
m4:
externals:
- spec: m4@1.4.18
prefix: /usr
buildable: false
llvm:
externals:
- spec: llvm@14.0.0
prefix: /usr
buildable: false
```
compilers.yaml
-----------------------
compilers:
- compiler:
spec: clang@14.0.0
paths:
cc: /usr/bin/clang
cxx: /usr/bin/clang++
f77: null
fc: null
flags: {}
operating_system: ubuntu22.04
target: x86_64
modules: []
environment: {}
extra_rpaths: []
- compiler:
spec: gcc@11.3.0
paths:
cc: /usr/bin/gcc-11
cpp: /usr/bin/cpp-11
cxx: /usr/bin/g++-11
f77: /usr/bin/gfortran-11
fc: /usr/bin/gfortran-11
flags: {}
operating_system: ubuntu22.04
target: x86_64
modules: []
environment: {}
extra_rpaths: []
- compiler:
spec: gcc@12.1.0
paths:
cc: /usr/bin/gcc-12
cpp: /usr/bin/cpp-12
cxx: /usr/bin/g++-12
f77: /usr/bin/gfortran-12
fc: /usr/bin/gfortran-12
flags: {}
operating_system: ubuntu22.04
target: x86_64
modules: []
environment: {}
extra_rpaths: []
- compiler:
spec: dpcpp@2022.2.1
paths:
cc: /home/mivkov/local/spack/opt/spack/linux-ubuntu22.04-skylake/gcc-12.1.0/intel-oneapi-compilers-2022.2.1-malnhriz2vh3cbo6rk2mvncapu4kunwp/compiler/2022.2.1/linux/bin/icx
cxx: /home/mivkov/local/spack/opt/spack/linux-ubuntu22.04-skylake/gcc-12.1.0/intel-oneapi-compilers-2022.2.1-malnhriz2vh3cbo6rk2mvncapu4kunwp/compiler/2022.2.1/linux/bin/dpcpp
f77: /home/mivkov/local/spack/opt/spack/linux-ubuntu22.04-skylake/gcc-12.1.0/intel-oneapi-compilers-2022.2.1-malnhriz2vh3cbo6rk2mvncapu4kunwp/compiler/2022.2.1/linux/bin/ifx
fc: /home/mivkov/local/spack/opt/spack/linux-ubuntu22.04-skylake/gcc-12.1.0/intel-oneapi-compilers-2022.2.1-malnhriz2vh3cbo6rk2mvncapu4kunwp/compiler/2022.2.1/linux/bin/ifx
flags: {}
operating_system: ubuntu22.04
target: x86_64
modules: []
environment: {}
extra_rpaths: []
- compiler:
spec: intel@2021.7.1
paths:
cc: /home/mivkov/local/spack/opt/spack/linux-ubuntu22.04-skylake/gcc-12.1.0/intel-oneapi-compilers-2022.2.1-malnhriz2vh3cbo6rk2mvncapu4kunwp/compiler/2022.2.1/linux/bin/intel64/icc
cxx: /home/mivkov/local/spack/opt/spack/linux-ubuntu22.04-skylake/gcc-12.1.0/intel-oneapi-compilers-2022.2.1-malnhriz2vh3cbo6rk2mvncapu4kunwp/compiler/2022.2.1/linux/bin/intel64/icpc
f77: /home/mivkov/local/spack/opt/spack/linux-ubuntu22.04-skylake/gcc-12.1.0/intel-oneapi-compilers-2022.2.1-malnhriz2vh3cbo6rk2mvncapu4kunwp/compiler/2022.2.1/linux/bin/intel64/ifort
fc: /home/mivkov/local/spack/opt/spack/linux-ubuntu22.04-skylake/gcc-12.1.0/intel-oneapi-compilers-2022.2.1-malnhriz2vh3cbo6rk2mvncapu4kunwp/compiler/2022.2.1/linux/bin/intel64/ifort
flags: {}
operating_system: ubuntu22.04
target: x86_64
modules: []
environment: {}
extra_rpaths: []
- compiler:
spec: oneapi@2022.2.1
paths:
cc: /home/mivkov/local/spack/opt/spack/linux-ubuntu22.04-skylake/gcc-12.1.0/intel-oneapi-compilers-2022.2.1-malnhriz2vh3cbo6rk2mvncapu4kunwp/compiler/2022.2.1/linux/bin/icx
cxx: /home/mivkov/local/spack/opt/spack/linux-ubuntu22.04-skylake/gcc-12.1.0/intel-oneapi-compilers-2022.2.1-malnhriz2vh3cbo6rk2mvncapu4kunwp/compiler/2022.2.1/linux/bin/icpx
f77: /home/mivkov/local/spack/opt/spack/linux-ubuntu22.04-skylake/gcc-12.1.0/intel-oneapi-compilers-2022.2.1-malnhriz2vh3cbo6rk2mvncapu4kunwp/compiler/2022.2.1/linux/bin/ifx
fc: /home/mivkov/local/spack/opt/spack/linux-ubuntu22.04-skylake/gcc-12.1.0/intel-oneapi-compilers-2022.2.1-malnhriz2vh3cbo6rk2mvncapu4kunwp/compiler/2022.2.1/linux/bin/ifx
flags: {}
operating_system: ubuntu22.04
target: x86_64
modules: []
environment: {}
extra_rpaths: []
```
### Additional information
[spack-configure-args.txt](https://github.com/spack/spack/files/10990844/spack-configure-args.txt)
[spack-build-out.txt](https://github.com/spack/spack/files/10990846/spack-build-out.txt)
[spack-build-env-mods.txt](https://github.com/spack/spack/files/10990847/spack-build-env-mods.txt)
[spack-build-env.txt](https://github.com/spack/spack/files/10990848/spack-build-env.txt)
[spack-build-02-configure-out.txt](https://github.com/spack/spack/files/10990849/spack-build-02-configure-out.txt)
[spack-build-01-autoreconf-out.txt](https://github.com/spack/spack/files/10990850/spack-build-01-autoreconf-out.txt)
Additional Info
--------------------------
- This occurs when letting spack install autotools itself, as well as when I'm using my system's autotools (as is currently set up in my `packages.yaml` file)
- Happens as well when I try compiling using the `intel-oneapi-compilers/2022.2.1` compiler suite instead of my system's gcc@12.1.0
### General information
- [X] I have run `spack debug report` and reported the version of Spack/Python/Platform
- [X] I have run `spack maintainers <name-of-the-package>` and **@mentioned** any maintainers
- [X] I have uploaded the build log and environment files
- [X] I have searched the issues of this repo and believe this is not a duplicate | non_priority | installation issue fails at configure stage with error spack lib spack env cpp defines unix with or without undef i don t know what to do steps to reproduce the issue console spack spec i gcc input spec gcc concretized gcc build system autotools arch linux skylake inputproto gcc build system autotools arch linux skylake kbproto gcc build system autotools arch linux skylake libxcb gcc build system autotools arch linux skylake libpthread stubs gcc build system autotools arch linux skylake libxau gcc build system autotools arch linux skylake libxdmcp gcc build system autotools arch linux skylake libbsd gcc build system autotools arch linux skylake libmd gcc build system autotools arch linux skylake xcb proto gcc build system autotools arch linux skylake perl gcc cpanm open shared threads build system generic arch linux skylake berkeley db gcc cxx docs stl build system autotools patches arch linux skylake gcc debug pic shared build system generic arch linux skylake diffutils gcc build system autotools arch linux skylake libiconv gcc build system autotools libs shared static arch linux skylake gdbm gcc build system autotools arch linux skylake readline gcc build system autotools patches arch linux skylake ncurses gcc symlinks termlib abi none build system autotools arch linux skylake zlib gcc optimize pic shared build system makefile arch linux skylake pkgconf gcc build system autotools arch linux skylake util macros gcc build system autotools arch linux skylake xextproto gcc build system autotools arch linux skylake xproto gcc build system autotools arch linux skylake xtrans gcc build system autotools arch linux skylake error message error message error processerror command exited with status tmp mivkov spack stage spack stage spack src configure prefix home mivkov local spack opt spack linux skylake oneapi error found in build log checking if home mivkov local spack lib spack env cpp requires undef cpp fatal error no input files compilation terminated cpp fatal error no input files compilation terminated cpp fatal error no input files compilation terminated configure error home mivkov local spack lib spack env cpp defines unix with or without undef i don t know what to do information on your system spack debug report spack python platform linux skylake concretizer clingo modules yaml modules prefix inspections lib ld library path ld library path default enable lmod lmod hash length hierarchy mpi core compilers gcc all environment set name root prefix grackle suffixes grackle float suffixes blacklist ant autoconf autoconf archive automake berkeley db binutils bison boost cmake curl diffutils double conversion eigen expat findutils flex freetype gdbm gettext git glproto gnutls gmp hwloc inputproto isl jsoncpp kbproto libaec libarchive libbsd libedit libevent libfabric libffi libice libiconv libjpeg turbo libmd libogg libpciaccess libpng libpthread stubs libsigsegv libsm libszip libtheora libtool libunwind libuv libxau libxcb libxdmcp libunistring lmod lua luafilesystem lua luaposix lua lzo mbedtls meson mpc mpfr nasm ncurses nettle ninja openjdk openssl openssh patchelf pcre perl perl data dumper pigz pkgconf pmix proj python py mako py markupsafe py pip py setuptools py wheel randrproto readline renderproto rhash sqlite tar tcl texinfo unzip util linux uuid util macros xcb proto xextproto xproto xtrans xz yaksa zlib zstd packages yaml packages gettext externals spec gettext prefix usr buildable false all compiler providers mpi fftw variants mpi git externals spec git buildable false variants cxx fortran hl szip threadsafe openmpi variants thread multiple debug openssl externals spec openssl prefix usr buildable false python externals spec python prefix usr buildable false vtk variants mpi automake externals spec automake prefix usr buildable false autoconf externals spec autoconf prefix usr buildable false cmake externals spec cmake prefix usr buildable false libtool externals spec libtool prefix usr buildable false externals spec prefix usr buildable false llvm externals spec llvm prefix usr buildable false compilers yaml compilers compiler spec clang paths cc usr bin clang cxx usr bin clang null fc null flags operating system target modules environment extra rpaths compiler spec gcc paths cc usr bin gcc cpp usr bin cpp cxx usr bin g usr bin gfortran fc usr bin gfortran flags operating system target modules environment extra rpaths compiler spec gcc paths cc usr bin gcc cpp usr bin cpp cxx usr bin g usr bin gfortran fc usr bin gfortran flags operating system target modules environment extra rpaths compiler spec dpcpp paths cc home mivkov local spack opt spack linux skylake gcc intel oneapi compilers compiler linux bin icx cxx home mivkov local spack opt spack linux skylake gcc intel oneapi compilers compiler linux bin dpcpp home mivkov local spack opt spack linux skylake gcc intel oneapi compilers compiler linux bin ifx fc home mivkov local spack opt spack linux skylake gcc intel oneapi compilers compiler linux bin ifx flags operating system target modules environment extra rpaths compiler spec intel paths cc home mivkov local spack opt spack linux skylake gcc intel oneapi compilers compiler linux bin icc cxx home mivkov local spack opt spack linux skylake gcc intel oneapi compilers compiler linux bin icpc home mivkov local spack opt spack linux skylake gcc intel oneapi compilers compiler linux bin ifort fc home mivkov local spack opt spack linux skylake gcc intel oneapi compilers compiler linux bin ifort flags operating system target modules environment extra rpaths compiler spec oneapi paths cc home mivkov local spack opt spack linux skylake gcc intel oneapi compilers compiler linux bin icx cxx home mivkov local spack opt spack linux skylake gcc intel oneapi compilers compiler linux bin icpx home mivkov local spack opt spack linux skylake gcc intel oneapi compilers compiler linux bin ifx fc home mivkov local spack opt spack linux skylake gcc intel oneapi compilers compiler linux bin ifx flags operating system target modules environment extra rpaths additional information additional info this occurs when letting spack install autotools itself as well as when i m using my system s autotools as is currently set up in my packages yaml file happens as well when i try compiling using the intel oneapi compilers compiler suite instead of my system s gcc general information i have run spack debug report and reported the version of spack python platform i have run spack maintainers and mentioned any maintainers i have uploaded the build log and environment files i have searched the issues of this repo and believe this is not a duplicate | 0 |
45,903 | 13,135,934,999 | IssuesEvent | 2020-08-07 04:30:39 | shaundmorris/ddf | https://api.github.com/repos/shaundmorris/ddf | closed | CVE-2016-1000343 High Severity Vulnerability detected by WhiteSource | security vulnerability wontfix | ## CVE-2016-1000343 - High Severity Vulnerability
<details><summary><img src='https://www.whitesourcesoftware.com/wp-content/uploads/2018/10/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>bcprov-jdk15on-1.54.jar</b></p></summary>
<p>The Bouncy Castle Crypto package is a Java implementation of cryptographic algorithms. This jar contains JCE provider and lightweight API for the Bouncy Castle Cryptography APIs for JDK 1.5 to JDK 1.8.</p>
<p>path: /root/.m2/repository/org/bouncycastle/bcprov-jdk15on/1.54/bcprov-jdk15on-1.54.jar,/root/.m2/repository/org/bouncycastle/bcprov-jdk15on/1.54/bcprov-jdk15on-1.54.jar,/root/.m2/repository/org/bouncycastle/bcprov-jdk15on/1.54/bcprov-jdk15on-1.54.jar,/root/.m2/repository/org/bouncycastle/bcprov-jdk15on/1.54/bcprov-jdk15on-1.54.jar,/root/.m2/repository/org/bouncycastle/bcprov-jdk15on/1.54/bcprov-jdk15on-1.54.jar</p>
<p>
<p>Library home page: <a href=http://www.bouncycastle.org/java.html>http://www.bouncycastle.org/java.html</a></p>
Dependency Hierarchy:
- tika-parsers-1.18.jar (Root Library)
- :x: **bcprov-jdk15on-1.54.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/shaundmorris/ddf/commit/6134603ad52ed60611f9b2d31e923d9a992ede39">6134603ad52ed60611f9b2d31e923d9a992ede39</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://www.whitesourcesoftware.com/wp-content/uploads/2018/10/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In the Bouncy Castle JCE Provider version 1.55 and earlier the DSA key pair generator generates a weak private key if used with default values. If the JCA key pair generator is not explicitly initialised with DSA parameters, 1.55 and earlier generates a private value assuming a 1024 bit key size. In earlier releases this can be dealt with by explicitly passing parameters to the key pair generator.
<p>Publish Date: 2018-06-04
<p>URL: <a href=https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1000343>CVE-2016-1000343</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://www.whitesourcesoftware.com/wp-content/uploads/2018/10/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://www.whitesourcesoftware.com/wp-content/uploads/2018/10/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Change files</p>
<p>Origin: <a href="https://github.com/bcgit/bc-java/commit/50a53068c094d6cff37659da33c9b4505becd389#diff-5578e61500abb2b87b300d3114bdfd7d">https://github.com/bcgit/bc-java/commit/50a53068c094d6cff37659da33c9b4505becd389#diff-5578e61500abb2b87b300d3114bdfd7d</a></p>
<p>Release Date: 2016-11-03</p>
<p>Fix Resolution: Replace or update the following files: KeyPairGeneratorSpi.java, DSATest.java</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2016-1000343 High Severity Vulnerability detected by WhiteSource - ## CVE-2016-1000343 - High Severity Vulnerability
<details><summary><img src='https://www.whitesourcesoftware.com/wp-content/uploads/2018/10/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>bcprov-jdk15on-1.54.jar</b></p></summary>
<p>The Bouncy Castle Crypto package is a Java implementation of cryptographic algorithms. This jar contains JCE provider and lightweight API for the Bouncy Castle Cryptography APIs for JDK 1.5 to JDK 1.8.</p>
<p>path: /root/.m2/repository/org/bouncycastle/bcprov-jdk15on/1.54/bcprov-jdk15on-1.54.jar,/root/.m2/repository/org/bouncycastle/bcprov-jdk15on/1.54/bcprov-jdk15on-1.54.jar,/root/.m2/repository/org/bouncycastle/bcprov-jdk15on/1.54/bcprov-jdk15on-1.54.jar,/root/.m2/repository/org/bouncycastle/bcprov-jdk15on/1.54/bcprov-jdk15on-1.54.jar,/root/.m2/repository/org/bouncycastle/bcprov-jdk15on/1.54/bcprov-jdk15on-1.54.jar</p>
<p>
<p>Library home page: <a href=http://www.bouncycastle.org/java.html>http://www.bouncycastle.org/java.html</a></p>
Dependency Hierarchy:
- tika-parsers-1.18.jar (Root Library)
- :x: **bcprov-jdk15on-1.54.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/shaundmorris/ddf/commit/6134603ad52ed60611f9b2d31e923d9a992ede39">6134603ad52ed60611f9b2d31e923d9a992ede39</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://www.whitesourcesoftware.com/wp-content/uploads/2018/10/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In the Bouncy Castle JCE Provider version 1.55 and earlier the DSA key pair generator generates a weak private key if used with default values. If the JCA key pair generator is not explicitly initialised with DSA parameters, 1.55 and earlier generates a private value assuming a 1024 bit key size. In earlier releases this can be dealt with by explicitly passing parameters to the key pair generator.
<p>Publish Date: 2018-06-04
<p>URL: <a href=https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1000343>CVE-2016-1000343</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://www.whitesourcesoftware.com/wp-content/uploads/2018/10/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://www.whitesourcesoftware.com/wp-content/uploads/2018/10/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Change files</p>
<p>Origin: <a href="https://github.com/bcgit/bc-java/commit/50a53068c094d6cff37659da33c9b4505becd389#diff-5578e61500abb2b87b300d3114bdfd7d">https://github.com/bcgit/bc-java/commit/50a53068c094d6cff37659da33c9b4505becd389#diff-5578e61500abb2b87b300d3114bdfd7d</a></p>
<p>Release Date: 2016-11-03</p>
<p>Fix Resolution: Replace or update the following files: KeyPairGeneratorSpi.java, DSATest.java</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve high severity vulnerability detected by whitesource cve high severity vulnerability vulnerable library bcprov jar the bouncy castle crypto package is a java implementation of cryptographic algorithms this jar contains jce provider and lightweight api for the bouncy castle cryptography apis for jdk to jdk path root repository org bouncycastle bcprov bcprov jar root repository org bouncycastle bcprov bcprov jar root repository org bouncycastle bcprov bcprov jar root repository org bouncycastle bcprov bcprov jar root repository org bouncycastle bcprov bcprov jar library home page a href dependency hierarchy tika parsers jar root library x bcprov jar vulnerable library found in head commit a href vulnerability details in the bouncy castle jce provider version and earlier the dsa key pair generator generates a weak private key if used with default values if the jca key pair generator is not explicitly initialised with dsa parameters and earlier generates a private value assuming a bit key size in earlier releases this can be dealt with by explicitly passing parameters to the key pair generator publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact none availability impact none for more information on scores click a href suggested fix type change files origin a href release date fix resolution replace or update the following files keypairgeneratorspi java dsatest java step up your open source security game with whitesource | 0 |
377,852 | 26,272,511,763 | IssuesEvent | 2023-01-06 18:24:46 | cBarbosa/iris-gestao | https://api.github.com/repos/cBarbosa/iris-gestao | closed | [Imóvel] Ajuste nos tipos de imóvel | documentation | Os 3 tipos de imóveis devem ser:
_ Edificio Corporativo;
_ Sala/Pavimento;
_ Loja; | 1.0 | [Imóvel] Ajuste nos tipos de imóvel - Os 3 tipos de imóveis devem ser:
_ Edificio Corporativo;
_ Sala/Pavimento;
_ Loja; | non_priority | ajuste nos tipos de imóvel os tipos de imóveis devem ser edificio corporativo sala pavimento loja | 0 |
119,787 | 12,042,844,243 | IssuesEvent | 2020-04-14 11:20:21 | NLnetLabs/krillmanager | https://api.github.com/repos/NLnetLabs/krillmanager | closed | Incorrect OWN certificate guidance | bug documentation wizard | The wizard says that an OWN certificate must be in `/tmp` but IIRC this restriction no longer applies. | 1.0 | Incorrect OWN certificate guidance - The wizard says that an OWN certificate must be in `/tmp` but IIRC this restriction no longer applies. | non_priority | incorrect own certificate guidance the wizard says that an own certificate must be in tmp but iirc this restriction no longer applies | 0 |
128,429 | 17,534,425,652 | IssuesEvent | 2021-08-12 03:53:51 | dotnet/project-system | https://api.github.com/repos/dotnet/project-system | closed | Launch Profiles UI doesn't honor property visibility (2) | Bug Triage-Approved Must-Have Feature-Project-Properties-Designer | **Steps to Reproduce**:
1. Add the following property to ProjectDebugPropertyPage.xaml:
``` xml
<StringProperty Name="MyOtherProperty"
Visible="False" />
```
2. Ctrl+F5 to run VS in the experimental hive (the updated .xaml file will be picked up).
3. Create a new C# Console App targeting .NET 5 (or any .NET Core, really)
4. Open the Launch Profiles UI
**Expected Behavior**:
"MyOtherProperty" does not show in the UI.
**Actual Behavior**:
The property does in fact show up:
**User Impact**:
Users see properties they shouldn't.
| 1.0 | Launch Profiles UI doesn't honor property visibility (2) - **Steps to Reproduce**:
1. Add the following property to ProjectDebugPropertyPage.xaml:
``` xml
<StringProperty Name="MyOtherProperty"
Visible="False" />
```
2. Ctrl+F5 to run VS in the experimental hive (the updated .xaml file will be picked up).
3. Create a new C# Console App targeting .NET 5 (or any .NET Core, really)
4. Open the Launch Profiles UI
**Expected Behavior**:
"MyOtherProperty" does not show in the UI.
**Actual Behavior**:
The property does in fact show up:
**User Impact**:
Users see properties they shouldn't.
| non_priority | launch profiles ui doesn t honor property visibility steps to reproduce add the following property to projectdebugpropertypage xaml xml stringproperty name myotherproperty visible false ctrl to run vs in the experimental hive the updated xaml file will be picked up create a new c console app targeting net or any net core really open the launch profiles ui expected behavior myotherproperty does not show in the ui actual behavior the property does in fact show up user impact users see properties they shouldn t | 0 |
34,804 | 12,301,020,403 | IssuesEvent | 2020-05-11 14:49:18 | TIBCOSoftware/TCSTK-Angular | https://api.github.com/repos/TIBCOSoftware/TCSTK-Angular | closed | CVE-2019-16769 (Medium) detected in serialize-javascript-1.9.1.tgz | security vulnerability | ## CVE-2019-16769 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>serialize-javascript-1.9.1.tgz</b></p></summary>
<p>Serialize JavaScript to a superset of JSON that includes regular expressions and functions.</p>
<p>Library home page: <a href="https://registry.npmjs.org/serialize-javascript/-/serialize-javascript-1.9.1.tgz">https://registry.npmjs.org/serialize-javascript/-/serialize-javascript-1.9.1.tgz</a></p>
<p>Path to dependency file: /tmp/ws-scm/TCSTK-Angular/package.json</p>
<p>Path to vulnerable library: /tmp/ws-scm/TCSTK-Angular/node_modules/serialize-javascript/package.json</p>
<p>
Dependency Hierarchy:
- build-angular-0.803.19.tgz (Root Library)
- copy-webpack-plugin-5.0.4.tgz
- :x: **serialize-javascript-1.9.1.tgz** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Affected versions of this package are vulnerable to Cross-site Scripting (XSS). It does not properly mitigate against unsafe characters in serialized regular expressions. This vulnerability is not affected on Node.js environment since Node.js's implementation of RegExp.prototype.toString() backslash-escapes all forward slashes in regular expressions. If serialized data of regular expression objects are used in an environment other than Node.js, it is affected by this vulnerability.
<p>Publish Date: 2019-12-05
<p>URL: <a href=https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-16769>CVE-2019-16769</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 2 Score Details (<b>5.0</b>)</summary>
<p>
Base Score Metrics not available</p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-16769">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-16769</a></p>
<p>Release Date: 2019-12-05</p>
<p>Fix Resolution: v2.1.1</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"serialize-javascript","packageVersion":"1.9.1","isTransitiveDependency":true,"dependencyTree":"@angular-devkit/build-angular:0.803.19;copy-webpack-plugin:5.0.4;serialize-javascript:1.9.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"v2.1.1"}],"vulnerabilityIdentifier":"CVE-2019-16769","vulnerabilityDetails":"Affected versions of this package are vulnerable to Cross-site Scripting (XSS). It does not properly mitigate against unsafe characters in serialized regular expressions. This vulnerability is not affected on Node.js environment since Node.js\u0027s implementation of RegExp.prototype.toString() backslash-escapes all forward slashes in regular expressions. If serialized data of regular expression objects are used in an environment other than Node.js, it is affected by this vulnerability.","vulnerabilityUrl":"https://cve.mitre.org/cgi-bin/cvename.cgi?name\u003dCVE-2019-16769","cvss2Severity":"medium","cvss2Score":"5.0","extraData":{}}</REMEDIATE> --> | True | CVE-2019-16769 (Medium) detected in serialize-javascript-1.9.1.tgz - ## CVE-2019-16769 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>serialize-javascript-1.9.1.tgz</b></p></summary>
<p>Serialize JavaScript to a superset of JSON that includes regular expressions and functions.</p>
<p>Library home page: <a href="https://registry.npmjs.org/serialize-javascript/-/serialize-javascript-1.9.1.tgz">https://registry.npmjs.org/serialize-javascript/-/serialize-javascript-1.9.1.tgz</a></p>
<p>Path to dependency file: /tmp/ws-scm/TCSTK-Angular/package.json</p>
<p>Path to vulnerable library: /tmp/ws-scm/TCSTK-Angular/node_modules/serialize-javascript/package.json</p>
<p>
Dependency Hierarchy:
- build-angular-0.803.19.tgz (Root Library)
- copy-webpack-plugin-5.0.4.tgz
- :x: **serialize-javascript-1.9.1.tgz** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Affected versions of this package are vulnerable to Cross-site Scripting (XSS). It does not properly mitigate against unsafe characters in serialized regular expressions. This vulnerability is not affected on Node.js environment since Node.js's implementation of RegExp.prototype.toString() backslash-escapes all forward slashes in regular expressions. If serialized data of regular expression objects are used in an environment other than Node.js, it is affected by this vulnerability.
<p>Publish Date: 2019-12-05
<p>URL: <a href=https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-16769>CVE-2019-16769</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 2 Score Details (<b>5.0</b>)</summary>
<p>
Base Score Metrics not available</p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-16769">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-16769</a></p>
<p>Release Date: 2019-12-05</p>
<p>Fix Resolution: v2.1.1</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"serialize-javascript","packageVersion":"1.9.1","isTransitiveDependency":true,"dependencyTree":"@angular-devkit/build-angular:0.803.19;copy-webpack-plugin:5.0.4;serialize-javascript:1.9.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"v2.1.1"}],"vulnerabilityIdentifier":"CVE-2019-16769","vulnerabilityDetails":"Affected versions of this package are vulnerable to Cross-site Scripting (XSS). It does not properly mitigate against unsafe characters in serialized regular expressions. This vulnerability is not affected on Node.js environment since Node.js\u0027s implementation of RegExp.prototype.toString() backslash-escapes all forward slashes in regular expressions. If serialized data of regular expression objects are used in an environment other than Node.js, it is affected by this vulnerability.","vulnerabilityUrl":"https://cve.mitre.org/cgi-bin/cvename.cgi?name\u003dCVE-2019-16769","cvss2Severity":"medium","cvss2Score":"5.0","extraData":{}}</REMEDIATE> --> | non_priority | cve medium detected in serialize javascript tgz cve medium severity vulnerability vulnerable library serialize javascript tgz serialize javascript to a superset of json that includes regular expressions and functions library home page a href path to dependency file tmp ws scm tcstk angular package json path to vulnerable library tmp ws scm tcstk angular node modules serialize javascript package json dependency hierarchy build angular tgz root library copy webpack plugin tgz x serialize javascript tgz vulnerable library vulnerability details affected versions of this package are vulnerable to cross site scripting xss it does not properly mitigate against unsafe characters in serialized regular expressions this vulnerability is not affected on node js environment since node js s implementation of regexp prototype tostring backslash escapes all forward slashes in regular expressions if serialized data of regular expression objects are used in an environment other than node js it is affected by this vulnerability publish date url a href cvss score details base score metrics not available suggested fix type upgrade version origin a href release date fix resolution isopenpronvulnerability false ispackagebased true isdefaultbranch true packages vulnerabilityidentifier cve vulnerabilitydetails affected versions of this package are vulnerable to cross site scripting xss it does not properly mitigate against unsafe characters in serialized regular expressions this vulnerability is not affected on node js environment since node js implementation of regexp prototype tostring backslash escapes all forward slashes in regular expressions if serialized data of regular expression objects are used in an environment other than node js it is affected by this vulnerability vulnerabilityurl | 0 |
131,889 | 18,428,894,312 | IssuesEvent | 2021-10-14 04:08:34 | dotnet/aspnetcore | https://api.github.com/repos/dotnet/aspnetcore | opened | Minimal APIs ServiceBase | design-proposal | ## Summary
I had a scene where I had to write a lot of apis, If all the apis were written in program.cs, feels very smelly to me.
So, I need a `ServiceBase` like `ControllerBase`.
## Motivation and goals
Can group apis like controllers
## In scope
Use Minimal APIs to write a lot of API.
## Out of scope
## Risks / unknowns
The service needs to be added before the `WebApplicationBuilder` is built, and the `WebApplication` needs to be injected into the `ServiceBase` constructor via `DI`, so the constructor's operation on `app.Map` can be treated as a singleton, unlike controller
## Examples
Program.cs
```csharp
var builder = WebApplication.CreateBuilder(args);
var app = builder.Services.AddServices(builder);
app.Run();
```
HelloService.cs
```csharp
public class HelloService : ServiceBase
{
public HelloService(IServiceCollection services) : base(services)
{
App.MapGet("/Hello", Hello);
}
public IResult Hello(string word)
{
return Results.Ok($"Hello {word}");
}
}
```
| 1.0 | Minimal APIs ServiceBase - ## Summary
I had a scene where I had to write a lot of apis, If all the apis were written in program.cs, feels very smelly to me.
So, I need a `ServiceBase` like `ControllerBase`.
## Motivation and goals
Can group apis like controllers
## In scope
Use Minimal APIs to write a lot of API.
## Out of scope
## Risks / unknowns
The service needs to be added before the `WebApplicationBuilder` is built, and the `WebApplication` needs to be injected into the `ServiceBase` constructor via `DI`, so the constructor's operation on `app.Map` can be treated as a singleton, unlike controller
## Examples
Program.cs
```csharp
var builder = WebApplication.CreateBuilder(args);
var app = builder.Services.AddServices(builder);
app.Run();
```
HelloService.cs
```csharp
public class HelloService : ServiceBase
{
public HelloService(IServiceCollection services) : base(services)
{
App.MapGet("/Hello", Hello);
}
public IResult Hello(string word)
{
return Results.Ok($"Hello {word}");
}
}
```
| non_priority | minimal apis servicebase summary i had a scene where i had to write a lot of apis if all the apis were written in program cs feels very smelly to me so i need a servicebase like controllerbase motivation and goals can group apis like controllers in scope use minimal apis to write a lot of api out of scope risks unknowns the service needs to be added before the webapplicationbuilder is built and the webapplication needs to be injected into the servicebase constructor via di so the constructor s operation on app map can be treated as a singleton unlike controller examples program cs csharp var builder webapplication createbuilder args var app builder services addservices builder app run helloservice cs csharp public class helloservice servicebase public helloservice iservicecollection services base services app mapget hello hello public iresult hello string word return results ok hello word | 0 |
262,224 | 27,864,885,107 | IssuesEvent | 2023-03-21 09:34:32 | elastic/beats | https://api.github.com/repos/elastic/beats | opened | [S3 + SQS input] Dynamic "max_number_of_messages" boolean option | discuss Team:Security-External Integrations | Based on feedback from customers, especially larger ones, I want to create this issue to discuss a possible way of better handling our scaling for SQS.
**This does not assume we have the capabilities today to perform this, and is to research and discuss further**
**Common SQS workflow behavior**
- A single thread handles the communication with SQS.
- First it will run a ReceiveMessage (with the count configured for max_number_of_messages) to retrieve the next messages in queue.
- For each message retrieved, we run HideVisibilityTimeout, that hides the message from other beat instances that also retrieves messages from the Queue.
- This timeout is 300 seconds, if the S3 object is still being processed when 150s has passed, it will refresh the 300s.
- Once the object has been processed, we send a DeleteMessage to SQS to remove it.
Now let's apply this logic to a usecase:
**Large scale example**
Usecase1:
A customer is storing data from a datasource on S3. This specific data source usually stores a very small amount of events, but over a large amount of S3 objects. This means that even if a single filebeat has no problem handling the amount of objects coming in, its not fast enough to retrieve them from the queue.
Increasing the `max_number_of_messages` helps in this case, but the default values would have been too low. However if we set the default value too high, it will break the usecase below
Usecase2:
A customer is storing data in S3. The specific data source creates 50MB objects (each event being around 200-400 bytes), when retrieving more than a few SQS messages at a time, what will happen is that the underlying filebeat will take a long time processing these objects.
While these are being processed, if you have a higher `max_number_of_messages` (even the default 5 is sometime to high), the `HideVisibilityTimeout` on the other objects waiting to be processed by the same filebeat instance is going to be refreshing for minutes (or even hours), which makes them hidden from other concurrent instances of filebeat that is used to scale SQS ingest horizontally.
This can add latency of minutes or hours, and make the load balancing on SQS really bad.
**Solution**
I want to provide a better user experience for users, to prevent as many usecases as possible (niche usecases we can't cover will always happen).
The solution should be:
- a togglable option, that defaults to false, that overrides the `max_number_of_messages` dynamically.
- It should start at 5 `max_number_of_messages`, minimum is 1, and max is 100
- We need to determine either how long a worker is spending on an object, or how large an object is, and find some good measurements to determine if we should change `max_number_of_messages`
Some metrics we do have access to, that could help determine this:
https://www.elastic.co/guide/en/beats/filebeat/master/filebeat-input-aws-s3.html#_metrics
- sqs_visibility_timeout_extensions_total (How many HideVisibilityTimeouts used)
- sqs_lag_time (How far behind we are)
- s3_object_processing_time (Histogram of the elapsed S3 object processing times in nanoseconds (start of download to completion of parsing).
| True | [S3 + SQS input] Dynamic "max_number_of_messages" boolean option - Based on feedback from customers, especially larger ones, I want to create this issue to discuss a possible way of better handling our scaling for SQS.
**This does not assume we have the capabilities today to perform this, and is to research and discuss further**
**Common SQS workflow behavior**
- A single thread handles the communication with SQS.
- First it will run a ReceiveMessage (with the count configured for max_number_of_messages) to retrieve the next messages in queue.
- For each message retrieved, we run HideVisibilityTimeout, that hides the message from other beat instances that also retrieves messages from the Queue.
- This timeout is 300 seconds, if the S3 object is still being processed when 150s has passed, it will refresh the 300s.
- Once the object has been processed, we send a DeleteMessage to SQS to remove it.
Now let's apply this logic to a usecase:
**Large scale example**
Usecase1:
A customer is storing data from a datasource on S3. This specific data source usually stores a very small amount of events, but over a large amount of S3 objects. This means that even if a single filebeat has no problem handling the amount of objects coming in, its not fast enough to retrieve them from the queue.
Increasing the `max_number_of_messages` helps in this case, but the default values would have been too low. However if we set the default value too high, it will break the usecase below
Usecase2:
A customer is storing data in S3. The specific data source creates 50MB objects (each event being around 200-400 bytes), when retrieving more than a few SQS messages at a time, what will happen is that the underlying filebeat will take a long time processing these objects.
While these are being processed, if you have a higher `max_number_of_messages` (even the default 5 is sometime to high), the `HideVisibilityTimeout` on the other objects waiting to be processed by the same filebeat instance is going to be refreshing for minutes (or even hours), which makes them hidden from other concurrent instances of filebeat that is used to scale SQS ingest horizontally.
This can add latency of minutes or hours, and make the load balancing on SQS really bad.
**Solution**
I want to provide a better user experience for users, to prevent as many usecases as possible (niche usecases we can't cover will always happen).
The solution should be:
- a togglable option, that defaults to false, that overrides the `max_number_of_messages` dynamically.
- It should start at 5 `max_number_of_messages`, minimum is 1, and max is 100
- We need to determine either how long a worker is spending on an object, or how large an object is, and find some good measurements to determine if we should change `max_number_of_messages`
Some metrics we do have access to, that could help determine this:
https://www.elastic.co/guide/en/beats/filebeat/master/filebeat-input-aws-s3.html#_metrics
- sqs_visibility_timeout_extensions_total (How many HideVisibilityTimeouts used)
- sqs_lag_time (How far behind we are)
- s3_object_processing_time (Histogram of the elapsed S3 object processing times in nanoseconds (start of download to completion of parsing).
| non_priority | dynamic max number of messages boolean option based on feedback from customers especially larger ones i want to create this issue to discuss a possible way of better handling our scaling for sqs this does not assume we have the capabilities today to perform this and is to research and discuss further common sqs workflow behavior a single thread handles the communication with sqs first it will run a receivemessage with the count configured for max number of messages to retrieve the next messages in queue for each message retrieved we run hidevisibilitytimeout that hides the message from other beat instances that also retrieves messages from the queue this timeout is seconds if the object is still being processed when has passed it will refresh the once the object has been processed we send a deletemessage to sqs to remove it now let s apply this logic to a usecase large scale example a customer is storing data from a datasource on this specific data source usually stores a very small amount of events but over a large amount of objects this means that even if a single filebeat has no problem handling the amount of objects coming in its not fast enough to retrieve them from the queue increasing the max number of messages helps in this case but the default values would have been too low however if we set the default value too high it will break the usecase below a customer is storing data in the specific data source creates objects each event being around bytes when retrieving more than a few sqs messages at a time what will happen is that the underlying filebeat will take a long time processing these objects while these are being processed if you have a higher max number of messages even the default is sometime to high the hidevisibilitytimeout on the other objects waiting to be processed by the same filebeat instance is going to be refreshing for minutes or even hours which makes them hidden from other concurrent instances of filebeat that is used to scale sqs ingest horizontally this can add latency of minutes or hours and make the load balancing on sqs really bad solution i want to provide a better user experience for users to prevent as many usecases as possible niche usecases we can t cover will always happen the solution should be a togglable option that defaults to false that overrides the max number of messages dynamically it should start at max number of messages minimum is and max is we need to determine either how long a worker is spending on an object or how large an object is and find some good measurements to determine if we should change max number of messages some metrics we do have access to that could help determine this sqs visibility timeout extensions total how many hidevisibilitytimeouts used sqs lag time how far behind we are object processing time histogram of the elapsed object processing times in nanoseconds start of download to completion of parsing | 0 |
183,321 | 21,721,703,359 | IssuesEvent | 2022-05-11 01:17:54 | raindigi/reaction | https://api.github.com/repos/raindigi/reaction | closed | CVE-2020-15256 (High) detected in object-path-0.11.4.tgz - autoclosed | security vulnerability | ## CVE-2020-15256 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>object-path-0.11.4.tgz</b></p></summary>
<p>Access deep object properties using a path</p>
<p>Library home page: <a href="https://registry.npmjs.org/object-path/-/object-path-0.11.4.tgz">https://registry.npmjs.org/object-path/-/object-path-0.11.4.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/object-path/package.json</p>
<p>
Dependency Hierarchy:
- apollo-server-2.3.1.tgz (Root Library)
- apollo-server-core-2.3.1.tgz
- graphql-upload-8.0.2.tgz
- :x: **object-path-0.11.4.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/raindigi/reaction/commit/8fdbba13c35a1c097dff462c1459f4a4adadac45">8fdbba13c35a1c097dff462c1459f4a4adadac45</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
A prototype pollution vulnerability has been found in `object-path` <= 0.11.4 affecting the `set()` method. The vulnerability is limited to the `includeInheritedProps` mode (if version >= 0.11.0 is used), which has to be explicitly enabled by creating a new instance of `object-path` and setting the option `includeInheritedProps: true`, or by using the default `withInheritedProps` instance. The default operating mode is not affected by the vulnerability if version >= 0.11.0 is used. Any usage of `set()` in versions < 0.11.0 is vulnerable. The issue is fixed in object-path version 0.11.5 As a workaround, don't use the `includeInheritedProps: true` options or the `withInheritedProps` instance if using a version >= 0.11.0.
<p>Publish Date: 2020-10-19
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-15256>CVE-2020-15256</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/mariocasciaro/object-path/security/advisories/GHSA-cwx2-736x-mf6w">https://github.com/mariocasciaro/object-path/security/advisories/GHSA-cwx2-736x-mf6w</a></p>
<p>Release Date: 2020-10-19</p>
<p>Fix Resolution (object-path): 0.11.5</p>
<p>Direct dependency fix Resolution (apollo-server): 2.3.2</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2020-15256 (High) detected in object-path-0.11.4.tgz - autoclosed - ## CVE-2020-15256 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>object-path-0.11.4.tgz</b></p></summary>
<p>Access deep object properties using a path</p>
<p>Library home page: <a href="https://registry.npmjs.org/object-path/-/object-path-0.11.4.tgz">https://registry.npmjs.org/object-path/-/object-path-0.11.4.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/object-path/package.json</p>
<p>
Dependency Hierarchy:
- apollo-server-2.3.1.tgz (Root Library)
- apollo-server-core-2.3.1.tgz
- graphql-upload-8.0.2.tgz
- :x: **object-path-0.11.4.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/raindigi/reaction/commit/8fdbba13c35a1c097dff462c1459f4a4adadac45">8fdbba13c35a1c097dff462c1459f4a4adadac45</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
A prototype pollution vulnerability has been found in `object-path` <= 0.11.4 affecting the `set()` method. The vulnerability is limited to the `includeInheritedProps` mode (if version >= 0.11.0 is used), which has to be explicitly enabled by creating a new instance of `object-path` and setting the option `includeInheritedProps: true`, or by using the default `withInheritedProps` instance. The default operating mode is not affected by the vulnerability if version >= 0.11.0 is used. Any usage of `set()` in versions < 0.11.0 is vulnerable. The issue is fixed in object-path version 0.11.5 As a workaround, don't use the `includeInheritedProps: true` options or the `withInheritedProps` instance if using a version >= 0.11.0.
<p>Publish Date: 2020-10-19
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-15256>CVE-2020-15256</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/mariocasciaro/object-path/security/advisories/GHSA-cwx2-736x-mf6w">https://github.com/mariocasciaro/object-path/security/advisories/GHSA-cwx2-736x-mf6w</a></p>
<p>Release Date: 2020-10-19</p>
<p>Fix Resolution (object-path): 0.11.5</p>
<p>Direct dependency fix Resolution (apollo-server): 2.3.2</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve high detected in object path tgz autoclosed cve high severity vulnerability vulnerable library object path tgz access deep object properties using a path library home page a href path to dependency file package json path to vulnerable library node modules object path package json dependency hierarchy apollo server tgz root library apollo server core tgz graphql upload tgz x object path tgz vulnerable library found in head commit a href vulnerability details a prototype pollution vulnerability has been found in object path is used which has to be explicitly enabled by creating a new instance of object path and setting the option includeinheritedprops true or by using the default withinheritedprops instance the default operating mode is not affected by the vulnerability if version is used any usage of set in versions publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution object path direct dependency fix resolution apollo server step up your open source security game with whitesource | 0 |
681 | 2,602,201,344 | IssuesEvent | 2015-02-24 05:57:04 | bboyle/relevance | https://api.github.com/repos/bboyle/relevance | closed | improve test running and coverage | build | - investigate karma or saucelabs to run qunit tests
- run tests in multiple browsers (including IE?)
- allow single running across multiple browsers
- integrate with sauce labs? https://saucelabs.com/pricing or browserstack: http://www.browserstack.com/javascript-testing-api | 1.0 | improve test running and coverage - - investigate karma or saucelabs to run qunit tests
- run tests in multiple browsers (including IE?)
- allow single running across multiple browsers
- integrate with sauce labs? https://saucelabs.com/pricing or browserstack: http://www.browserstack.com/javascript-testing-api | non_priority | improve test running and coverage investigate karma or saucelabs to run qunit tests run tests in multiple browsers including ie allow single running across multiple browsers integrate with sauce labs or browserstack | 0 |
332,128 | 24,336,822,550 | IssuesEvent | 2022-10-01 07:03:06 | otto-de/gitactionboard | https://api.github.com/repos/otto-de/gitactionboard | closed | Running the docker Container | documentation | Hi it would be nice to have an example deployment in the README, using an organisation and or a USERNAME. Also a multi repo view example too would be appreciated. | 1.0 | Running the docker Container - Hi it would be nice to have an example deployment in the README, using an organisation and or a USERNAME. Also a multi repo view example too would be appreciated. | non_priority | running the docker container hi it would be nice to have an example deployment in the readme using an organisation and or a username also a multi repo view example too would be appreciated | 0 |
180,413 | 21,625,728,475 | IssuesEvent | 2022-05-05 01:41:13 | Sh2dowFi3nd/Test_2 | https://api.github.com/repos/Sh2dowFi3nd/Test_2 | closed | CVE-2017-12626 (High) detected in poi-3.8.jar - autoclosed | security vulnerability | ## CVE-2017-12626 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>poi-3.8.jar</b></p></summary>
<p>Apache POI - Java API To Access Microsoft Format Files</p>
<p>Library home page: <a href="http://poi.apache.org/">http://poi.apache.org/</a></p>
<p>
Dependency Hierarchy:
- :x: **poi-3.8.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/Sh2dowFi3nd/Test_2/commit/496ee93a49670cf2906171c7293cf9b50cc09d47">496ee93a49670cf2906171c7293cf9b50cc09d47</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Apache POI in versions prior to release 3.17 are vulnerable to Denial of Service Attacks: 1) Infinite Loops while parsing crafted WMF, EMF, MSG and macros (POI bugs 61338 and 61294), and 2) Out of Memory Exceptions while parsing crafted DOC, PPT and XLS (POI bugs 52372 and 61295).
<p>Publish Date: 2018-01-29
<p>URL: <a href=https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-12626>CVE-2017-12626</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://lists.apache.org/thread.html/453d9af5dbabaccd9afb58d27279a9dbfe8e35f4e5ea1645ddd6960b@%3Cdev.poi.apache.org%3E">https://lists.apache.org/thread.html/453d9af5dbabaccd9afb58d27279a9dbfe8e35f4e5ea1645ddd6960b@%3Cdev.poi.apache.org%3E</a></p>
<p>Release Date: 2018-01-29</p>
<p>Fix Resolution: org.apache.poi:poi-scratchpad:3.17,org.apache.poi:poi:3.17</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2017-12626 (High) detected in poi-3.8.jar - autoclosed - ## CVE-2017-12626 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>poi-3.8.jar</b></p></summary>
<p>Apache POI - Java API To Access Microsoft Format Files</p>
<p>Library home page: <a href="http://poi.apache.org/">http://poi.apache.org/</a></p>
<p>
Dependency Hierarchy:
- :x: **poi-3.8.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/Sh2dowFi3nd/Test_2/commit/496ee93a49670cf2906171c7293cf9b50cc09d47">496ee93a49670cf2906171c7293cf9b50cc09d47</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Apache POI in versions prior to release 3.17 are vulnerable to Denial of Service Attacks: 1) Infinite Loops while parsing crafted WMF, EMF, MSG and macros (POI bugs 61338 and 61294), and 2) Out of Memory Exceptions while parsing crafted DOC, PPT and XLS (POI bugs 52372 and 61295).
<p>Publish Date: 2018-01-29
<p>URL: <a href=https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-12626>CVE-2017-12626</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://lists.apache.org/thread.html/453d9af5dbabaccd9afb58d27279a9dbfe8e35f4e5ea1645ddd6960b@%3Cdev.poi.apache.org%3E">https://lists.apache.org/thread.html/453d9af5dbabaccd9afb58d27279a9dbfe8e35f4e5ea1645ddd6960b@%3Cdev.poi.apache.org%3E</a></p>
<p>Release Date: 2018-01-29</p>
<p>Fix Resolution: org.apache.poi:poi-scratchpad:3.17,org.apache.poi:poi:3.17</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve high detected in poi jar autoclosed cve high severity vulnerability vulnerable library poi jar apache poi java api to access microsoft format files library home page a href dependency hierarchy x poi jar vulnerable library found in head commit a href vulnerability details apache poi in versions prior to release are vulnerable to denial of service attacks infinite loops while parsing crafted wmf emf msg and macros poi bugs and and out of memory exceptions while parsing crafted doc ppt and xls poi bugs and publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution org apache poi poi scratchpad org apache poi poi step up your open source security game with whitesource | 0 |
234,930 | 19,276,913,757 | IssuesEvent | 2021-12-10 12:58:51 | IntellectualSites/PlotSquared | https://api.github.com/repos/IntellectualSites/PlotSquared | opened | when importing PlotSquared-Bukkit: The POM for org.enginehub:squirrelid:jar:0.3.0 is missing, no dependency information available | Requires Testing | ### Server Implementation
Paper
### Server Version
1.18
### Describe the bug
Similar to https://github.com/IntellectualSites/PlotSquared/issues/3359, but with ``org.enginehub:squirrelid`` when importing ``PlotSquared-Bukkit``
Such as:
```xml
<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>co.purevanilla.mcplugins</groupId>
<artifactId>ShopWorld</artifactId>
<version>1.0.0</version>
<properties>
<maven.compiler.source>17</maven.compiler.source>
<maven.compiler.target>17</maven.compiler.target>
</properties>
<repositories>
<repository>
<id>sonatype snapshots</id>
<url>https://s01.oss.sonatype.org/content/repositories/snapshots/</url>
</repository>
</repositories>
<dependencies>
<dependency>
<groupId>com.plotsquared</groupId>
<artifactId>PlotSquared-Core</artifactId>
<version>6.1.5-SNAPSHOT</version>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>com.plotsquared</groupId>
<artifactId>PlotSquared-Bukkit</artifactId>
<version>6.1.5-SNAPSHOT</version>
<scope>provided</scope>
<exclusions>
<exclusion>
<artifactId>PlotSquared-Core</artifactId>
<groupId>*</groupId>
</exclusion>
</exclusions>
</dependency>
</dependencies>
</project>
```
```
[INFO] Scanning for projects...
[INFO]
[INFO] -----------------< co.purevanilla.mcplugins:ShopWorld >-----------------
[INFO] Building ShopWorld 1.0.0
[INFO] --------------------------------[ jar ]---------------------------------
[WARNING] The POM for org.enginehub:squirrelid:jar:0.3.0 is missing, no dependency information available
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 0.598 s
[INFO] Finished at: 2021-12-10T13:52:39+01:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project ShopWorld: Could not resolve dependencies for project co.purevanilla.mcplugins:ShopWorld:jar:1.0.0: Failure to find org.enginehub:squirrelid:jar:0.3.0 in https://s01.oss.sonatype.org/content/repositories/snapshots/ was cached in the local repository, resolution will not be reattempted until the update interval of intellectualsites snapshots has elapsed or updates are forced -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
Process finished with exit code 1
```
### To Reproduce
1. Create a new maven-based project
2. Import PlotSquared Core and PlotSquared Bukkit
3. Build
### Expected behaviour
Valid build
### Screenshots / Videos
_No response_
### Error log (if applicable)
_No response_
### Plot Debugpaste
no debugpaste
### PlotSquared Version
6.1.5-SNAPSHOT
### Checklist
- [X] I have included a Plot debugpaste.
- [X] I am using the newest build from https://www.spigotmc.org/resources/77506/ and the issue still persists.
### Anything else?
See https://github.com/IntellectualSites/PlotSquared/issues/3359,
I've also tested importing both repos with
```xml
<repositories>
<repository>
<id>sonatype snapshots</id>
<url>https://s01.oss.sonatype.org/content/repositories/snapshots/</url>
</repository>
<repository>
<id>intellectualsites.com snapshots</id>
<url>https://mvn.intellectualsites.com/content/repositories/snapshots/</url>
</repository>
</repositories>
```
same deal sadly | 1.0 | when importing PlotSquared-Bukkit: The POM for org.enginehub:squirrelid:jar:0.3.0 is missing, no dependency information available - ### Server Implementation
Paper
### Server Version
1.18
### Describe the bug
Similar to https://github.com/IntellectualSites/PlotSquared/issues/3359, but with ``org.enginehub:squirrelid`` when importing ``PlotSquared-Bukkit``
Such as:
```xml
<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>co.purevanilla.mcplugins</groupId>
<artifactId>ShopWorld</artifactId>
<version>1.0.0</version>
<properties>
<maven.compiler.source>17</maven.compiler.source>
<maven.compiler.target>17</maven.compiler.target>
</properties>
<repositories>
<repository>
<id>sonatype snapshots</id>
<url>https://s01.oss.sonatype.org/content/repositories/snapshots/</url>
</repository>
</repositories>
<dependencies>
<dependency>
<groupId>com.plotsquared</groupId>
<artifactId>PlotSquared-Core</artifactId>
<version>6.1.5-SNAPSHOT</version>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>com.plotsquared</groupId>
<artifactId>PlotSquared-Bukkit</artifactId>
<version>6.1.5-SNAPSHOT</version>
<scope>provided</scope>
<exclusions>
<exclusion>
<artifactId>PlotSquared-Core</artifactId>
<groupId>*</groupId>
</exclusion>
</exclusions>
</dependency>
</dependencies>
</project>
```
```
[INFO] Scanning for projects...
[INFO]
[INFO] -----------------< co.purevanilla.mcplugins:ShopWorld >-----------------
[INFO] Building ShopWorld 1.0.0
[INFO] --------------------------------[ jar ]---------------------------------
[WARNING] The POM for org.enginehub:squirrelid:jar:0.3.0 is missing, no dependency information available
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 0.598 s
[INFO] Finished at: 2021-12-10T13:52:39+01:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project ShopWorld: Could not resolve dependencies for project co.purevanilla.mcplugins:ShopWorld:jar:1.0.0: Failure to find org.enginehub:squirrelid:jar:0.3.0 in https://s01.oss.sonatype.org/content/repositories/snapshots/ was cached in the local repository, resolution will not be reattempted until the update interval of intellectualsites snapshots has elapsed or updates are forced -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
Process finished with exit code 1
```
### To Reproduce
1. Create a new maven-based project
2. Import PlotSquared Core and PlotSquared Bukkit
3. Build
### Expected behaviour
Valid build
### Screenshots / Videos
_No response_
### Error log (if applicable)
_No response_
### Plot Debugpaste
no debugpaste
### PlotSquared Version
6.1.5-SNAPSHOT
### Checklist
- [X] I have included a Plot debugpaste.
- [X] I am using the newest build from https://www.spigotmc.org/resources/77506/ and the issue still persists.
### Anything else?
See https://github.com/IntellectualSites/PlotSquared/issues/3359,
I've also tested importing both repos with
```xml
<repositories>
<repository>
<id>sonatype snapshots</id>
<url>https://s01.oss.sonatype.org/content/repositories/snapshots/</url>
</repository>
<repository>
<id>intellectualsites.com snapshots</id>
<url>https://mvn.intellectualsites.com/content/repositories/snapshots/</url>
</repository>
</repositories>
```
same deal sadly | non_priority | when importing plotsquared bukkit the pom for org enginehub squirrelid jar is missing no dependency information available server implementation paper server version describe the bug similar to but with org enginehub squirrelid when importing plotsquared bukkit such as xml project xmlns xmlns xsi xsi schemalocation co purevanilla mcplugins shopworld sonatype snapshots com plotsquared plotsquared core snapshot provided com plotsquared plotsquared bukkit snapshot provided plotsquared core scanning for projects building shopworld the pom for org enginehub squirrelid jar is missing no dependency information available build failure total time s finished at failed to execute goal on project shopworld could not resolve dependencies for project co purevanilla mcplugins shopworld jar failure to find org enginehub squirrelid jar in was cached in the local repository resolution will not be reattempted until the update interval of intellectualsites snapshots has elapsed or updates are forced to see the full stack trace of the errors re run maven with the e switch re run maven using the x switch to enable full debug logging for more information about the errors and possible solutions please read the following articles process finished with exit code to reproduce create a new maven based project import plotsquared core and plotsquared bukkit build expected behaviour valid build screenshots videos no response error log if applicable no response plot debugpaste no debugpaste plotsquared version snapshot checklist i have included a plot debugpaste i am using the newest build from and the issue still persists anything else see i ve also tested importing both repos with xml sonatype snapshots intellectualsites com snapshots same deal sadly | 0 |
29,990 | 4,544,394,985 | IssuesEvent | 2016-09-10 17:24:42 | FreeCodeCamp/FreeCodeCamp | https://api.github.com/repos/FreeCodeCamp/FreeCodeCamp | closed | Iterate over Array with .map Issue! FIXED by FCC | confirmed help wanted tests | Challenge [iterate-over-arrays-with-map](https://www.freecodecamp.com/en/challenges/object-oriented-and-functional-programming/iterate-over-arrays-with-map) has an issue.
User Agent is: <code>Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36</code>.
Please describe how to reproduce this issue, and include links to screenshots if possible.
My code is as followed but I keep getting "You should only modify arrays with map"! Please could you have a look into this?
```js
var oldArray = [1,2,3,4,5];
// Only change code below this line.
var newArray = oldArray.map(function(num){
return num + 3;
});
```
| 1.0 | Iterate over Array with .map Issue! FIXED by FCC - Challenge [iterate-over-arrays-with-map](https://www.freecodecamp.com/en/challenges/object-oriented-and-functional-programming/iterate-over-arrays-with-map) has an issue.
User Agent is: <code>Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36</code>.
Please describe how to reproduce this issue, and include links to screenshots if possible.
My code is as followed but I keep getting "You should only modify arrays with map"! Please could you have a look into this?
```js
var oldArray = [1,2,3,4,5];
// Only change code below this line.
var newArray = oldArray.map(function(num){
return num + 3;
});
```
| non_priority | iterate over array with map issue fixed by fcc challenge has an issue user agent is mozilla windows nt applewebkit khtml like gecko chrome safari please describe how to reproduce this issue and include links to screenshots if possible my code is as followed but i keep getting you should only modify arrays with map please could you have a look into this js var oldarray only change code below this line var newarray oldarray map function num return num | 0 |
207,903 | 16,097,112,463 | IssuesEvent | 2021-04-27 02:36:29 | padma-g/info478-project | https://api.github.com/repos/padma-g/info478-project | closed | Identify target audience and research questions | documentation | Who is the target audience? Depending on the domain of the data, there may be a variety of audiences interested in using the dataset. We should hone in on one of these audiences.
What should the audience learn from the resource? Please consider specific questions that the project can answer using the data that has been identified (that are related to the overarching purpose of the project) | 1.0 | Identify target audience and research questions - Who is the target audience? Depending on the domain of the data, there may be a variety of audiences interested in using the dataset. We should hone in on one of these audiences.
What should the audience learn from the resource? Please consider specific questions that the project can answer using the data that has been identified (that are related to the overarching purpose of the project) | non_priority | identify target audience and research questions who is the target audience depending on the domain of the data there may be a variety of audiences interested in using the dataset we should hone in on one of these audiences what should the audience learn from the resource please consider specific questions that the project can answer using the data that has been identified that are related to the overarching purpose of the project | 0 |
14,131 | 5,560,911,764 | IssuesEvent | 2017-03-24 20:50:47 | STScI-JWST/jwst | https://api.github.com/repos/STScI-JWST/jwst | closed | cube_build_io, association and ModelContainer | associations bug cube_build datamodels | From a [basecamp report by Jeb](https://stsci-ins.basecamphq.com/projects/11477312-jwst-pipeline/posts/100992154/comments), it appears there is a conflict about how/when associations are opened. cube_build is expecting just the filename for the association, but in the pipeline, it has already been opened as a ModelContainer
The offending section of code in cube_build_io is lines 517-543.
@jemorrison @jdavies-st Thoughts? | 1.0 | cube_build_io, association and ModelContainer - From a [basecamp report by Jeb](https://stsci-ins.basecamphq.com/projects/11477312-jwst-pipeline/posts/100992154/comments), it appears there is a conflict about how/when associations are opened. cube_build is expecting just the filename for the association, but in the pipeline, it has already been opened as a ModelContainer
The offending section of code in cube_build_io is lines 517-543.
@jemorrison @jdavies-st Thoughts? | non_priority | cube build io association and modelcontainer from a it appears there is a conflict about how when associations are opened cube build is expecting just the filename for the association but in the pipeline it has already been opened as a modelcontainer the offending section of code in cube build io is lines jemorrison jdavies st thoughts | 0 |
146,862 | 23,134,132,235 | IssuesEvent | 2022-07-28 13:03:28 | patternfly/patternfly-design | https://api.github.com/repos/patternfly/patternfly-design | closed | [PieChart] - [docs update] | needs Info needs design/css | **Is this a new component or an extension of an existing one?**
I would like you to update the PieChart documentation and add my example to it
**Describe the feature**
My example uses the Tooltip component that wraps the ChartLabel.
The Patternfly Tooltip documentation contains class examples only and not a functional component.
https://codesandbox.io/s/vigorous-wozniak-ke604g?file=/index.js:0-1639
```
import ReactDOM from "react-dom";
import "@patternfly/react-core/dist/styles/base.css";
import "./fonts.css";
import React from "react";
import { ChartPie, ChartLabel } from "@patternfly/react-charts";
import { Tooltip } from "@patternfly/react-core";
const CustomLabel = ({ datum, ...rest }) => (
<Tooltip
content={
<snap>
{datum.x}:{datum.y}
</snap>
}
enableFlip
>
<ChartLabel {...rest} />
</Tooltip>
);
const BasicWithRightAlignedLegend = () => {
return (
<div style={{ height: "230px", width: "350px" }}>
<ChartPie
labelComponent={
<CustomLabel
textAnchor="middle"
style={{ fill: "white", fontSize: 13 }}
/>
}
labelRadius={25}
ariaDesc="Average number of pets"
ariaTitle="Pie chart example"
constrainToVisibleArea={true}
data={[
{ x: "Cats", y: 35 },
{ x: "Dogs", y: 55 },
{ x: "Birds", y: 10 },
{ x: "Fishes", y: 15 }
]}
height={230}
labels={({ datum }) => `${datum.y}`}
legendData={[
{ name: "Cats: 35" },
{ name: "Dogs: 55" },
{ name: "Birds: 10" },
{ name: "Fishes: 15" }
]}
legendOrientation="vertical"
legendPosition="right"
padding={{
bottom: 20,
left: 20,
right: 140, // Adjusted to accommodate legend
top: 20
}}
width={350}
/>
</div>
);
};
const rootElement = document.getElementById("root");
ReactDOM.render(<BasicWithRightAlignedLegend />, rootElement);
```
**Are there visuals for this feature? If applicable, please include examples for each state and for varying widths**
Include screenshots or links to Marvel or other mockups.
| 1.0 | [PieChart] - [docs update] - **Is this a new component or an extension of an existing one?**
I would like you to update the PieChart documentation and add my example to it
**Describe the feature**
My example uses the Tooltip component that wraps the ChartLabel.
The Patternfly Tooltip documentation contains class examples only and not a functional component.
https://codesandbox.io/s/vigorous-wozniak-ke604g?file=/index.js:0-1639
```
import ReactDOM from "react-dom";
import "@patternfly/react-core/dist/styles/base.css";
import "./fonts.css";
import React from "react";
import { ChartPie, ChartLabel } from "@patternfly/react-charts";
import { Tooltip } from "@patternfly/react-core";
const CustomLabel = ({ datum, ...rest }) => (
<Tooltip
content={
<snap>
{datum.x}:{datum.y}
</snap>
}
enableFlip
>
<ChartLabel {...rest} />
</Tooltip>
);
const BasicWithRightAlignedLegend = () => {
return (
<div style={{ height: "230px", width: "350px" }}>
<ChartPie
labelComponent={
<CustomLabel
textAnchor="middle"
style={{ fill: "white", fontSize: 13 }}
/>
}
labelRadius={25}
ariaDesc="Average number of pets"
ariaTitle="Pie chart example"
constrainToVisibleArea={true}
data={[
{ x: "Cats", y: 35 },
{ x: "Dogs", y: 55 },
{ x: "Birds", y: 10 },
{ x: "Fishes", y: 15 }
]}
height={230}
labels={({ datum }) => `${datum.y}`}
legendData={[
{ name: "Cats: 35" },
{ name: "Dogs: 55" },
{ name: "Birds: 10" },
{ name: "Fishes: 15" }
]}
legendOrientation="vertical"
legendPosition="right"
padding={{
bottom: 20,
left: 20,
right: 140, // Adjusted to accommodate legend
top: 20
}}
width={350}
/>
</div>
);
};
const rootElement = document.getElementById("root");
ReactDOM.render(<BasicWithRightAlignedLegend />, rootElement);
```
**Are there visuals for this feature? If applicable, please include examples for each state and for varying widths**
Include screenshots or links to Marvel or other mockups.
| non_priority | is this a new component or an extension of an existing one i would like you to update the piechart documentation and add my example to it describe the feature my example uses the tooltip component that wraps the chartlabel the patternfly tooltip documentation contains class examples only and not a functional component import reactdom from react dom import patternfly react core dist styles base css import fonts css import react from react import chartpie chartlabel from patternfly react charts import tooltip from patternfly react core const customlabel datum rest tooltip content datum x datum y enableflip const basicwithrightalignedlegend return chartpie labelcomponent customlabel textanchor middle style fill white fontsize labelradius ariadesc average number of pets ariatitle pie chart example constraintovisiblearea true data x cats y x dogs y x birds y x fishes y height labels datum datum y legenddata name cats name dogs name birds name fishes legendorientation vertical legendposition right padding bottom left right adjusted to accommodate legend top width const rootelement document getelementbyid root reactdom render rootelement are there visuals for this feature if applicable please include examples for each state and for varying widths include screenshots or links to marvel or other mockups | 0 |
209,365 | 23,716,690,423 | IssuesEvent | 2022-08-30 12:23:24 | rsoreq/zaproxy | https://api.github.com/repos/rsoreq/zaproxy | closed | CVE-2020-36188 (High) detected in jackson-databind-2.9.10.jar - autoclosed | security vulnerability | ## CVE-2020-36188 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jackson-databind-2.9.10.jar</b></p></summary>
<p>General data-binding functionality for Jackson: works on core streaming API</p>
<p>Library home page: <a href="http://github.com/FasterXML/jackson">http://github.com/FasterXML/jackson</a></p>
<p>Path to dependency file: /zap/zap.gradle.kts</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/com.fasterxml.jackson.core/jackson-databind/2.9.10/e201bb70b7469ba18dd58ed8268aa44e702fa2f0/jackson-databind-2.9.10.jar</p>
<p>
Dependency Hierarchy:
- wiremock-jre8-2.25.1.jar (Root Library)
- :x: **jackson-databind-2.9.10.jar** (Vulnerable Library)
<p>Found in base branch: <b>develop</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
FasterXML jackson-databind 2.x before 2.9.10.8 mishandles the interaction between serialization gadgets and typing, related to com.newrelic.agent.deps.ch.qos.logback.core.db.JNDIConnectionSource.
<p>Publish Date: 2021-01-06
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-36188>CVE-2020-36188</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>8.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2021-01-06</p>
<p>Fix Resolution (com.fasterxml.jackson.core:jackson-databind): 2.9.10.8</p>
<p>Direct dependency fix Resolution (com.github.tomakehurst:wiremock-jre8): 2.26.0</p>
</p>
</details>
<p></p>
***
:rescue_worker_helmet: Automatic Remediation is available for this issue | True | CVE-2020-36188 (High) detected in jackson-databind-2.9.10.jar - autoclosed - ## CVE-2020-36188 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jackson-databind-2.9.10.jar</b></p></summary>
<p>General data-binding functionality for Jackson: works on core streaming API</p>
<p>Library home page: <a href="http://github.com/FasterXML/jackson">http://github.com/FasterXML/jackson</a></p>
<p>Path to dependency file: /zap/zap.gradle.kts</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/com.fasterxml.jackson.core/jackson-databind/2.9.10/e201bb70b7469ba18dd58ed8268aa44e702fa2f0/jackson-databind-2.9.10.jar</p>
<p>
Dependency Hierarchy:
- wiremock-jre8-2.25.1.jar (Root Library)
- :x: **jackson-databind-2.9.10.jar** (Vulnerable Library)
<p>Found in base branch: <b>develop</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
FasterXML jackson-databind 2.x before 2.9.10.8 mishandles the interaction between serialization gadgets and typing, related to com.newrelic.agent.deps.ch.qos.logback.core.db.JNDIConnectionSource.
<p>Publish Date: 2021-01-06
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-36188>CVE-2020-36188</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>8.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2021-01-06</p>
<p>Fix Resolution (com.fasterxml.jackson.core:jackson-databind): 2.9.10.8</p>
<p>Direct dependency fix Resolution (com.github.tomakehurst:wiremock-jre8): 2.26.0</p>
</p>
</details>
<p></p>
***
:rescue_worker_helmet: Automatic Remediation is available for this issue | non_priority | cve high detected in jackson databind jar autoclosed cve high severity vulnerability vulnerable library jackson databind jar general data binding functionality for jackson works on core streaming api library home page a href path to dependency file zap zap gradle kts path to vulnerable library home wss scanner gradle caches modules files com fasterxml jackson core jackson databind jackson databind jar dependency hierarchy wiremock jar root library x jackson databind jar vulnerable library found in base branch develop vulnerability details fasterxml jackson databind x before mishandles the interaction between serialization gadgets and typing related to com newrelic agent deps ch qos logback core db jndiconnectionsource publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version release date fix resolution com fasterxml jackson core jackson databind direct dependency fix resolution com github tomakehurst wiremock rescue worker helmet automatic remediation is available for this issue | 0 |
259,121 | 19,587,085,843 | IssuesEvent | 2022-01-05 08:30:41 | audeering/audformat | https://api.github.com/repos/audeering/audformat | closed | Difference between TIME and DATE in audformat.define.DataType | documentation question | Let's assume you would like to store the exact date and time of a recording using `datetime.datetime`, then it is not obvious from the [current documentation](https://audeering.github.io/audformat/api-define.html) what the data type of the scheme should be: `TIME` or `DATE`.
I would assume that `TIME` should cover duration values rather then datetime values, correct?
/cc @agfcrespi | 1.0 | Difference between TIME and DATE in audformat.define.DataType - Let's assume you would like to store the exact date and time of a recording using `datetime.datetime`, then it is not obvious from the [current documentation](https://audeering.github.io/audformat/api-define.html) what the data type of the scheme should be: `TIME` or `DATE`.
I would assume that `TIME` should cover duration values rather then datetime values, correct?
/cc @agfcrespi | non_priority | difference between time and date in audformat define datatype let s assume you would like to store the exact date and time of a recording using datetime datetime then it is not obvious from the what the data type of the scheme should be time or date i would assume that time should cover duration values rather then datetime values correct cc agfcrespi | 0 |
4,962 | 25,479,207,790 | IssuesEvent | 2022-11-25 17:57:00 | bazelbuild/intellij | https://api.github.com/repos/bazelbuild/intellij | closed | Run gazelle on project sync | type: feature request P1 lang: go product: IntelliJ topic: sync product: GoLand awaiting-maintainer | ## Problem
For projects that use gazelle, moving a single file is a two-step process: First they must run gazelle, then they must sync to trigger re-indexing if IntelliJ didn't pick those changes up.
Ideally, this would be a single-click action, whereby a user only has to click "sync" after a refactoring is done.
## Proposed Solution
Run Gazelle on sync, at least for full, non-incremental syncs of projects, before we run the bazel build that enables the actual sync.
Regarding performance, Gazelle accepts packages as arguments, so I believe it should be possible to inspect the `.bazelproject` file to gather which packages it should sync, therefore correlating performance to the size of the indexed project.
The changes I imagine would be needed:
- Additional entries in the Bazel Plugin preferences, where the user can specify:
- The label of the Gazelle target to run.
- The frequency of the gazelle runs (on every sync, or only on full syncs).
- Custom logic to derive go packages from the `directories` entry in the `.bazelproject`.
- A call to gazelle during project sync, which would run before even the initial query.
I'm happy to spend the effort of implementing this, but as per the contributing guidelines I thought I'd ask first if this would be an interesting contribution, and if I missed important pieces. | True | Run gazelle on project sync - ## Problem
For projects that use gazelle, moving a single file is a two-step process: First they must run gazelle, then they must sync to trigger re-indexing if IntelliJ didn't pick those changes up.
Ideally, this would be a single-click action, whereby a user only has to click "sync" after a refactoring is done.
## Proposed Solution
Run Gazelle on sync, at least for full, non-incremental syncs of projects, before we run the bazel build that enables the actual sync.
Regarding performance, Gazelle accepts packages as arguments, so I believe it should be possible to inspect the `.bazelproject` file to gather which packages it should sync, therefore correlating performance to the size of the indexed project.
The changes I imagine would be needed:
- Additional entries in the Bazel Plugin preferences, where the user can specify:
- The label of the Gazelle target to run.
- The frequency of the gazelle runs (on every sync, or only on full syncs).
- Custom logic to derive go packages from the `directories` entry in the `.bazelproject`.
- A call to gazelle during project sync, which would run before even the initial query.
I'm happy to spend the effort of implementing this, but as per the contributing guidelines I thought I'd ask first if this would be an interesting contribution, and if I missed important pieces. | non_priority | run gazelle on project sync problem for projects that use gazelle moving a single file is a two step process first they must run gazelle then they must sync to trigger re indexing if intellij didn t pick those changes up ideally this would be a single click action whereby a user only has to click sync after a refactoring is done proposed solution run gazelle on sync at least for full non incremental syncs of projects before we run the bazel build that enables the actual sync regarding performance gazelle accepts packages as arguments so i believe it should be possible to inspect the bazelproject file to gather which packages it should sync therefore correlating performance to the size of the indexed project the changes i imagine would be needed additional entries in the bazel plugin preferences where the user can specify the label of the gazelle target to run the frequency of the gazelle runs on every sync or only on full syncs custom logic to derive go packages from the directories entry in the bazelproject a call to gazelle during project sync which would run before even the initial query i m happy to spend the effort of implementing this but as per the contributing guidelines i thought i d ask first if this would be an interesting contribution and if i missed important pieces | 0 |
5,828 | 30,849,982,196 | IssuesEvent | 2023-08-02 16:01:56 | obi1kenobi/trustfall | https://api.github.com/repos/obi1kenobi/trustfall | opened | Consider switching fuzzer backends to LibAFL | C-maintainability | LibFuzzer is in [maintenance mode](https://llvm.org/docs/LibFuzzer.html#status):
> The original authors of libFuzzer have stopped active work on it and switched to working on another fuzzing engine, [Centipede](https://github.com/google/centipede).
We should consider switching to LibAFL or another implementation, since it seems that we can get both fuzzing performance and maintainability improvements.
More info:
https://hachyderm.io/@addison@infosec.exchange/110820552409622753
https://github.com/rust-fuzz/cargo-fuzz/issues/330 | True | Consider switching fuzzer backends to LibAFL - LibFuzzer is in [maintenance mode](https://llvm.org/docs/LibFuzzer.html#status):
> The original authors of libFuzzer have stopped active work on it and switched to working on another fuzzing engine, [Centipede](https://github.com/google/centipede).
We should consider switching to LibAFL or another implementation, since it seems that we can get both fuzzing performance and maintainability improvements.
More info:
https://hachyderm.io/@addison@infosec.exchange/110820552409622753
https://github.com/rust-fuzz/cargo-fuzz/issues/330 | non_priority | consider switching fuzzer backends to libafl libfuzzer is in the original authors of libfuzzer have stopped active work on it and switched to working on another fuzzing engine we should consider switching to libafl or another implementation since it seems that we can get both fuzzing performance and maintainability improvements more info | 0 |
94,874 | 27,319,336,782 | IssuesEvent | 2023-02-24 18:19:06 | helidon-io/helidon | https://api.github.com/repos/helidon-io/helidon | opened | Incorrect code in generated `Abstract<BuilderTarget>` class when target interface extends another interface | bug 4.x builder | ## Environment Details
* Helidon Version: 4.x
* Helidon SE or Helidon MP
* JDK version:
* OS:
* Docker version (if applicable):
----------
## Problem Description
If I have
```java
public interfaceMyInterface extends YourInterface {
// ...
}
```
then the generated `AbstractMyInterface` class has `extends AbstractYourInterface` even though there is no such class.
I actually encountered this when `YourInterface` is in a 3rd-party library. Obviously I cannot add `@Builder` to it in that case but I wanted a builder and a Helidon-specific implementation I could extend with some special behavior (and obviously cannot add `@Builder` to the 3rd-party interface itself).
## Steps to reproduce
See above.
| 1.0 | Incorrect code in generated `Abstract<BuilderTarget>` class when target interface extends another interface - ## Environment Details
* Helidon Version: 4.x
* Helidon SE or Helidon MP
* JDK version:
* OS:
* Docker version (if applicable):
----------
## Problem Description
If I have
```java
public interfaceMyInterface extends YourInterface {
// ...
}
```
then the generated `AbstractMyInterface` class has `extends AbstractYourInterface` even though there is no such class.
I actually encountered this when `YourInterface` is in a 3rd-party library. Obviously I cannot add `@Builder` to it in that case but I wanted a builder and a Helidon-specific implementation I could extend with some special behavior (and obviously cannot add `@Builder` to the 3rd-party interface itself).
## Steps to reproduce
See above.
| non_priority | incorrect code in generated abstract class when target interface extends another interface environment details helidon version x helidon se or helidon mp jdk version os docker version if applicable problem description if i have java public interfacemyinterface extends yourinterface then the generated abstractmyinterface class has extends abstractyourinterface even though there is no such class i actually encountered this when yourinterface is in a party library obviously i cannot add builder to it in that case but i wanted a builder and a helidon specific implementation i could extend with some special behavior and obviously cannot add builder to the party interface itself steps to reproduce see above | 0 |
350,154 | 31,857,740,074 | IssuesEvent | 2023-09-15 08:42:23 | snu-quiqcl/iquip | https://api.github.com/repos/snu-quiqcl/iquip | opened | Pass the unittest without any error | test | ### Feature you want to implement
After updating QIWIS version, it causes too many unittest error due to global constants.
Thus, I will resolve this temporarily, not completely. (Just make the unittest passed) | 1.0 | Pass the unittest without any error - ### Feature you want to implement
After updating QIWIS version, it causes too many unittest error due to global constants.
Thus, I will resolve this temporarily, not completely. (Just make the unittest passed) | non_priority | pass the unittest without any error feature you want to implement after updating qiwis version it causes too many unittest error due to global constants thus i will resolve this temporarily not completely just make the unittest passed | 0 |
310,009 | 23,317,076,590 | IssuesEvent | 2022-08-08 13:24:32 | galasa-dev/projectmanagement | https://api.github.com/repos/galasa-dev/projectmanagement | closed | Create page structure and template for blogs in galasa.dev | documentation | A series of blogs is being created and these need to be hosted on galasa.dev
Blogs can be created in galasa-dev repository and published on demand outside of release cycle
Need to include structure of page, blogs and url - kept simple initially. Also include guidelines on eg use of images, tagging etc for searchability
URL structure might be based on time eg year/month/article or name of author or could be done by area eg ecosystem / manager etc - to be investigated
Future works to include looking at more front end development eg filtering etc. Some design work already done on this area from previous piece of work. | 1.0 | Create page structure and template for blogs in galasa.dev - A series of blogs is being created and these need to be hosted on galasa.dev
Blogs can be created in galasa-dev repository and published on demand outside of release cycle
Need to include structure of page, blogs and url - kept simple initially. Also include guidelines on eg use of images, tagging etc for searchability
URL structure might be based on time eg year/month/article or name of author or could be done by area eg ecosystem / manager etc - to be investigated
Future works to include looking at more front end development eg filtering etc. Some design work already done on this area from previous piece of work. | non_priority | create page structure and template for blogs in galasa dev a series of blogs is being created and these need to be hosted on galasa dev blogs can be created in galasa dev repository and published on demand outside of release cycle need to include structure of page blogs and url kept simple initially also include guidelines on eg use of images tagging etc for searchability url structure might be based on time eg year month article or name of author or could be done by area eg ecosystem manager etc to be investigated future works to include looking at more front end development eg filtering etc some design work already done on this area from previous piece of work | 0 |
141,123 | 12,958,368,752 | IssuesEvent | 2020-07-20 11:15:33 | opencv/opencv | https://api.github.com/repos/opencv/opencv | closed | OpenCV in Android Studio's NDK fails with "undefined reference" error | category: documentation platform: android | ##### System information (version)
- OpenCV => :grey_question: 4.3 / 3.4
- Operating System / Platform => :grey_question: Linux Ubuntu 16.04
- Compiler => :grey_question: Android Studio (Gradle / Ninja / CMake / clang++)
##### Detailed description
I'm trying to use OpenCV on Android's NDK.
I have two similar environments - one integrated with OpenCV 4.3 and the other with OpenCV 3.4.
I created an Android C++ app.
For the 4.3 integration I followed [this](https://github.com/VlSomers/native-opencv-android-template) tutorial.
For the 3.4 integration I followed [this](https://github.com/leadrien/opencv_native_androidstudio) tutorial.
I have a very basic `native-lib.cpp` file (see below), which is trying to use `cv::imread`.
In my code I provide the last trial - which includes the `OpenCVLoader.initAsync` instance, but I also tried the `OpenCVLoader.initDebug` way and `System.loadLibrary("opencv_java4")`, but the error remains.
I'm aware of the following issues:
- https://github.com/opencv/opencv/issues/17282
- https://github.com/opencv/opencv/issues/15536
- https://github.com/opencv/opencv/issues/12074
- https://github.com/opencv/opencv/issues/9512
- https://github.com/opencv/opencv/issues/9437
and noticed the recent update regarding link issues (which I assumed was my problem):
- https://github.com/opencv/opencv/issues/17282
I tried to build for my SDK version or against libc++, as described in the following:
- https://stackoverflow.com/questions/51767214/android-studio-with-ndk-link-error-undefined-reference-to-stderr
- https://stackoverflow.com/questions/52436506/undefined-references-error-opencv-android-with-ndk-18-c-static
- https://stackoverflow.com/questions/52410712/ndk-problems-after-gnustl-has-been-removed-from-the-ndk-revision-r18/52436751#52436751
and noticed some other issues, which do not use exactly the same setup (for example, using ndk-build instead of cmake):
- https://stackoverflow.com/questions/14649710/opencv-with-android-ndk-undefined-references
but failed to find anything new.
When trying to run the app I get the following errors:
```
undefined reference to `cv::imread'
clang++: error: linker command failed with exit code 1 (use -v to see invocation)
ninja: build stopped: subcommand failed.
```
Isn't undefined reference a linker issue?
Did I forget a compiler flag or something?
##### Steps to reproduce
Follow one of the tutorials ([4.3 tutorial](https://github.com/VlSomers/native-opencv-android-template) or [3.4 tutorial](https://github.com/leadrien/opencv_native_androidstudio)) to integrate OpenCV library into Android Studio.
Create the following simple **native-lib.cpp**:
```
#include <jni.h>
#include <string>
#include <opencv2/core.hpp>
#include <opencv2/imgcodecs.hpp>
extern "C" JNIEXPORT jstring JNICALL
Java_com_ocv_MainActivity_ocvLoadImage(
JNIEnv *env,
jobject thiz) {
using namespace cv;
using namespace std;
Mat image;
string imageName = "/Pictures/images/image-001.jpg";
image = imread(imageName, IMREAD_COLOR);
std::string returnString = "OpenCV load image: ";
if (! image.empty()){
returnString.append(imageName);
}
return env -> NewStringUTF(returnString.c_str());
}
```
and call it from this simple **MainActivity.java**:
```
package com.ocv;
import androidx.appcompat.app.AppCompatActivity;
import android.os.Bundle;
import android.widget.TextView;
import android.util.Log;
import org.opencv.android.BaseLoaderCallback;
import org.opencv.android.LoaderCallbackInterface;
import org.opencv.android.OpenCVLoader;
import org.opencv.core.Mat;
public class MainActivity extends AppCompatActivity {
static {
System.loadLibrary("native-lib");
System.loadLibrary("opencv_java4");
}
@Override
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.activity_main);
}
private BaseLoaderCallback mLoaderCallback = new BaseLoaderCallback(this) {
@Override
public void onManagerConnected(int status) {
if (status == LoaderCallbackInterface.SUCCESS) {
TextView textView = findViewById(R.id.sample_text);
String displayString =
textView.getText() +
"\n" + "OpenCV loaded successfully via initAsync" +
"\n" + ocvLoadImage();
textView.setText(displayString);
} else {
super.onManagerConnected(status);
}
}
};
@Override
public void onResume()
{
super.onResume();
OpenCVLoader.initAsync(
OpenCVLoader.OPENCV_VERSION_3_4_0,
this,
mLoaderCallback);
}
public native String ocvLoadImage(String imagePath);
}
```
**NOTES**:
- When calling `OpenCVLoader.initAsync`, both the 4.3 and the 3.4 version use the `OPENCV_VERSION_3_4_0` flag, since `OPENCV_VERSION` on 4.3 results in an error. I also tried the `OpenCVLoader.initDebug` and it produces the same error.
- When commenting out the `image = imread` line in `native-lib.cpp`, the app runs OK, and returns the string (all cases).
the app's **build.gradle**:
```
externalNativeBuild {
cmake {
cppFlags "-frtti -fexceptions"
abiFilters 'arm64-v8a'
arguments "-DOpenCV_DIR=" + opencvsdk + "/sdk/native/jni"
}
}
...
packagingOptions {
pickFirst 'lib/arm64-v8a/libopencv_java4.so'
}
```
**CMakeLists.txt**:
```
cmake_minimum_required(VERSION 3.4.1)
include_directories(${OpenCV_DIR}/jni/include)
find_package(OpenCV 4.3
REQUIRED
java)
add_library(
native-lib
SHARED
native-lib.cpp )
find_library(
log-lib
log )
target_link_libraries( # Specifies the target library.
native-lib
${OpenCV_LIBRARIES}
${log-lib} )
```
##### Error
**ERROR**:
`undefined reference to "cv::imread"`
**CLANG++**:
`/path/to/Sdk/ndk/21.1.6352462/toolchains/llvm/prebuilt/linux-x86_64/bin/clang++ --target=aarch64-none-linux-android29 --gcc-toolchain=/path/to/Sdk/ndk/21.1.6352462/toolchains/llvm/prebuilt/linux-x86_64 --sysroot=/path/to/Sdk/ndk/21.1.6352462/toolchains/llvm/prebuilt/linux-x86_64/sysroot -fPIC -g -DANDROID -fdata-sections -ffunction-sections -funwind-tables -fstack-protector-strong -no-canonical-prefixes -D_FORTIFY_SOURCE=2 -Wformat -Werror=format-security -frtti -fexceptions -O0 -fno-limit-debug-info -Wl,--exclude-libs,libgcc.a -Wl,--exclude-libs,libgcc_real.a -Wl,--exclude-libs,libatomic.a -static-libstdc++ -Wl,--build-id -Wl,--fatal-warnings -Wl,--no-undefined -Qunused-arguments -shared -Wl,-soname,libnative-lib.so -o /path/to/app/build/intermediates/cmake/debug/obj/arm64-v8a/libnative-lib.so CMakeFiles/native-lib.dir/native-lib.cpp.o /path/to/opencv-4.3.0-android-sdk/OpenCV-android-sdk/sdk/native/libs/arm64-v8a/libopencv_java4.so /path/to/Sdk/ndk/21.1.6352462/toolchains/llvm/prebuilt/linux-x86_64/sysroot/usr/lib/aarch64-linux-android/29/liblog.so -ljnigraphics -llog -ldl -lz -latomic -lm`
| 1.0 | OpenCV in Android Studio's NDK fails with "undefined reference" error - ##### System information (version)
- OpenCV => :grey_question: 4.3 / 3.4
- Operating System / Platform => :grey_question: Linux Ubuntu 16.04
- Compiler => :grey_question: Android Studio (Gradle / Ninja / CMake / clang++)
##### Detailed description
I'm trying to use OpenCV on Android's NDK.
I have two similar environments - one integrated with OpenCV 4.3 and the other with OpenCV 3.4.
I created an Android C++ app.
For the 4.3 integration I followed [this](https://github.com/VlSomers/native-opencv-android-template) tutorial.
For the 3.4 integration I followed [this](https://github.com/leadrien/opencv_native_androidstudio) tutorial.
I have a very basic `native-lib.cpp` file (see below), which is trying to use `cv::imread`.
In my code I provide the last trial - which includes the `OpenCVLoader.initAsync` instance, but I also tried the `OpenCVLoader.initDebug` way and `System.loadLibrary("opencv_java4")`, but the error remains.
I'm aware of the following issues:
- https://github.com/opencv/opencv/issues/17282
- https://github.com/opencv/opencv/issues/15536
- https://github.com/opencv/opencv/issues/12074
- https://github.com/opencv/opencv/issues/9512
- https://github.com/opencv/opencv/issues/9437
and noticed the recent update regarding link issues (which I assumed was my problem):
- https://github.com/opencv/opencv/issues/17282
I tried to build for my SDK version or against libc++, as described in the following:
- https://stackoverflow.com/questions/51767214/android-studio-with-ndk-link-error-undefined-reference-to-stderr
- https://stackoverflow.com/questions/52436506/undefined-references-error-opencv-android-with-ndk-18-c-static
- https://stackoverflow.com/questions/52410712/ndk-problems-after-gnustl-has-been-removed-from-the-ndk-revision-r18/52436751#52436751
and noticed some other issues, which do not use exactly the same setup (for example, using ndk-build instead of cmake):
- https://stackoverflow.com/questions/14649710/opencv-with-android-ndk-undefined-references
but failed to find anything new.
When trying to run the app I get the following errors:
```
undefined reference to `cv::imread'
clang++: error: linker command failed with exit code 1 (use -v to see invocation)
ninja: build stopped: subcommand failed.
```
Isn't undefined reference a linker issue?
Did I forget a compiler flag or something?
##### Steps to reproduce
Follow one of the tutorials ([4.3 tutorial](https://github.com/VlSomers/native-opencv-android-template) or [3.4 tutorial](https://github.com/leadrien/opencv_native_androidstudio)) to integrate OpenCV library into Android Studio.
Create the following simple **native-lib.cpp**:
```
#include <jni.h>
#include <string>
#include <opencv2/core.hpp>
#include <opencv2/imgcodecs.hpp>
extern "C" JNIEXPORT jstring JNICALL
Java_com_ocv_MainActivity_ocvLoadImage(
JNIEnv *env,
jobject thiz) {
using namespace cv;
using namespace std;
Mat image;
string imageName = "/Pictures/images/image-001.jpg";
image = imread(imageName, IMREAD_COLOR);
std::string returnString = "OpenCV load image: ";
if (! image.empty()){
returnString.append(imageName);
}
return env -> NewStringUTF(returnString.c_str());
}
```
and call it from this simple **MainActivity.java**:
```
package com.ocv;
import androidx.appcompat.app.AppCompatActivity;
import android.os.Bundle;
import android.widget.TextView;
import android.util.Log;
import org.opencv.android.BaseLoaderCallback;
import org.opencv.android.LoaderCallbackInterface;
import org.opencv.android.OpenCVLoader;
import org.opencv.core.Mat;
public class MainActivity extends AppCompatActivity {
static {
System.loadLibrary("native-lib");
System.loadLibrary("opencv_java4");
}
@Override
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.activity_main);
}
private BaseLoaderCallback mLoaderCallback = new BaseLoaderCallback(this) {
@Override
public void onManagerConnected(int status) {
if (status == LoaderCallbackInterface.SUCCESS) {
TextView textView = findViewById(R.id.sample_text);
String displayString =
textView.getText() +
"\n" + "OpenCV loaded successfully via initAsync" +
"\n" + ocvLoadImage();
textView.setText(displayString);
} else {
super.onManagerConnected(status);
}
}
};
@Override
public void onResume()
{
super.onResume();
OpenCVLoader.initAsync(
OpenCVLoader.OPENCV_VERSION_3_4_0,
this,
mLoaderCallback);
}
public native String ocvLoadImage(String imagePath);
}
```
**NOTES**:
- When calling `OpenCVLoader.initAsync`, both the 4.3 and the 3.4 version use the `OPENCV_VERSION_3_4_0` flag, since `OPENCV_VERSION` on 4.3 results in an error. I also tried the `OpenCVLoader.initDebug` and it produces the same error.
- When commenting out the `image = imread` line in `native-lib.cpp`, the app runs OK, and returns the string (all cases).
the app's **build.gradle**:
```
externalNativeBuild {
cmake {
cppFlags "-frtti -fexceptions"
abiFilters 'arm64-v8a'
arguments "-DOpenCV_DIR=" + opencvsdk + "/sdk/native/jni"
}
}
...
packagingOptions {
pickFirst 'lib/arm64-v8a/libopencv_java4.so'
}
```
**CMakeLists.txt**:
```
cmake_minimum_required(VERSION 3.4.1)
include_directories(${OpenCV_DIR}/jni/include)
find_package(OpenCV 4.3
REQUIRED
java)
add_library(
native-lib
SHARED
native-lib.cpp )
find_library(
log-lib
log )
target_link_libraries( # Specifies the target library.
native-lib
${OpenCV_LIBRARIES}
${log-lib} )
```
##### Error
**ERROR**:
`undefined reference to "cv::imread"`
**CLANG++**:
`/path/to/Sdk/ndk/21.1.6352462/toolchains/llvm/prebuilt/linux-x86_64/bin/clang++ --target=aarch64-none-linux-android29 --gcc-toolchain=/path/to/Sdk/ndk/21.1.6352462/toolchains/llvm/prebuilt/linux-x86_64 --sysroot=/path/to/Sdk/ndk/21.1.6352462/toolchains/llvm/prebuilt/linux-x86_64/sysroot -fPIC -g -DANDROID -fdata-sections -ffunction-sections -funwind-tables -fstack-protector-strong -no-canonical-prefixes -D_FORTIFY_SOURCE=2 -Wformat -Werror=format-security -frtti -fexceptions -O0 -fno-limit-debug-info -Wl,--exclude-libs,libgcc.a -Wl,--exclude-libs,libgcc_real.a -Wl,--exclude-libs,libatomic.a -static-libstdc++ -Wl,--build-id -Wl,--fatal-warnings -Wl,--no-undefined -Qunused-arguments -shared -Wl,-soname,libnative-lib.so -o /path/to/app/build/intermediates/cmake/debug/obj/arm64-v8a/libnative-lib.so CMakeFiles/native-lib.dir/native-lib.cpp.o /path/to/opencv-4.3.0-android-sdk/OpenCV-android-sdk/sdk/native/libs/arm64-v8a/libopencv_java4.so /path/to/Sdk/ndk/21.1.6352462/toolchains/llvm/prebuilt/linux-x86_64/sysroot/usr/lib/aarch64-linux-android/29/liblog.so -ljnigraphics -llog -ldl -lz -latomic -lm`
| non_priority | opencv in android studio s ndk fails with undefined reference error system information version opencv grey question operating system platform grey question linux ubuntu compiler grey question android studio gradle ninja cmake clang detailed description i m trying to use opencv on android s ndk i have two similar environments one integrated with opencv and the other with opencv i created an android c app for the integration i followed tutorial for the integration i followed tutorial i have a very basic native lib cpp file see below which is trying to use cv imread in my code i provide the last trial which includes the opencvloader initasync instance but i also tried the opencvloader initdebug way and system loadlibrary opencv but the error remains i m aware of the following issues and noticed the recent update regarding link issues which i assumed was my problem i tried to build for my sdk version or against libc as described in the following and noticed some other issues which do not use exactly the same setup for example using ndk build instead of cmake but failed to find anything new when trying to run the app i get the following errors undefined reference to cv imread clang error linker command failed with exit code use v to see invocation ninja build stopped subcommand failed isn t undefined reference a linker issue did i forget a compiler flag or something steps to reproduce follow one of the tutorials or to integrate opencv library into android studio create the following simple native lib cpp include include include include extern c jniexport jstring jnicall java com ocv mainactivity ocvloadimage jnienv env jobject thiz using namespace cv using namespace std mat image string imagename pictures images image jpg image imread imagename imread color std string returnstring opencv load image if image empty returnstring append imagename return env newstringutf returnstring c str and call it from this simple mainactivity java package com ocv import androidx appcompat app appcompatactivity import android os bundle import android widget textview import android util log import org opencv android baseloadercallback import org opencv android loadercallbackinterface import org opencv android opencvloader import org opencv core mat public class mainactivity extends appcompatactivity static system loadlibrary native lib system loadlibrary opencv override protected void oncreate bundle savedinstancestate super oncreate savedinstancestate setcontentview r layout activity main private baseloadercallback mloadercallback new baseloadercallback this override public void onmanagerconnected int status if status loadercallbackinterface success textview textview findviewbyid r id sample text string displaystring textview gettext n opencv loaded successfully via initasync n ocvloadimage textview settext displaystring else super onmanagerconnected status override public void onresume super onresume opencvloader initasync opencvloader opencv version this mloadercallback public native string ocvloadimage string imagepath notes when calling opencvloader initasync both the and the version use the opencv version flag since opencv version on results in an error i also tried the opencvloader initdebug and it produces the same error when commenting out the image imread line in native lib cpp the app runs ok and returns the string all cases the app s build gradle externalnativebuild cmake cppflags frtti fexceptions abifilters arguments dopencv dir opencvsdk sdk native jni packagingoptions pickfirst lib libopencv so cmakelists txt cmake minimum required version include directories opencv dir jni include find package opencv required java add library native lib shared native lib cpp find library log lib log target link libraries specifies the target library native lib opencv libraries log lib error error undefined reference to cv imread clang path to sdk ndk toolchains llvm prebuilt linux bin clang target none linux gcc toolchain path to sdk ndk toolchains llvm prebuilt linux sysroot path to sdk ndk toolchains llvm prebuilt linux sysroot fpic g dandroid fdata sections ffunction sections funwind tables fstack protector strong no canonical prefixes d fortify source wformat werror format security frtti fexceptions fno limit debug info wl exclude libs libgcc a wl exclude libs libgcc real a wl exclude libs libatomic a static libstdc wl build id wl fatal warnings wl no undefined qunused arguments shared wl soname libnative lib so o path to app build intermediates cmake debug obj libnative lib so cmakefiles native lib dir native lib cpp o path to opencv android sdk opencv android sdk sdk native libs libopencv so path to sdk ndk toolchains llvm prebuilt linux sysroot usr lib linux android liblog so ljnigraphics llog ldl lz latomic lm | 0 |
249,577 | 26,954,452,180 | IssuesEvent | 2023-02-08 14:02:09 | simplycubed/terraform-google-static-assets | https://api.github.com/repos/simplycubed/terraform-google-static-assets | closed | CVE-2022-1996 (High) detected in github.com/emicklei/go-restful/v3-v3.8.0 - autoclosed | security vulnerability | ## CVE-2022-1996 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>github.com/emicklei/go-restful/v3-v3.8.0</b></p></summary>
<p>package for building REST-style Web Services using Go</p>
<p>Library home page: <a href="https://proxy.golang.org/github.com/emicklei/go-restful/v3/@v/v3.8.0.zip">https://proxy.golang.org/github.com/emicklei/go-restful/v3/@v/v3.8.0.zip</a></p>
<p>
Dependency Hierarchy:
- github.com/gruntwork-io/terratest-v0.40.17 (Root Library)
- k8s.io/client-go-v0.24.2
- k8s.io/kube-openapi
- :x: **github.com/emicklei/go-restful/v3-v3.8.0** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/simplycubed/terraform-google-static-assets/commit/e49e2f33b77657ce4ab7eac9abebafc4a1fd18ba">e49e2f33b77657ce4ab7eac9abebafc4a1fd18ba</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Authorization Bypass Through User-Controlled Key in GitHub repository emicklei/go-restful prior to v3.8.0.
<p>Publish Date: 2022-06-08
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-1996>CVE-2022-1996</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1996">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1996</a></p>
<p>Release Date: 2022-06-08</p>
<p>Fix Resolution: v3.8.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2022-1996 (High) detected in github.com/emicklei/go-restful/v3-v3.8.0 - autoclosed - ## CVE-2022-1996 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>github.com/emicklei/go-restful/v3-v3.8.0</b></p></summary>
<p>package for building REST-style Web Services using Go</p>
<p>Library home page: <a href="https://proxy.golang.org/github.com/emicklei/go-restful/v3/@v/v3.8.0.zip">https://proxy.golang.org/github.com/emicklei/go-restful/v3/@v/v3.8.0.zip</a></p>
<p>
Dependency Hierarchy:
- github.com/gruntwork-io/terratest-v0.40.17 (Root Library)
- k8s.io/client-go-v0.24.2
- k8s.io/kube-openapi
- :x: **github.com/emicklei/go-restful/v3-v3.8.0** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/simplycubed/terraform-google-static-assets/commit/e49e2f33b77657ce4ab7eac9abebafc4a1fd18ba">e49e2f33b77657ce4ab7eac9abebafc4a1fd18ba</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Authorization Bypass Through User-Controlled Key in GitHub repository emicklei/go-restful prior to v3.8.0.
<p>Publish Date: 2022-06-08
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-1996>CVE-2022-1996</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1996">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1996</a></p>
<p>Release Date: 2022-06-08</p>
<p>Fix Resolution: v3.8.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve high detected in github com emicklei go restful autoclosed cve high severity vulnerability vulnerable library github com emicklei go restful package for building rest style web services using go library home page a href dependency hierarchy github com gruntwork io terratest root library io client go io kube openapi x github com emicklei go restful vulnerable library found in head commit a href found in base branch master vulnerability details authorization bypass through user controlled key in github repository emicklei go restful prior to publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with mend | 0 |
5,058 | 3,899,771,987 | IssuesEvent | 2016-04-17 23:01:44 | lionheart/openradar-mirror | https://api.github.com/repos/lionheart/openradar-mirror | opened | 13067395: Keynote 5.3: transition delay values less than 0.3 s ignored | classification:ui/usability reproducible:always | #### Description
Summary:
If you set the transition to "automatically", you can set a delay of 0.5, 0.4 and 0.3s and it will work. If you set 0.2 or 0.1 the change will be ignored.
Steps to Reproduce:
1. Set auto transition delay to 0.1
2. click onto another object
3. click back to the object
Expected Results:
auto transition delay should be 0.1
Actual Results:
auto transition delay is whatever it was before.
Regression:
I think this has happened for some time.
-
Product Version: Keynote 5.3 (1170)
Created: 2013-01-23T03:38:58.090748
Originated: 2016-04-17T00:00:00
Open Radar Link: http://www.openradar.me/13067395 | True | 13067395: Keynote 5.3: transition delay values less than 0.3 s ignored - #### Description
Summary:
If you set the transition to "automatically", you can set a delay of 0.5, 0.4 and 0.3s and it will work. If you set 0.2 or 0.1 the change will be ignored.
Steps to Reproduce:
1. Set auto transition delay to 0.1
2. click onto another object
3. click back to the object
Expected Results:
auto transition delay should be 0.1
Actual Results:
auto transition delay is whatever it was before.
Regression:
I think this has happened for some time.
-
Product Version: Keynote 5.3 (1170)
Created: 2013-01-23T03:38:58.090748
Originated: 2016-04-17T00:00:00
Open Radar Link: http://www.openradar.me/13067395 | non_priority | keynote transition delay values less than s ignored description summary if you set the transition to automatically you can set a delay of and and it will work if you set or the change will be ignored steps to reproduce set auto transition delay to click onto another object click back to the object expected results auto transition delay should be actual results auto transition delay is whatever it was before regression i think this has happened for some time product version keynote created originated open radar link | 0 |
232,029 | 25,564,359,176 | IssuesEvent | 2022-11-30 13:15:40 | hygieia/hygieia-artifact-artifactory-collector | https://api.github.com/repos/hygieia/hygieia-artifact-artifactory-collector | opened | CVE-2022-31692 (High) detected in spring-security-core-5.6.6.jar | security vulnerability | ## CVE-2022-31692 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>spring-security-core-5.6.6.jar</b></p></summary>
<p>Spring Security</p>
<p>Library home page: <a href="https://spring.io/projects/spring-security">https://spring.io/projects/spring-security</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/springframework/security/spring-security-core/5.6.6/spring-security-core-5.6.6.jar</p>
<p>
Dependency Hierarchy:
- core-4.0.1.jar (Root Library)
- spring-boot-starter-security-2.7.0.jar
- spring-security-config-5.6.6.jar
- :x: **spring-security-core-5.6.6.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/hygieia/hygieia-artifact-artifactory-collector/commit/4ab95b0cf6018bd3df942aa2f915655966d4fa9a">4ab95b0cf6018bd3df942aa2f915655966d4fa9a</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Spring Security, versions 5.7 prior to 5.7.5 and 5.6 prior to 5.6.9 could be susceptible to authorization rules bypass via forward or include dispatcher types. Specifically, an application is vulnerable when all of the following are true: The application expects that Spring Security applies security to forward and include dispatcher types. The application uses the AuthorizationFilter either manually or via the authorizeHttpRequests() method. The application configures the FilterChainProxy to apply to forward and/or include requests (e.g. spring.security.filter.dispatcher-types = request, error, async, forward, include). The application may forward or include the request to a higher privilege-secured endpoint.The application configures Spring Security to apply to every dispatcher type via authorizeHttpRequests().shouldFilterAllDispatcherTypes(true)
<p>Publish Date: 2022-10-31
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-31692>CVE-2022-31692</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-mmmh-wcxm-2wr4">https://github.com/advisories/GHSA-mmmh-wcxm-2wr4</a></p>
<p>Release Date: 2022-10-31</p>
<p>Fix Resolution: org.springframework.security:spring-security-core:5.6.9,5.7.5</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2022-31692 (High) detected in spring-security-core-5.6.6.jar - ## CVE-2022-31692 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>spring-security-core-5.6.6.jar</b></p></summary>
<p>Spring Security</p>
<p>Library home page: <a href="https://spring.io/projects/spring-security">https://spring.io/projects/spring-security</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/springframework/security/spring-security-core/5.6.6/spring-security-core-5.6.6.jar</p>
<p>
Dependency Hierarchy:
- core-4.0.1.jar (Root Library)
- spring-boot-starter-security-2.7.0.jar
- spring-security-config-5.6.6.jar
- :x: **spring-security-core-5.6.6.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/hygieia/hygieia-artifact-artifactory-collector/commit/4ab95b0cf6018bd3df942aa2f915655966d4fa9a">4ab95b0cf6018bd3df942aa2f915655966d4fa9a</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Spring Security, versions 5.7 prior to 5.7.5 and 5.6 prior to 5.6.9 could be susceptible to authorization rules bypass via forward or include dispatcher types. Specifically, an application is vulnerable when all of the following are true: The application expects that Spring Security applies security to forward and include dispatcher types. The application uses the AuthorizationFilter either manually or via the authorizeHttpRequests() method. The application configures the FilterChainProxy to apply to forward and/or include requests (e.g. spring.security.filter.dispatcher-types = request, error, async, forward, include). The application may forward or include the request to a higher privilege-secured endpoint.The application configures Spring Security to apply to every dispatcher type via authorizeHttpRequests().shouldFilterAllDispatcherTypes(true)
<p>Publish Date: 2022-10-31
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-31692>CVE-2022-31692</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-mmmh-wcxm-2wr4">https://github.com/advisories/GHSA-mmmh-wcxm-2wr4</a></p>
<p>Release Date: 2022-10-31</p>
<p>Fix Resolution: org.springframework.security:spring-security-core:5.6.9,5.7.5</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve high detected in spring security core jar cve high severity vulnerability vulnerable library spring security core jar spring security library home page a href path to dependency file pom xml path to vulnerable library home wss scanner repository org springframework security spring security core spring security core jar dependency hierarchy core jar root library spring boot starter security jar spring security config jar x spring security core jar vulnerable library found in head commit a href found in base branch master vulnerability details spring security versions prior to and prior to could be susceptible to authorization rules bypass via forward or include dispatcher types specifically an application is vulnerable when all of the following are true the application expects that spring security applies security to forward and include dispatcher types the application uses the authorizationfilter either manually or via the authorizehttprequests method the application configures the filterchainproxy to apply to forward and or include requests e g spring security filter dispatcher types request error async forward include the application may forward or include the request to a higher privilege secured endpoint the application configures spring security to apply to every dispatcher type via authorizehttprequests shouldfilteralldispatchertypes true publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution org springframework security spring security core step up your open source security game with mend | 0 |
15,813 | 3,485,360,786 | IssuesEvent | 2015-12-31 05:33:13 | destroytoday/Dwarf | https://api.github.com/repos/destroytoday/Dwarf | closed | Issues with Guides | Linux-only To Fix To Test | I found a number of issues with these:
1. I can't drag a horizontal guide to my other (non-active) monitor.
2. I can't create a horizontal guide that spans the width of both monitors.
3. Cutting (Crtrl+X) a guide works, pasting (Ctrl+V) rarely does paste a guide, and when it does, it doesn't restore it's X,Y properties | 1.0 | Issues with Guides - I found a number of issues with these:
1. I can't drag a horizontal guide to my other (non-active) monitor.
2. I can't create a horizontal guide that spans the width of both monitors.
3. Cutting (Crtrl+X) a guide works, pasting (Ctrl+V) rarely does paste a guide, and when it does, it doesn't restore it's X,Y properties | non_priority | issues with guides i found a number of issues with these i can t drag a horizontal guide to my other non active monitor i can t create a horizontal guide that spans the width of both monitors cutting crtrl x a guide works pasting ctrl v rarely does paste a guide and when it does it doesn t restore it s x y properties | 0 |
235,581 | 19,401,222,012 | IssuesEvent | 2021-12-19 07:57:45 | cockroachdb/cockroach | https://api.github.com/repos/cockroachdb/cockroach | opened | roachtest: sqlsmith/setup=tpch-sf1/setting=no-ddl failed | C-test-failure O-robot O-roachtest branch-master release-blocker | roachtest.sqlsmith/setup=tpch-sf1/setting=no-ddl [failed](https://teamcity.cockroachdb.com/viewLog.html?buildId=3949693&tab=buildLog) with [artifacts](https://teamcity.cockroachdb.com/viewLog.html?buildId=3949693&tab=artifacts#/sqlsmith/setup=tpch-sf1/setting=no-ddl) on master @ [4cbe795c7f8c36c007c3ca1250367cb181f5ca0c](https://github.com/cockroachdb/cockroach/commits/4cbe795c7f8c36c007c3ca1250367cb181f5ca0c):
```
The test failed on branch=master, cloud=gce:
test artifacts and logs in: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/artifacts/sqlsmith/setup=tpch-sf1/setting=no-ddl/run_1
sqlsmith.go:258,sqlsmith.go:297,test_runner.go:779: error: pq: internal error: cannot map variable 38 to an indexed var
stmt:
INSERT
INTO
defaultdb.public.part AS tab_454
(p_comment, p_partkey, p_name, p_mfgr, p_brand, p_type, p_size, p_container, p_retailprice)
SELECT
tab_456.p_comment AS col_855,
tab_455.l_suppkey AS col_856,
tab_455.l_linestatus AS col_857,
tab_456.p_name AS col_858,
tab_456.p_name AS col_859,
tab_455.l_shipinstruct AS col_860,
crdb_internal.trace_id()::INT8 AS col_861,
tab_456.p_comment AS col_862,
NULL AS col_863
FROM
defaultdb.public.lineitem@[0] AS tab_455, defaultdb.public.part@primary AS tab_456
WHERE
false;
```
<details><summary>Help</summary>
<p>
See: [roachtest README](https://github.com/cockroachdb/cockroach/blob/master/pkg/cmd/roachtest/README.md)
See: [How To Investigate \(internal\)](https://cockroachlabs.atlassian.net/l/c/SSSBr8c7)
</p>
</details>
/cc @cockroachdb/sql-queries
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*sqlsmith/setup=tpch-sf1/setting=no-ddl.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
| 2.0 | roachtest: sqlsmith/setup=tpch-sf1/setting=no-ddl failed - roachtest.sqlsmith/setup=tpch-sf1/setting=no-ddl [failed](https://teamcity.cockroachdb.com/viewLog.html?buildId=3949693&tab=buildLog) with [artifacts](https://teamcity.cockroachdb.com/viewLog.html?buildId=3949693&tab=artifacts#/sqlsmith/setup=tpch-sf1/setting=no-ddl) on master @ [4cbe795c7f8c36c007c3ca1250367cb181f5ca0c](https://github.com/cockroachdb/cockroach/commits/4cbe795c7f8c36c007c3ca1250367cb181f5ca0c):
```
The test failed on branch=master, cloud=gce:
test artifacts and logs in: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/artifacts/sqlsmith/setup=tpch-sf1/setting=no-ddl/run_1
sqlsmith.go:258,sqlsmith.go:297,test_runner.go:779: error: pq: internal error: cannot map variable 38 to an indexed var
stmt:
INSERT
INTO
defaultdb.public.part AS tab_454
(p_comment, p_partkey, p_name, p_mfgr, p_brand, p_type, p_size, p_container, p_retailprice)
SELECT
tab_456.p_comment AS col_855,
tab_455.l_suppkey AS col_856,
tab_455.l_linestatus AS col_857,
tab_456.p_name AS col_858,
tab_456.p_name AS col_859,
tab_455.l_shipinstruct AS col_860,
crdb_internal.trace_id()::INT8 AS col_861,
tab_456.p_comment AS col_862,
NULL AS col_863
FROM
defaultdb.public.lineitem@[0] AS tab_455, defaultdb.public.part@primary AS tab_456
WHERE
false;
```
<details><summary>Help</summary>
<p>
See: [roachtest README](https://github.com/cockroachdb/cockroach/blob/master/pkg/cmd/roachtest/README.md)
See: [How To Investigate \(internal\)](https://cockroachlabs.atlassian.net/l/c/SSSBr8c7)
</p>
</details>
/cc @cockroachdb/sql-queries
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*sqlsmith/setup=tpch-sf1/setting=no-ddl.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
| non_priority | roachtest sqlsmith setup tpch setting no ddl failed roachtest sqlsmith setup tpch setting no ddl with on master the test failed on branch master cloud gce test artifacts and logs in home agent work go src github com cockroachdb cockroach artifacts sqlsmith setup tpch setting no ddl run sqlsmith go sqlsmith go test runner go error pq internal error cannot map variable to an indexed var stmt insert into defaultdb public part as tab p comment p partkey p name p mfgr p brand p type p size p container p retailprice select tab p comment as col tab l suppkey as col tab l linestatus as col tab p name as col tab p name as col tab l shipinstruct as col crdb internal trace id as col tab p comment as col null as col from defaultdb public lineitem as tab defaultdb public part primary as tab where false help see see cc cockroachdb sql queries | 0 |
74,941 | 9,813,589,873 | IssuesEvent | 2019-06-13 08:21:06 | aserebryakov/vim-todo-lists | https://api.github.com/repos/aserebryakov/vim-todo-lists | closed | Swap o and O commands | documentation | To more model how normal vim works "O" would insert a line above while this program does it opposite, consider changing to more closely model vim? | 1.0 | Swap o and O commands - To more model how normal vim works "O" would insert a line above while this program does it opposite, consider changing to more closely model vim? | non_priority | swap o and o commands to more model how normal vim works o would insert a line above while this program does it opposite consider changing to more closely model vim | 0 |
127,173 | 18,010,317,724 | IssuesEvent | 2021-09-16 07:50:35 | maddyCode23/linux-4.1.15 | https://api.github.com/repos/maddyCode23/linux-4.1.15 | opened | CVE-2020-28097 (Medium) detected in linux-stable-rtv4.1.33 | security vulnerability | ## CVE-2020-28097 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux-stable-rtv4.1.33</b></p></summary>
<p>
<p>Julia Cartwright's fork of linux-stable-rt.git</p>
<p>Library home page: <a href=https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git>https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git</a></p>
<p>Found in HEAD commit: <a href="https://github.com/maddyCode23/linux-4.1.15/commit/f1f3d2b150be669390b32dfea28e773471bdd6e7">f1f3d2b150be669390b32dfea28e773471bdd6e7</a></p>
</p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (2)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/drivers/video/console/vgacon.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/drivers/video/console/vgacon.c</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The vgacon subsystem in the Linux kernel before 5.8.10 mishandles software scrollback. There is a vgacon_scrolldelta out-of-bounds read, aka CID-973c096f6a85.
<p>Publish Date: 2021-06-24
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-28097>CVE-2020-28097</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.9</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Physical
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-20178">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-20178</a></p>
<p>Release Date: 2021-06-24</p>
<p>Fix Resolution: v4.4.237, v4.19.146, v4.14.199, v5.4.66, v5.8.10</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2020-28097 (Medium) detected in linux-stable-rtv4.1.33 - ## CVE-2020-28097 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux-stable-rtv4.1.33</b></p></summary>
<p>
<p>Julia Cartwright's fork of linux-stable-rt.git</p>
<p>Library home page: <a href=https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git>https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git</a></p>
<p>Found in HEAD commit: <a href="https://github.com/maddyCode23/linux-4.1.15/commit/f1f3d2b150be669390b32dfea28e773471bdd6e7">f1f3d2b150be669390b32dfea28e773471bdd6e7</a></p>
</p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (2)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/drivers/video/console/vgacon.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/drivers/video/console/vgacon.c</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The vgacon subsystem in the Linux kernel before 5.8.10 mishandles software scrollback. There is a vgacon_scrolldelta out-of-bounds read, aka CID-973c096f6a85.
<p>Publish Date: 2021-06-24
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-28097>CVE-2020-28097</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.9</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Physical
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-20178">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-20178</a></p>
<p>Release Date: 2021-06-24</p>
<p>Fix Resolution: v4.4.237, v4.19.146, v4.14.199, v5.4.66, v5.8.10</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve medium detected in linux stable cve medium severity vulnerability vulnerable library linux stable julia cartwright s fork of linux stable rt git library home page a href found in head commit a href vulnerable source files drivers video console vgacon c drivers video console vgacon c vulnerability details the vgacon subsystem in the linux kernel before mishandles software scrollback there is a vgacon scrolldelta out of bounds read aka cid publish date url a href cvss score details base score metrics exploitability metrics attack vector physical attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact high integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource | 0 |
192,280 | 22,215,926,818 | IssuesEvent | 2022-06-08 01:37:53 | madhans23/linux-4.1.15 | https://api.github.com/repos/madhans23/linux-4.1.15 | reopened | CVE-2018-5953 (Medium) detected in linux-stable-rtv4.1.33 | security vulnerability | ## CVE-2018-5953 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux-stable-rtv4.1.33</b></p></summary>
<p>
<p>Julia Cartwright's fork of linux-stable-rt.git</p>
<p>Library home page: <a href=https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git>https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git</a></p>
<p>Found in HEAD commit: <a href="https://github.com/madhans23/linux-4.1.15/commit/f9d19044b0eef1965f9bc412d7d9e579b74ec968">f9d19044b0eef1965f9bc412d7d9e579b74ec968</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (2)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/lib/swiotlb.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/lib/swiotlb.c</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The swiotlb_print_info function in lib/swiotlb.c in the Linux kernel through 4.14.14 allows local users to obtain sensitive address information by reading dmesg data from a "software IO TLB" printk call.
<p>Publish Date: 2018-08-07
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-5953>CVE-2018-5953</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2018-5953">https://nvd.nist.gov/vuln/detail/CVE-2018-5953</a></p>
<p>Release Date: 2018-08-07</p>
<p>Fix Resolution: linux-yocto - 5.4.20+gitAUTOINC+c11911d4d1_f4d7dbafb1,4.8.24+gitAUTOINC+c84532b647_f6329fd287</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2018-5953 (Medium) detected in linux-stable-rtv4.1.33 - ## CVE-2018-5953 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux-stable-rtv4.1.33</b></p></summary>
<p>
<p>Julia Cartwright's fork of linux-stable-rt.git</p>
<p>Library home page: <a href=https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git>https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git</a></p>
<p>Found in HEAD commit: <a href="https://github.com/madhans23/linux-4.1.15/commit/f9d19044b0eef1965f9bc412d7d9e579b74ec968">f9d19044b0eef1965f9bc412d7d9e579b74ec968</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (2)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/lib/swiotlb.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/lib/swiotlb.c</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The swiotlb_print_info function in lib/swiotlb.c in the Linux kernel through 4.14.14 allows local users to obtain sensitive address information by reading dmesg data from a "software IO TLB" printk call.
<p>Publish Date: 2018-08-07
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-5953>CVE-2018-5953</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2018-5953">https://nvd.nist.gov/vuln/detail/CVE-2018-5953</a></p>
<p>Release Date: 2018-08-07</p>
<p>Fix Resolution: linux-yocto - 5.4.20+gitAUTOINC+c11911d4d1_f4d7dbafb1,4.8.24+gitAUTOINC+c84532b647_f6329fd287</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve medium detected in linux stable cve medium severity vulnerability vulnerable library linux stable julia cartwright s fork of linux stable rt git library home page a href found in head commit a href found in base branch master vulnerable source files lib swiotlb c lib swiotlb c vulnerability details the swiotlb print info function in lib swiotlb c in the linux kernel through allows local users to obtain sensitive address information by reading dmesg data from a software io tlb printk call publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact high integrity impact none availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution linux yocto gitautoinc gitautoinc step up your open source security game with whitesource | 0 |
218,709 | 17,017,253,078 | IssuesEvent | 2021-07-02 13:44:34 | sveltejs/kit | https://api.github.com/repos/sveltejs/kit | closed | Static Adapter pnpm test fails when path to Node has spaces in on Windows | bug tests windows | **Describe the bug**
Running pnpm test on Windows when node is installed in "C:\\Program Files\\nodejs\\node.exe" fails due to the space in the path.
Looks like spawn function
https://github.com/sveltejs/kit/blob/0d69e556851a02678f8694f948517fc6ec85df86/packages/adapter-static/test/utils.js#L71
is using spaces to determine arguments.
`const [cmd, ...args] = str.split(' ');`
Not sure what's the nicest fix for this is as could get a bit messy?
**Logs**
```
Error: spawn "C:\Program ENOENT
at Process.ChildProcess._handle.onexit (internal/child_process.js:269:19)
at onErrorNT (internal/child_process.js:465:16)
at processTicksAndRejections (internal/process/task_queues.js:80:21) {
errno: -4058,
code: 'ENOENT',
syscall: 'spawn "C:\\Program',
path: '"C:\\Program',
spawnargs: [
'Files\\nodejs\\node.exe',
'C:\\Users\\SDE\\WebstormProjects\\teemu\\packages\\kit\\packages\\kit\\src\\cli.js',
'build"'
]
}
```
**To Reproduce**
Run pnpm test in kit folder
**Stacktraces**
<details>
<summary>Stack trace</summary>
```
TypeError: Cannot read property 'close' of undefined
at file:///C:/Users/SDE/WebstormProjects/teemu/packages/kit/packages/adapter-static/test/utils.js:59:18
at Number.runner (file:///C:/Users/SDE/WebstormProjects/teemu/packages/kit/node_modules/.pnpm/uvu@0.5.1/node_modules/uvu/dist/index.mjs:90:29)
at processTicksAndRejections (internal/process/task_queues.js:93:5)
at async exec (file:///C:/Users/SDE/WebstormProjects/teemu/packages/kit/node_modules/.pnpm/uvu@0.5.1/node_modules/uvu/dist/index.mjs:131:33)
at async Module.run (file:///C:/Users/SDE/WebstormProjects/teemu/packages/kit/node_modules/.pnpm/uvu@0.5.1/node_modules/uvu/run/index.mjs:13:2)
```
</details>
Windows 10 with Node v14.16.0
<details>
<summary>Diagnostics</summary>
System:
OS: Windows 10 10.0.19043
CPU: (4) x64 Intel(R) Core(TM) i5-4570 CPU @ 3.20GHz
Memory: 6.53 GB / 15.91 GB
Binaries:
Node: 14.16.0 - C:\Program Files\nodejs\node.EXE
Yarn: 1.22.4 - ~\AppData\Roaming\npm\yarn.CMD
npm: 6.14.11 - C:\Program Files\nodejs\npm.CMD
Browsers:
Chrome: 91.0.4472.124
Edge: Spartan (44.19041.1023.0), Chromium (91.0.864.59)
Internet Explorer: 11.0.19041.1
</details>
**Severity**
Not irritating or annoying. Just needs fixing at some point.
| 1.0 | Static Adapter pnpm test fails when path to Node has spaces in on Windows - **Describe the bug**
Running pnpm test on Windows when node is installed in "C:\\Program Files\\nodejs\\node.exe" fails due to the space in the path.
Looks like spawn function
https://github.com/sveltejs/kit/blob/0d69e556851a02678f8694f948517fc6ec85df86/packages/adapter-static/test/utils.js#L71
is using spaces to determine arguments.
`const [cmd, ...args] = str.split(' ');`
Not sure what's the nicest fix for this is as could get a bit messy?
**Logs**
```
Error: spawn "C:\Program ENOENT
at Process.ChildProcess._handle.onexit (internal/child_process.js:269:19)
at onErrorNT (internal/child_process.js:465:16)
at processTicksAndRejections (internal/process/task_queues.js:80:21) {
errno: -4058,
code: 'ENOENT',
syscall: 'spawn "C:\\Program',
path: '"C:\\Program',
spawnargs: [
'Files\\nodejs\\node.exe',
'C:\\Users\\SDE\\WebstormProjects\\teemu\\packages\\kit\\packages\\kit\\src\\cli.js',
'build"'
]
}
```
**To Reproduce**
Run pnpm test in kit folder
**Stacktraces**
<details>
<summary>Stack trace</summary>
```
TypeError: Cannot read property 'close' of undefined
at file:///C:/Users/SDE/WebstormProjects/teemu/packages/kit/packages/adapter-static/test/utils.js:59:18
at Number.runner (file:///C:/Users/SDE/WebstormProjects/teemu/packages/kit/node_modules/.pnpm/uvu@0.5.1/node_modules/uvu/dist/index.mjs:90:29)
at processTicksAndRejections (internal/process/task_queues.js:93:5)
at async exec (file:///C:/Users/SDE/WebstormProjects/teemu/packages/kit/node_modules/.pnpm/uvu@0.5.1/node_modules/uvu/dist/index.mjs:131:33)
at async Module.run (file:///C:/Users/SDE/WebstormProjects/teemu/packages/kit/node_modules/.pnpm/uvu@0.5.1/node_modules/uvu/run/index.mjs:13:2)
```
</details>
Windows 10 with Node v14.16.0
<details>
<summary>Diagnostics</summary>
System:
OS: Windows 10 10.0.19043
CPU: (4) x64 Intel(R) Core(TM) i5-4570 CPU @ 3.20GHz
Memory: 6.53 GB / 15.91 GB
Binaries:
Node: 14.16.0 - C:\Program Files\nodejs\node.EXE
Yarn: 1.22.4 - ~\AppData\Roaming\npm\yarn.CMD
npm: 6.14.11 - C:\Program Files\nodejs\npm.CMD
Browsers:
Chrome: 91.0.4472.124
Edge: Spartan (44.19041.1023.0), Chromium (91.0.864.59)
Internet Explorer: 11.0.19041.1
</details>
**Severity**
Not irritating or annoying. Just needs fixing at some point.
| non_priority | static adapter pnpm test fails when path to node has spaces in on windows describe the bug running pnpm test on windows when node is installed in c program files nodejs node exe fails due to the space in the path looks like spawn function is using spaces to determine arguments const str split not sure what s the nicest fix for this is as could get a bit messy logs error spawn c program enoent at process childprocess handle onexit internal child process js at onerrornt internal child process js at processticksandrejections internal process task queues js errno code enoent syscall spawn c program path c program spawnargs files nodejs node exe c users sde webstormprojects teemu packages kit packages kit src cli js build to reproduce run pnpm test in kit folder stacktraces stack trace typeerror cannot read property close of undefined at file c users sde webstormprojects teemu packages kit packages adapter static test utils js at number runner file c users sde webstormprojects teemu packages kit node modules pnpm uvu node modules uvu dist index mjs at processticksandrejections internal process task queues js at async exec file c users sde webstormprojects teemu packages kit node modules pnpm uvu node modules uvu dist index mjs at async module run file c users sde webstormprojects teemu packages kit node modules pnpm uvu node modules uvu run index mjs windows with node diagnostics system os windows cpu intel r core tm cpu memory gb gb binaries node c program files nodejs node exe yarn appdata roaming npm yarn cmd npm c program files nodejs npm cmd browsers chrome edge spartan chromium internet explorer severity not irritating or annoying just needs fixing at some point | 0 |
164,117 | 20,364,331,326 | IssuesEvent | 2022-02-21 02:34:35 | n-devs/share-we-go-dev | https://api.github.com/repos/n-devs/share-we-go-dev | opened | CVE-2022-0639 (Medium) detected in url-parse-1.4.7.tgz | security vulnerability | ## CVE-2022-0639 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>url-parse-1.4.7.tgz</b></p></summary>
<p>Small footprint URL parser that works seamlessly across Node.js and browser environments</p>
<p>Library home page: <a href="https://registry.npmjs.org/url-parse/-/url-parse-1.4.7.tgz">https://registry.npmjs.org/url-parse/-/url-parse-1.4.7.tgz</a></p>
<p>Path to dependency file: /share_we_go/package.json</p>
<p>Path to vulnerable library: /tmp/git/share_we_go/node_modules/url-parse/package.json</p>
<p>
Dependency Hierarchy:
- webpack-dev-server-3.7.2.tgz (Root Library)
- sockjs-client-1.3.0.tgz
- :x: **url-parse-1.4.7.tgz** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Authorization Bypass Through User-Controlled Key in NPM url-parse prior to 1.5.7.
<p>Publish Date: 2022-02-17
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-0639>CVE-2022-0639</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0639">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0639</a></p>
<p>Release Date: 2022-02-17</p>
<p>Fix Resolution: url-parse - 1.5.7</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2022-0639 (Medium) detected in url-parse-1.4.7.tgz - ## CVE-2022-0639 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>url-parse-1.4.7.tgz</b></p></summary>
<p>Small footprint URL parser that works seamlessly across Node.js and browser environments</p>
<p>Library home page: <a href="https://registry.npmjs.org/url-parse/-/url-parse-1.4.7.tgz">https://registry.npmjs.org/url-parse/-/url-parse-1.4.7.tgz</a></p>
<p>Path to dependency file: /share_we_go/package.json</p>
<p>Path to vulnerable library: /tmp/git/share_we_go/node_modules/url-parse/package.json</p>
<p>
Dependency Hierarchy:
- webpack-dev-server-3.7.2.tgz (Root Library)
- sockjs-client-1.3.0.tgz
- :x: **url-parse-1.4.7.tgz** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Authorization Bypass Through User-Controlled Key in NPM url-parse prior to 1.5.7.
<p>Publish Date: 2022-02-17
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-0639>CVE-2022-0639</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0639">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0639</a></p>
<p>Release Date: 2022-02-17</p>
<p>Fix Resolution: url-parse - 1.5.7</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve medium detected in url parse tgz cve medium severity vulnerability vulnerable library url parse tgz small footprint url parser that works seamlessly across node js and browser environments library home page a href path to dependency file share we go package json path to vulnerable library tmp git share we go node modules url parse package json dependency hierarchy webpack dev server tgz root library sockjs client tgz x url parse tgz vulnerable library vulnerability details authorization bypass through user controlled key in npm url parse prior to publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact low integrity impact low availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution url parse step up your open source security game with whitesource | 0 |
107,701 | 13,503,188,318 | IssuesEvent | 2020-09-13 12:22:18 | pandas-dev/pandas | https://api.github.com/repos/pandas-dev/pandas | closed | BUG: when i merge two dataframes in pandas if the datatypes of columns are mismatched exception is raised | API Design Reshaping | - [ ] I have checked that this issue has not already been reported.
- [ ] I have confirmed this bug exists on the latest version of pandas.
- [ ] (optional) I have confirmed this bug exists on the master branch of pandas.
---
**Note**: Please read [this guide](https://matthewrocklin.com/blog/work/2018/02/28/minimal-bug-reports) detailing how to provide the necessary information for us to reproduce your bug.
#### Code Sample, a copy-pastable example
```python
# Your code here
import pandas as pd
data_right = [['Alex','10',100],['Bob','12',90],['Clarke','13.0',80]]
data_left =[[10.0],[12.0],[13.0]]
df_right = pd.DataFrame(data_right,columns=['Name','Age','score'])
df_left = pd.DataFrame(data_left,columns=['Age'])
df_result=df_left.merge(df_right,on='Age',how='inner')
print(df_result)
```
#### Problem description
[this should explain **why** the current behaviour is a problem and why the expected output is a better solution]
sometimes when I read from files in some storage .I am not sure of the datatype of a column . Hence I get an Exception while merging
#### Expected Output
What I Propose is we could have a parameter having ignore_data_type=true in the merge . When its true We could mandatorily cast the column of right_dataframe to the data type of left one and Proceed. Hence we could avoid this Exception.
#### Output of ``pd.show_versions()``
<details>
Age Name score
0 13.0 Clarke 80
[paste the output of ``pd.show_versions()`` here leaving a blank line after the details tag]
</details>
| 1.0 | BUG: when i merge two dataframes in pandas if the datatypes of columns are mismatched exception is raised - - [ ] I have checked that this issue has not already been reported.
- [ ] I have confirmed this bug exists on the latest version of pandas.
- [ ] (optional) I have confirmed this bug exists on the master branch of pandas.
---
**Note**: Please read [this guide](https://matthewrocklin.com/blog/work/2018/02/28/minimal-bug-reports) detailing how to provide the necessary information for us to reproduce your bug.
#### Code Sample, a copy-pastable example
```python
# Your code here
import pandas as pd
data_right = [['Alex','10',100],['Bob','12',90],['Clarke','13.0',80]]
data_left =[[10.0],[12.0],[13.0]]
df_right = pd.DataFrame(data_right,columns=['Name','Age','score'])
df_left = pd.DataFrame(data_left,columns=['Age'])
df_result=df_left.merge(df_right,on='Age',how='inner')
print(df_result)
```
#### Problem description
[this should explain **why** the current behaviour is a problem and why the expected output is a better solution]
sometimes when I read from files in some storage .I am not sure of the datatype of a column . Hence I get an Exception while merging
#### Expected Output
What I Propose is we could have a parameter having ignore_data_type=true in the merge . When its true We could mandatorily cast the column of right_dataframe to the data type of left one and Proceed. Hence we could avoid this Exception.
#### Output of ``pd.show_versions()``
<details>
Age Name score
0 13.0 Clarke 80
[paste the output of ``pd.show_versions()`` here leaving a blank line after the details tag]
</details>
| non_priority | bug when i merge two dataframes in pandas if the datatypes of columns are mismatched exception is raised i have checked that this issue has not already been reported i have confirmed this bug exists on the latest version of pandas optional i have confirmed this bug exists on the master branch of pandas note please read detailing how to provide the necessary information for us to reproduce your bug code sample a copy pastable example python your code here import pandas as pd data right data left df right pd dataframe data right columns df left pd dataframe data left columns df result df left merge df right on age how inner print df result problem description sometimes when i read from files in some storage i am not sure of the datatype of a column hence i get an exception while merging expected output what i propose is we could have a parameter having ignore data type true in the merge when its true we could mandatorily cast the column of right dataframe to the data type of left one and proceed hence we could avoid this exception output of pd show versions age name score clarke | 0 |
297,133 | 22,341,166,735 | IssuesEvent | 2022-06-15 01:02:30 | MichaelPetersen22/Solace | https://api.github.com/repos/MichaelPetersen22/Solace | opened | Create Readme and Additional Documentation on Application Usage | documentation | The application (for myself as well) could benefit from documentation on configuration, usage, setup, deployment, requirements etc. | 1.0 | Create Readme and Additional Documentation on Application Usage - The application (for myself as well) could benefit from documentation on configuration, usage, setup, deployment, requirements etc. | non_priority | create readme and additional documentation on application usage the application for myself as well could benefit from documentation on configuration usage setup deployment requirements etc | 0 |
63,156 | 6,827,816,605 | IssuesEvent | 2017-11-08 18:17:05 | bpmn-miwg/bpmn-miwg-test-suite | https://api.github.com/repos/bpmn-miwg/bpmn-miwg-test-suite | opened | Depiction of the Onboarding employee page labels on shape are not properly positioned | Test: C.4.0 | Shapes label in the C.4.0.3 file are off based on the reference schema | 1.0 | Depiction of the Onboarding employee page labels on shape are not properly positioned - Shapes label in the C.4.0.3 file are off based on the reference schema | non_priority | depiction of the onboarding employee page labels on shape are not properly positioned shapes label in the c file are off based on the reference schema | 0 |
6,006 | 21,880,639,301 | IssuesEvent | 2022-05-19 14:04:22 | gergelytakacs/AutomationShield | https://api.github.com/repos/gergelytakacs/AutomationShield | closed | LQ and more: LINPACK benchmark | AutomationShield common software | A LINPACK benchmark should be added to the timing and memory evaluation. See[ this ](https://en.wikipedia.org/wiki/LINPACK_benchmarks) for a start. Essentially it is about the solution of the set of linear equations given in the matrix form by Ax=b. | 1.0 | LQ and more: LINPACK benchmark - A LINPACK benchmark should be added to the timing and memory evaluation. See[ this ](https://en.wikipedia.org/wiki/LINPACK_benchmarks) for a start. Essentially it is about the solution of the set of linear equations given in the matrix form by Ax=b. | non_priority | lq and more linpack benchmark a linpack benchmark should be added to the timing and memory evaluation see for a start essentially it is about the solution of the set of linear equations given in the matrix form by ax b | 0 |
5,818 | 13,193,851,844 | IssuesEvent | 2020-08-13 15:51:22 | dfds/backstage | https://api.github.com/repos/dfds/backstage | closed | Agree with PO (grooming) on "developer experience roadmap": | Architecture | - [x] Create Capability.
- [ ] Create WebAPI. (dfds-web-api)
- [ ] Create WebHost.
- [x] Create AuthorizationServer.
- [x] Register application with AuthorizationServer.
- [x] Grant application permissions with AuthorizationServer. | 1.0 | Agree with PO (grooming) on "developer experience roadmap": - - [x] Create Capability.
- [ ] Create WebAPI. (dfds-web-api)
- [ ] Create WebHost.
- [x] Create AuthorizationServer.
- [x] Register application with AuthorizationServer.
- [x] Grant application permissions with AuthorizationServer. | non_priority | agree with po grooming on developer experience roadmap create capability create webapi dfds web api create webhost create authorizationserver register application with authorizationserver grant application permissions with authorizationserver | 0 |
80,564 | 10,024,170,346 | IssuesEvent | 2019-07-16 21:06:46 | ParabolInc/action | https://api.github.com/repos/ParabolInc/action | closed | Lo-fi design prototypes for Group phase including prompt categories | design enhancement | See #2557
### Acceptance Criteria (optional)
A lo-fi prototype we can send to users for feedback that:
- Shows current group layout, but with headers for each prompt and generated cards under each prompt
- Shows cards in grid, but automatically color-coded by prompt. Sort cards by prompt
- Figma prototype link generated for each
- **Estimated effort:** 12 points ([see CONTRIBUTING.md](https://github.com/ParabolInc/action/blob/master/CONTRIBUTING.md#points-and-sizes))
| 1.0 | Lo-fi design prototypes for Group phase including prompt categories - See #2557
### Acceptance Criteria (optional)
A lo-fi prototype we can send to users for feedback that:
- Shows current group layout, but with headers for each prompt and generated cards under each prompt
- Shows cards in grid, but automatically color-coded by prompt. Sort cards by prompt
- Figma prototype link generated for each
- **Estimated effort:** 12 points ([see CONTRIBUTING.md](https://github.com/ParabolInc/action/blob/master/CONTRIBUTING.md#points-and-sizes))
| non_priority | lo fi design prototypes for group phase including prompt categories see acceptance criteria optional a lo fi prototype we can send to users for feedback that shows current group layout but with headers for each prompt and generated cards under each prompt shows cards in grid but automatically color coded by prompt sort cards by prompt figma prototype link generated for each estimated effort points | 0 |
288,226 | 31,861,196,782 | IssuesEvent | 2023-09-15 11:02:47 | nidhi7598/linux-v4.19.72_CVE-2022-3564 | https://api.github.com/repos/nidhi7598/linux-v4.19.72_CVE-2022-3564 | opened | CVE-2023-3338 (Medium) detected in multiple libraries | Mend: dependency security vulnerability | ## CVE-2023-3338 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>linuxlinux-4.19.294</b>, <b>linuxlinux-4.19.294</b>, <b>linuxlinux-4.19.294</b>, <b>linuxlinux-4.19.294</b>, <b>linuxlinux-4.19.294</b>, <b>linuxlinux-4.19.294</b>, <b>linuxlinux-4.19.294</b></p></summary>
<p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Vulnerability Details</summary>
<p>
A null pointer dereference flaw was found in the Linux kernel's DECnet networking protocol. This issue could allow a remote user to crash the system.
<p>Publish Date: 2023-06-30
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2023-3338>CVE-2023-3338</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.linuxkernelcves.com/cves/CVE-2023-3338">https://www.linuxkernelcves.com/cves/CVE-2023-3338</a></p>
<p>Release Date: 2023-06-30</p>
<p>Fix Resolution: v4.14.319,v4.19.287,v5.4.248,v5.10.185,v5.15.118</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2023-3338 (Medium) detected in multiple libraries - ## CVE-2023-3338 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>linuxlinux-4.19.294</b>, <b>linuxlinux-4.19.294</b>, <b>linuxlinux-4.19.294</b>, <b>linuxlinux-4.19.294</b>, <b>linuxlinux-4.19.294</b>, <b>linuxlinux-4.19.294</b>, <b>linuxlinux-4.19.294</b></p></summary>
<p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Vulnerability Details</summary>
<p>
A null pointer dereference flaw was found in the Linux kernel's DECnet networking protocol. This issue could allow a remote user to crash the system.
<p>Publish Date: 2023-06-30
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2023-3338>CVE-2023-3338</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.linuxkernelcves.com/cves/CVE-2023-3338">https://www.linuxkernelcves.com/cves/CVE-2023-3338</a></p>
<p>Release Date: 2023-06-30</p>
<p>Fix Resolution: v4.14.319,v4.19.287,v5.4.248,v5.10.185,v5.15.118</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve medium detected in multiple libraries cve medium severity vulnerability vulnerable libraries linuxlinux linuxlinux linuxlinux linuxlinux linuxlinux linuxlinux linuxlinux vulnerability details a null pointer dereference flaw was found in the linux kernel s decnet networking protocol this issue could allow a remote user to crash the system publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with mend | 0 |
1,217 | 3,453,658,317 | IssuesEvent | 2015-12-17 12:28:36 | mesosphere/marathon | https://api.github.com/repos/mesosphere/marathon | closed | Provide memory and cpu as environment variables in docker containers | enhancement service | It would be useful if docker containers launched with marathon had the memory and cpu app settings set as environment variables, such as `MARATHON_APP_MEM` and `MARATHON_APP_CPU`.
These could be used to configure an application at runtime based on the memory/cpu given to the application. | 1.0 | Provide memory and cpu as environment variables in docker containers - It would be useful if docker containers launched with marathon had the memory and cpu app settings set as environment variables, such as `MARATHON_APP_MEM` and `MARATHON_APP_CPU`.
These could be used to configure an application at runtime based on the memory/cpu given to the application. | non_priority | provide memory and cpu as environment variables in docker containers it would be useful if docker containers launched with marathon had the memory and cpu app settings set as environment variables such as marathon app mem and marathon app cpu these could be used to configure an application at runtime based on the memory cpu given to the application | 0 |
117,008 | 9,905,817,898 | IssuesEvent | 2019-06-27 12:33:29 | elastic/elasticsearch | https://api.github.com/repos/elastic/elasticsearch | closed | Add dedicated Q.B. cache tests instead of generic testing in AbstractQueryTestCase#testToQuery | :Search/Search >test v8.0.0 | In relation to occasional failures like #43112 and while looking into a fix in #43199 I had some discussions
about if its really a good idea to test the caching behaviour of all query builders in general in
`AbstractQueryTestCase#testToQuery` like we currently do. Doing this for all kinds of randomized query builder
parametrizations requires sometimes non-trivial edge-case handling in either the query builder generation code
or the utility code that codifies assumtions about whether this particular configuration of a builder should be cached
or not (currently implemented on a test-by-test basis by overwriting isCachable()).
This has two drawbacks:
- the "isCachable()" code can get quite complex even if the non-caching case is the exception
- we might only rarely check the context cacheable flag because we only run into those cases accidentally
Instead we should probably remove the cache-flag checks from `AbstractQueryTestCase#testToQuery` and add dedicated,
more controlled tests for the query builders that need them. | 1.0 | Add dedicated Q.B. cache tests instead of generic testing in AbstractQueryTestCase#testToQuery - In relation to occasional failures like #43112 and while looking into a fix in #43199 I had some discussions
about if its really a good idea to test the caching behaviour of all query builders in general in
`AbstractQueryTestCase#testToQuery` like we currently do. Doing this for all kinds of randomized query builder
parametrizations requires sometimes non-trivial edge-case handling in either the query builder generation code
or the utility code that codifies assumtions about whether this particular configuration of a builder should be cached
or not (currently implemented on a test-by-test basis by overwriting isCachable()).
This has two drawbacks:
- the "isCachable()" code can get quite complex even if the non-caching case is the exception
- we might only rarely check the context cacheable flag because we only run into those cases accidentally
Instead we should probably remove the cache-flag checks from `AbstractQueryTestCase#testToQuery` and add dedicated,
more controlled tests for the query builders that need them. | non_priority | add dedicated q b cache tests instead of generic testing in abstractquerytestcase testtoquery in relation to occasional failures like and while looking into a fix in i had some discussions about if its really a good idea to test the caching behaviour of all query builders in general in abstractquerytestcase testtoquery like we currently do doing this for all kinds of randomized query builder parametrizations requires sometimes non trivial edge case handling in either the query builder generation code or the utility code that codifies assumtions about whether this particular configuration of a builder should be cached or not currently implemented on a test by test basis by overwriting iscachable this has two drawbacks the iscachable code can get quite complex even if the non caching case is the exception we might only rarely check the context cacheable flag because we only run into those cases accidentally instead we should probably remove the cache flag checks from abstractquerytestcase testtoquery and add dedicated more controlled tests for the query builders that need them | 0 |
57,113 | 8,140,666,721 | IssuesEvent | 2018-08-20 21:56:58 | heptio/ark | https://api.github.com/repos/heptio/ark | closed | Broken docs link from main readme | Bug Documentation | Page: https://heptio.github.io/ark/v0.8.1/
Any docs links that are relative seem to 404:
* https://heptio.github.io/docs/cloud-common.md
* https://heptio.github.io/docs/build-from-scratch.md
* https://heptio.github.io/docs/debugging-restores.md
* and more! | 1.0 | Broken docs link from main readme - Page: https://heptio.github.io/ark/v0.8.1/
Any docs links that are relative seem to 404:
* https://heptio.github.io/docs/cloud-common.md
* https://heptio.github.io/docs/build-from-scratch.md
* https://heptio.github.io/docs/debugging-restores.md
* and more! | non_priority | broken docs link from main readme page any docs links that are relative seem to and more | 0 |
134,970 | 18,520,894,055 | IssuesEvent | 2021-10-20 14:56:23 | rlennon/whitesource_bolt_demo | https://api.github.com/repos/rlennon/whitesource_bolt_demo | opened | CVE-2020-29652 (High) detected in github.com/jpillora/chisel-1.3.2 | security vulnerability | ## CVE-2020-29652 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>github.com/jpillora/chisel-1.3.2</b></p></summary>
<p>A fast TCP tunnel over HTTP</p>
<p>
Dependency Hierarchy:
- :x: **github.com/jpillora/chisel-1.3.2** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/rlennon/whitesource_bolt_demo/commit/ec9d972edb7fb1ea028782bd0f770272d89e0c60">ec9d972edb7fb1ea028782bd0f770272d89e0c60</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
A nil pointer dereference in the golang.org/x/crypto/ssh component through v0.0.0-20201203163018-be400aefbc4c for Go allows remote attackers to cause a denial of service against SSH servers.
<p>Publish Date: 2020-12-17
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-29652>CVE-2020-29652</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://groups.google.com/g/golang-announce/c/ouZIlBimOsE?pli=1">https://groups.google.com/g/golang-announce/c/ouZIlBimOsE?pli=1</a></p>
<p>Release Date: 2020-12-17</p>
<p>Fix Resolution: v0.0.0-20201216223049-8b5274cf687f</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2020-29652 (High) detected in github.com/jpillora/chisel-1.3.2 - ## CVE-2020-29652 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>github.com/jpillora/chisel-1.3.2</b></p></summary>
<p>A fast TCP tunnel over HTTP</p>
<p>
Dependency Hierarchy:
- :x: **github.com/jpillora/chisel-1.3.2** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/rlennon/whitesource_bolt_demo/commit/ec9d972edb7fb1ea028782bd0f770272d89e0c60">ec9d972edb7fb1ea028782bd0f770272d89e0c60</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
A nil pointer dereference in the golang.org/x/crypto/ssh component through v0.0.0-20201203163018-be400aefbc4c for Go allows remote attackers to cause a denial of service against SSH servers.
<p>Publish Date: 2020-12-17
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-29652>CVE-2020-29652</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://groups.google.com/g/golang-announce/c/ouZIlBimOsE?pli=1">https://groups.google.com/g/golang-announce/c/ouZIlBimOsE?pli=1</a></p>
<p>Release Date: 2020-12-17</p>
<p>Fix Resolution: v0.0.0-20201216223049-8b5274cf687f</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve high detected in github com jpillora chisel cve high severity vulnerability vulnerable library github com jpillora chisel a fast tcp tunnel over http dependency hierarchy x github com jpillora chisel vulnerable library found in head commit a href found in base branch main vulnerability details a nil pointer dereference in the golang org x crypto ssh component through for go allows remote attackers to cause a denial of service against ssh servers publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource | 0 |
41,661 | 16,828,029,219 | IssuesEvent | 2021-06-17 21:35:24 | BCDevOps/OpenShift4-RollOut | https://api.github.com/repos/BCDevOps/OpenShift4-RollOut | closed | OpenShift 4.6 Upgrade | Epic ops and shared services team/DXC tech/automation | **Describe the issue**
This is an EPIC to track all the sub tasks needed to get all the clusters updated to 4.6. Subsets of these tasks can be added to Sprint Goals as we worth through this work which may take several sprints.
**Additional context**
- [Release Notes](https://docs.openshift.com/container-platform/4.6/release_notes/ocp-4-6-release-notes.html)
- [What's New Webinar](https://youtu.be/0ZyPHC-7V_0) and [slides](https://speakerdeck.com/redhatopenshift/whats-new-in-openshift-container-platform-4-dot-6)
| 1.0 | OpenShift 4.6 Upgrade - **Describe the issue**
This is an EPIC to track all the sub tasks needed to get all the clusters updated to 4.6. Subsets of these tasks can be added to Sprint Goals as we worth through this work which may take several sprints.
**Additional context**
- [Release Notes](https://docs.openshift.com/container-platform/4.6/release_notes/ocp-4-6-release-notes.html)
- [What's New Webinar](https://youtu.be/0ZyPHC-7V_0) and [slides](https://speakerdeck.com/redhatopenshift/whats-new-in-openshift-container-platform-4-dot-6)
| non_priority | openshift upgrade describe the issue this is an epic to track all the sub tasks needed to get all the clusters updated to subsets of these tasks can be added to sprint goals as we worth through this work which may take several sprints additional context and | 0 |
18,695 | 4,306,176,147 | IssuesEvent | 2016-07-21 01:21:53 | kalabox/kalabox | https://api.github.com/repos/kalabox/kalabox | closed | Hyper-V enabled and/or VT-x not installed results in silent install forever, GUI "loading" screen seems to hang 4eva | documentation | linux and osx are nice and snappy | 1.0 | Hyper-V enabled and/or VT-x not installed results in silent install forever, GUI "loading" screen seems to hang 4eva - linux and osx are nice and snappy | non_priority | hyper v enabled and or vt x not installed results in silent install forever gui loading screen seems to hang linux and osx are nice and snappy | 0 |
18,535 | 3,390,071,373 | IssuesEvent | 2015-11-30 08:35:18 | coala-analyzer/coala | https://api.github.com/repos/coala-analyzer/coala | closed | architecture: How do we pass files to bears? | feature need-design | # What we have
We currently create a dictionary which holds the file name and the file contents.
# Issues with current design
1. We can't process non-unicode files.
2. We can't process files that are "virtual" i.e. only exist in memory and not on the fs. (Will need that for editor plugins/IDE support.)
# Goals
* We'd need to be able to only give the file contents, i.e. assign `None` to the file name.
* We'd need to be able to only give the filename and not the file contents or classify the filecontents (binary/text).
I'd be happy if anyone has an idea how we can solve that.
<bountysource-plugin>
---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/12921786-architecture-how-do-we-pass-files-to-bears?utm_campaign=plugin&utm_content=tracker%2F2228228&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F2228228&utm_medium=issues&utm_source=github).
</bountysource-plugin> | 1.0 | architecture: How do we pass files to bears? - # What we have
We currently create a dictionary which holds the file name and the file contents.
# Issues with current design
1. We can't process non-unicode files.
2. We can't process files that are "virtual" i.e. only exist in memory and not on the fs. (Will need that for editor plugins/IDE support.)
# Goals
* We'd need to be able to only give the file contents, i.e. assign `None` to the file name.
* We'd need to be able to only give the filename and not the file contents or classify the filecontents (binary/text).
I'd be happy if anyone has an idea how we can solve that.
<bountysource-plugin>
---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/12921786-architecture-how-do-we-pass-files-to-bears?utm_campaign=plugin&utm_content=tracker%2F2228228&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F2228228&utm_medium=issues&utm_source=github).
</bountysource-plugin> | non_priority | architecture how do we pass files to bears what we have we currently create a dictionary which holds the file name and the file contents issues with current design we can t process non unicode files we can t process files that are virtual i e only exist in memory and not on the fs will need that for editor plugins ide support goals we d need to be able to only give the file contents i e assign none to the file name we d need to be able to only give the filename and not the file contents or classify the filecontents binary text i d be happy if anyone has an idea how we can solve that want to back this issue we accept bounties via | 0 |
231,231 | 25,495,022,986 | IssuesEvent | 2022-11-27 15:14:36 | billmcchesney1/superagent | https://api.github.com/repos/billmcchesney1/superagent | opened | CVE-2022-24999 (Medium) detected in multiple libraries | security vulnerability | ## CVE-2022-24999 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>qs-2.4.2.tgz</b>, <b>qs-1.2.2.tgz</b>, <b>qs-6.9.4.tgz</b>, <b>qs-6.7.0.tgz</b></p></summary>
<p>
<details><summary><b>qs-2.4.2.tgz</b></p></summary>
<p>A querystring parser that supports nesting and arrays, with a depth limit</p>
<p>Library home page: <a href="https://registry.npmjs.org/qs/-/qs-2.4.2.tgz">https://registry.npmjs.org/qs/-/qs-2.4.2.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/istanbul-middleware/node_modules/qs/package.json</p>
<p>
Dependency Hierarchy:
- zuul-3.12.0.tgz (Root Library)
- istanbul-middleware-0.2.2.tgz
- body-parser-1.12.4.tgz
- :x: **qs-2.4.2.tgz** (Vulnerable Library)
</details>
<details><summary><b>qs-1.2.2.tgz</b></p></summary>
<p>A querystring parser that supports nesting and arrays, with a depth limit</p>
<p>Library home page: <a href="https://registry.npmjs.org/qs/-/qs-1.2.2.tgz">https://registry.npmjs.org/qs/-/qs-1.2.2.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/request/node_modules/qs/package.json</p>
<p>
Dependency Hierarchy:
- zuul-3.12.0.tgz (Root Library)
- wd-0.3.11.tgz
- request-2.46.0.tgz
- :x: **qs-1.2.2.tgz** (Vulnerable Library)
</details>
<details><summary><b>qs-6.9.4.tgz</b></p></summary>
<p>A querystring parser that supports nesting and arrays, with a depth limit</p>
<p>Library home page: <a href="https://registry.npmjs.org/qs/-/qs-6.9.4.tgz">https://registry.npmjs.org/qs/-/qs-6.9.4.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/qs/package.json</p>
<p>
Dependency Hierarchy:
- :x: **qs-6.9.4.tgz** (Vulnerable Library)
</details>
<details><summary><b>qs-6.7.0.tgz</b></p></summary>
<p>A querystring parser that supports nesting and arrays, with a depth limit</p>
<p>Library home page: <a href="https://registry.npmjs.org/qs/-/qs-6.7.0.tgz">https://registry.npmjs.org/qs/-/qs-6.7.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/body-parser/node_modules/qs/package.json,/node_modules/express/node_modules/qs/package.json</p>
<p>
Dependency Hierarchy:
- express-4.17.1.tgz (Root Library)
- :x: **qs-6.7.0.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/billmcchesney1/superagent/commit/77fefdaffd4ef3cef2e5b252e165b5f40fae61d5">77fefdaffd4ef3cef2e5b252e165b5f40fae61d5</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
qs before 6.10.3, as used in Express before 4.17.3 and other products, allows attackers to cause a Node process hang for an Express application because an __ proto__ key can be used. In many typical Express use cases, an unauthenticated remote attacker can place the attack payload in the query string of the URL that is used to visit the application, such as a[__proto__]=b&a[__proto__]&a[length]=100000000. The fix was backported to qs 6.9.7, 6.8.3, 6.7.3, 6.6.1, 6.5.3, 6.4.1, 6.3.3, and 6.2.4 (and therefore Express 4.17.3, which has "deps: qs@6.9.7" in its release description, is not vulnerable).
<p>Publish Date: 2022-11-26
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-24999>CVE-2022-24999</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.cve.org/CVERecord?id=CVE-2022-24999">https://www.cve.org/CVERecord?id=CVE-2022-24999</a></p>
<p>Release Date: 2022-11-26</p>
<p>Fix Resolution: qs - 6.2.4,6.3.3,6.4.1,6.5.3,6.6.1,6.7.3,6.8.3,6.9.7,6.10.3</p>
</p>
</details>
<p></p>
***
<!-- REMEDIATE-OPEN-PR-START -->
- [ ] Check this box to open an automated fix PR
<!-- REMEDIATE-OPEN-PR-END -->
| True | CVE-2022-24999 (Medium) detected in multiple libraries - ## CVE-2022-24999 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>qs-2.4.2.tgz</b>, <b>qs-1.2.2.tgz</b>, <b>qs-6.9.4.tgz</b>, <b>qs-6.7.0.tgz</b></p></summary>
<p>
<details><summary><b>qs-2.4.2.tgz</b></p></summary>
<p>A querystring parser that supports nesting and arrays, with a depth limit</p>
<p>Library home page: <a href="https://registry.npmjs.org/qs/-/qs-2.4.2.tgz">https://registry.npmjs.org/qs/-/qs-2.4.2.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/istanbul-middleware/node_modules/qs/package.json</p>
<p>
Dependency Hierarchy:
- zuul-3.12.0.tgz (Root Library)
- istanbul-middleware-0.2.2.tgz
- body-parser-1.12.4.tgz
- :x: **qs-2.4.2.tgz** (Vulnerable Library)
</details>
<details><summary><b>qs-1.2.2.tgz</b></p></summary>
<p>A querystring parser that supports nesting and arrays, with a depth limit</p>
<p>Library home page: <a href="https://registry.npmjs.org/qs/-/qs-1.2.2.tgz">https://registry.npmjs.org/qs/-/qs-1.2.2.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/request/node_modules/qs/package.json</p>
<p>
Dependency Hierarchy:
- zuul-3.12.0.tgz (Root Library)
- wd-0.3.11.tgz
- request-2.46.0.tgz
- :x: **qs-1.2.2.tgz** (Vulnerable Library)
</details>
<details><summary><b>qs-6.9.4.tgz</b></p></summary>
<p>A querystring parser that supports nesting and arrays, with a depth limit</p>
<p>Library home page: <a href="https://registry.npmjs.org/qs/-/qs-6.9.4.tgz">https://registry.npmjs.org/qs/-/qs-6.9.4.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/qs/package.json</p>
<p>
Dependency Hierarchy:
- :x: **qs-6.9.4.tgz** (Vulnerable Library)
</details>
<details><summary><b>qs-6.7.0.tgz</b></p></summary>
<p>A querystring parser that supports nesting and arrays, with a depth limit</p>
<p>Library home page: <a href="https://registry.npmjs.org/qs/-/qs-6.7.0.tgz">https://registry.npmjs.org/qs/-/qs-6.7.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/body-parser/node_modules/qs/package.json,/node_modules/express/node_modules/qs/package.json</p>
<p>
Dependency Hierarchy:
- express-4.17.1.tgz (Root Library)
- :x: **qs-6.7.0.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/billmcchesney1/superagent/commit/77fefdaffd4ef3cef2e5b252e165b5f40fae61d5">77fefdaffd4ef3cef2e5b252e165b5f40fae61d5</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
qs before 6.10.3, as used in Express before 4.17.3 and other products, allows attackers to cause a Node process hang for an Express application because an __ proto__ key can be used. In many typical Express use cases, an unauthenticated remote attacker can place the attack payload in the query string of the URL that is used to visit the application, such as a[__proto__]=b&a[__proto__]&a[length]=100000000. The fix was backported to qs 6.9.7, 6.8.3, 6.7.3, 6.6.1, 6.5.3, 6.4.1, 6.3.3, and 6.2.4 (and therefore Express 4.17.3, which has "deps: qs@6.9.7" in its release description, is not vulnerable).
<p>Publish Date: 2022-11-26
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-24999>CVE-2022-24999</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.cve.org/CVERecord?id=CVE-2022-24999">https://www.cve.org/CVERecord?id=CVE-2022-24999</a></p>
<p>Release Date: 2022-11-26</p>
<p>Fix Resolution: qs - 6.2.4,6.3.3,6.4.1,6.5.3,6.6.1,6.7.3,6.8.3,6.9.7,6.10.3</p>
</p>
</details>
<p></p>
***
<!-- REMEDIATE-OPEN-PR-START -->
- [ ] Check this box to open an automated fix PR
<!-- REMEDIATE-OPEN-PR-END -->
| non_priority | cve medium detected in multiple libraries cve medium severity vulnerability vulnerable libraries qs tgz qs tgz qs tgz qs tgz qs tgz a querystring parser that supports nesting and arrays with a depth limit library home page a href path to dependency file package json path to vulnerable library node modules istanbul middleware node modules qs package json dependency hierarchy zuul tgz root library istanbul middleware tgz body parser tgz x qs tgz vulnerable library qs tgz a querystring parser that supports nesting and arrays with a depth limit library home page a href path to dependency file package json path to vulnerable library node modules request node modules qs package json dependency hierarchy zuul tgz root library wd tgz request tgz x qs tgz vulnerable library qs tgz a querystring parser that supports nesting and arrays with a depth limit library home page a href path to dependency file package json path to vulnerable library node modules qs package json dependency hierarchy x qs tgz vulnerable library qs tgz a querystring parser that supports nesting and arrays with a depth limit library home page a href path to dependency file package json path to vulnerable library node modules body parser node modules qs package json node modules express node modules qs package json dependency hierarchy express tgz root library x qs tgz vulnerable library found in head commit a href found in base branch master vulnerability details qs before as used in express before and other products allows attackers to cause a node process hang for an express application because an proto key can be used in many typical express use cases an unauthenticated remote attacker can place the attack payload in the query string of the url that is used to visit the application such as a b a a the fix was backported to qs and and therefore express which has deps qs in its release description is not vulnerable publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required none user interaction required scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution qs check this box to open an automated fix pr | 0 |
191,098 | 15,269,799,568 | IssuesEvent | 2021-02-22 13:17:22 | MadManGaz/Accelerometry | https://api.github.com/repos/MadManGaz/Accelerometry | opened | Improve code readability and documentation | documentation enhancement | This code was created quickly over a weekend. Code quality, readability, and documentation needs some work.
- [ ] Ensure proper separation of concerns
- [ ] Add documentation comments to any public API
- [ ] Extract views from `ContentView` to separate files | 1.0 | Improve code readability and documentation - This code was created quickly over a weekend. Code quality, readability, and documentation needs some work.
- [ ] Ensure proper separation of concerns
- [ ] Add documentation comments to any public API
- [ ] Extract views from `ContentView` to separate files | non_priority | improve code readability and documentation this code was created quickly over a weekend code quality readability and documentation needs some work ensure proper separation of concerns add documentation comments to any public api extract views from contentview to separate files | 0 |
158,437 | 24,839,864,378 | IssuesEvent | 2022-10-26 11:53:28 | dotnet/efcore | https://api.github.com/repos/dotnet/efcore | closed | Scaffolding of synonyms in SqlServer | type-enhancement needs-design propose-close customer-reported area-scaffolding | <!-- What problem are you trying to solve? -->
I'm trying to reverse-engineer an already existing database and the created synonyms are not being mapped. I want to have them mapped to.
<!-- Describe the solution you'd like -->
So my solution is pretty simple. Basicly include that in the SqlServerDatabaseModelFactory. I think everything should just work.
https://github.com/dotnet/efcore/blob/92f9a2fe8faa6cffdd9d1646060a8cf6dba8c50e/src/EFCore.SqlServer/Scaffolding/Internal/SqlServerDatabaseModelFactory.cs#L650
```sql
UNION ALL
SELECT
name,
OBJECT_ID([base_object_name]) as object_id,
SCHEMA_ID() AS schema_id
FROM sys.synonyms s
```
| 1.0 | Scaffolding of synonyms in SqlServer - <!-- What problem are you trying to solve? -->
I'm trying to reverse-engineer an already existing database and the created synonyms are not being mapped. I want to have them mapped to.
<!-- Describe the solution you'd like -->
So my solution is pretty simple. Basicly include that in the SqlServerDatabaseModelFactory. I think everything should just work.
https://github.com/dotnet/efcore/blob/92f9a2fe8faa6cffdd9d1646060a8cf6dba8c50e/src/EFCore.SqlServer/Scaffolding/Internal/SqlServerDatabaseModelFactory.cs#L650
```sql
UNION ALL
SELECT
name,
OBJECT_ID([base_object_name]) as object_id,
SCHEMA_ID() AS schema_id
FROM sys.synonyms s
```
| non_priority | scaffolding of synonyms in sqlserver i m trying to reverse engineer an already existing database and the created synonyms are not being mapped i want to have them mapped to so my solution is pretty simple basicly include that in the sqlserverdatabasemodelfactory i think everything should just work sql union all select name object id as object id schema id as schema id from sys synonyms s | 0 |
107,549 | 11,564,141,682 | IssuesEvent | 2020-02-20 07:59:20 | fetchai/agents-aea | https://api.github.com/repos/fetchai/agents-aea | opened | Add a guide to the docs for Docker image based deployment | documentation enhancement v0.3 | **Is your feature request related to a problem? Please describe.**
We currently do not explain in the docs how to deploy an AEA
**Describe the solution you'd like**
Add a guide in the docs | 1.0 | Add a guide to the docs for Docker image based deployment - **Is your feature request related to a problem? Please describe.**
We currently do not explain in the docs how to deploy an AEA
**Describe the solution you'd like**
Add a guide in the docs | non_priority | add a guide to the docs for docker image based deployment is your feature request related to a problem please describe we currently do not explain in the docs how to deploy an aea describe the solution you d like add a guide in the docs | 0 |
21,250 | 10,588,386,096 | IssuesEvent | 2019-10-09 01:47:23 | Ne0nd0g/merlin | https://api.github.com/repos/Ne0nd0g/merlin | closed | Agent Allows Untrused Certificate | security | Merlin agent uses a TLS configuration setting of `InsecureSkipVerify: true` that will permit communications with a server using an untrusted certificate. Initially this was by design to facilitate ease of use and allow operators the ability to use self-signed certificates.
Merlin Agent should be written so that, by default, it won't communicate with hosts using an untrusted certificate. A command line flag and/or build argument should be implemented to downgrade security to allow communications with a host using an untrusted certificate.
Alternatively, have the agent report back the certificate hash it believes it is communicating with and check it against the server's hash, even if using a self-signed certificate. If there is no match drop the communication or hold the agent in a quarantine state and allow the operator to decide how to proceed. | True | Agent Allows Untrused Certificate - Merlin agent uses a TLS configuration setting of `InsecureSkipVerify: true` that will permit communications with a server using an untrusted certificate. Initially this was by design to facilitate ease of use and allow operators the ability to use self-signed certificates.
Merlin Agent should be written so that, by default, it won't communicate with hosts using an untrusted certificate. A command line flag and/or build argument should be implemented to downgrade security to allow communications with a host using an untrusted certificate.
Alternatively, have the agent report back the certificate hash it believes it is communicating with and check it against the server's hash, even if using a self-signed certificate. If there is no match drop the communication or hold the agent in a quarantine state and allow the operator to decide how to proceed. | non_priority | agent allows untrused certificate merlin agent uses a tls configuration setting of insecureskipverify true that will permit communications with a server using an untrusted certificate initially this was by design to facilitate ease of use and allow operators the ability to use self signed certificates merlin agent should be written so that by default it won t communicate with hosts using an untrusted certificate a command line flag and or build argument should be implemented to downgrade security to allow communications with a host using an untrusted certificate alternatively have the agent report back the certificate hash it believes it is communicating with and check it against the server s hash even if using a self signed certificate if there is no match drop the communication or hold the agent in a quarantine state and allow the operator to decide how to proceed | 0 |
1,941 | 2,678,172,414 | IssuesEvent | 2015-03-26 08:46:05 | Starcounter/Starcounter | https://api.github.com/repos/Starcounter/Starcounter | closed | Implement multi-level dynamic types | Code host Dynamic Types enhancement guess: < week | In the dynamic types specification, we have established that Starcounter will auto-create "one extra level" of types, for every type declaration explicitly specified by the developer. This is not yet implemented.
This model
```C#
class Car {
[Type] CarModel Model;
}
class CarModel {}
```
currently result in **one** new type: a type named "Car" (of .NET type ```CarModel```).
The current (logical) tuple of this type will look approx like:
Key | NET Type | Name | TypeInherits |Type
----- | ------------- | -------- | --------------- | -------
1 | CarModel | "Car" | null | null
The right thing for **next** is that it should instead result in **two** new types, with tuples looking like
Key | NET Type | Name | TypeInherits |Type
----- | ------------- | -------- | --------------- | -------
1 | CarModel | "Car" | null | 2
2 | [Unknown] | "CarModel" | null | null
("[Unknown]" is an implementation detail, but must support ```IObjectView``` and ```IDbTuple```; in the first implementation, it will most likely be represented by the metadata ```RawView```) | 1.0 | Implement multi-level dynamic types - In the dynamic types specification, we have established that Starcounter will auto-create "one extra level" of types, for every type declaration explicitly specified by the developer. This is not yet implemented.
This model
```C#
class Car {
[Type] CarModel Model;
}
class CarModel {}
```
currently result in **one** new type: a type named "Car" (of .NET type ```CarModel```).
The current (logical) tuple of this type will look approx like:
Key | NET Type | Name | TypeInherits |Type
----- | ------------- | -------- | --------------- | -------
1 | CarModel | "Car" | null | null
The right thing for **next** is that it should instead result in **two** new types, with tuples looking like
Key | NET Type | Name | TypeInherits |Type
----- | ------------- | -------- | --------------- | -------
1 | CarModel | "Car" | null | 2
2 | [Unknown] | "CarModel" | null | null
("[Unknown]" is an implementation detail, but must support ```IObjectView``` and ```IDbTuple```; in the first implementation, it will most likely be represented by the metadata ```RawView```) | non_priority | implement multi level dynamic types in the dynamic types specification we have established that starcounter will auto create one extra level of types for every type declaration explicitly specified by the developer this is not yet implemented this model c class car carmodel model class carmodel currently result in one new type a type named car of net type carmodel the current logical tuple of this type will look approx like key net type name typeinherits type carmodel car null null the right thing for next is that it should instead result in two new types with tuples looking like key net type name typeinherits type carmodel car null carmodel null null is an implementation detail but must support iobjectview and idbtuple in the first implementation it will most likely be represented by the metadata rawview | 0 |
132,805 | 18,764,921,421 | IssuesEvent | 2021-11-05 21:48:30 | HappyMeBulgaria/HappyMe | https://api.github.com/repos/HappyMeBulgaria/HappyMe | reopened | Add screen with the right answer/ wrong answer | enhancement design & UX feature | When guessing the answer, for example you have a banana and some colors. When you choose the yellow color, you go to the green Bobo modal. Maybe there should be a screen in between that shows how the grayscale banana merges with the yellow color or smth and you can see the right answer - the banana with color.
| 1.0 | Add screen with the right answer/ wrong answer - When guessing the answer, for example you have a banana and some colors. When you choose the yellow color, you go to the green Bobo modal. Maybe there should be a screen in between that shows how the grayscale banana merges with the yellow color or smth and you can see the right answer - the banana with color.
| non_priority | add screen with the right answer wrong answer when guessing the answer for example you have a banana and some colors when you choose the yellow color you go to the green bobo modal maybe there should be a screen in between that shows how the grayscale banana merges with the yellow color or smth and you can see the right answer the banana with color | 0 |
170,600 | 13,194,376,808 | IssuesEvent | 2020-08-13 16:43:33 | Karl255/UcenikShuffle | https://api.github.com/repos/Karl255/UcenikShuffle | closed | Create a test application | testing | Create a console application that prints out student sitting combinations and student sitting combinations for a couple of test cases | 1.0 | Create a test application - Create a console application that prints out student sitting combinations and student sitting combinations for a couple of test cases | non_priority | create a test application create a console application that prints out student sitting combinations and student sitting combinations for a couple of test cases | 0 |
35,225 | 6,423,144,761 | IssuesEvent | 2017-08-09 10:13:18 | terraform-providers/terraform-provider-aws | https://api.github.com/repos/terraform-providers/terraform-provider-aws | closed | Docs - aws_s3_bucket name example uses underscores , hence fails to create | bug documentation | ### Terraform Version
Terraform v0.10.0
### Affected Resource(s)
Please list the resources as a list, for example:
- aws_s3_bucket
### Terraform Configuration Files
From the existing docs:
```hcl
resource "aws_s3_bucket" "b" {
bucket = "my_tf_test_bucket"
acl = "private"
tags {
Name = "My bucket"
Environment = "Dev"
}
}
```
### Expected Behavior
The documented example should be syntactically correct so that further changes based on it should result in working resources except when it fails due to non-syntax related failures (example failure due to resource conflict which will happen if anyone creates the s3 bucket as mentioned in the example, no one else will be able to create/repeat the same).
### Actual Behavior
Error applying plan:
1 error(s) occurred:
* aws_s3_bucket.b: 1 error(s) occurred:
* aws_s3_bucket.b: Error validating S3 bucket name: only lowercase alphanumeric characters and hyphens allowed in "my_tf_test_bucket"
### Steps to Reproduce
`terraform apply`
| 1.0 | Docs - aws_s3_bucket name example uses underscores , hence fails to create - ### Terraform Version
Terraform v0.10.0
### Affected Resource(s)
Please list the resources as a list, for example:
- aws_s3_bucket
### Terraform Configuration Files
From the existing docs:
```hcl
resource "aws_s3_bucket" "b" {
bucket = "my_tf_test_bucket"
acl = "private"
tags {
Name = "My bucket"
Environment = "Dev"
}
}
```
### Expected Behavior
The documented example should be syntactically correct so that further changes based on it should result in working resources except when it fails due to non-syntax related failures (example failure due to resource conflict which will happen if anyone creates the s3 bucket as mentioned in the example, no one else will be able to create/repeat the same).
### Actual Behavior
Error applying plan:
1 error(s) occurred:
* aws_s3_bucket.b: 1 error(s) occurred:
* aws_s3_bucket.b: Error validating S3 bucket name: only lowercase alphanumeric characters and hyphens allowed in "my_tf_test_bucket"
### Steps to Reproduce
`terraform apply`
| non_priority | docs aws bucket name example uses underscores hence fails to create terraform version terraform affected resource s please list the resources as a list for example aws bucket terraform configuration files from the existing docs hcl resource aws bucket b bucket my tf test bucket acl private tags name my bucket environment dev expected behavior the documented example should be syntactically correct so that further changes based on it should result in working resources except when it fails due to non syntax related failures example failure due to resource conflict which will happen if anyone creates the bucket as mentioned in the example no one else will be able to create repeat the same actual behavior error applying plan error s occurred aws bucket b error s occurred aws bucket b error validating bucket name only lowercase alphanumeric characters and hyphens allowed in my tf test bucket steps to reproduce terraform apply | 0 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.