Skip to content

Conversation

@PaperStrange
Copy link
Owner

  • Dependabot cannot update nth-check to a non-vulnerable version
    The latest possible version that can be installed is 1.0.2 because of the following conflicting dependencies:

react-scripts@5.0.1 requires nth-check@^1.0.2 via a transitive dependency on css-select@2.1.0
No patched version available for nth-check

  • PostCSS line return parsing error
    Upgrade postcss to fix 1 Dependabot alert in package-lock.json
    Upgrade postcss to version 8.4.31 or later

  • Potential file system race condition
    scripts/utils/test-script-template.js:127
    scripts/generate-keys.js:92
    server/utils/vaultService.js:94
    Often it is necessary to check the state of a file before using it. These checks usually take a file name to be checked, and if the check returns positively, then the file is opened or otherwise operated upon.
    However, in the time between the check and the operation, the underlying file referenced by the file name could be changed by an attacker, causing unexpected behavior.

  • User-controlled bypass of security check
    server/routes/emails.js:24
    server/middleware/authMiddleware.js:124
    Using user-controlled data in a permissions check may allow a user to gain unauthorized access to protected functionality or data.

  • Remote property injection
    server/utils/tokenProvider.js:166
    Dynamically computing object property names from untrusted input may have multiple undesired consequences. For example, if the property access is used as part of a write, an attacker may overwrite vital properties of objects, such as proto. This attack is known as prototype pollution attack and may serve as a vehicle for denial-of-service attacks. A similar attack vector, is to replace the toString property of an object with a primitive. Whenever toString is then called on that object, either explicitly or implicitly as part of a type coercion, an exception will be raised.

  • security scan
    Missing download info for lirantal/lockfile-lint-action@master

  • build error
    AnalyticsService.js: Unexpected token (480:5)

@PaperStrange PaperStrange self-assigned this May 20, 2025
@PaperStrange PaperStrange added bug Something isn't working enhancement New feature or request labels May 20, 2025
# Check package.json for issues
- name: Package.json security audit
uses: lirantal/lockfile-lint-action@master
uses: lirantal/lockfile-lint-action@v4.7.1

Check warning

Code scanning / CodeQL

Unpinned tag for a non-immutable Action in workflow Medium

Unpinned 3rd party Action 'Security Scan' step
Uses Step
uses 'lirantal/lockfile-lint-action' with ref 'v4.7.1', not a pinned commit hash
@PaperStrange
Copy link
Owner Author

Merge with issue closed

@PaperStrange PaperStrange changed the title Fix issue #22 Address with severe security check issues Fix: fix issue #22 Address with severe security check issues May 20, 2025
@PaperStrange PaperStrange merged commit 88b8620 into master May 20, 2025
3 of 4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants