Skip to content

Restrict RemoteFlowSource of CAP to only some properties and method calls on it #208

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 9 commits into
base: main
Choose a base branch
from

Conversation

jeongsoolee09
Copy link
Contributor

What This PR Contributes

Future Works

- `service3nocds.js` had a service that was named differently. Clarified the gist of the file using tags.
- `service4.js` was identical to `service3nocds.js`, except for the `cds.serve` call. This is better suited for `server.js`.
- Since `HandlerParameterOfExposedService` is no longer a `RemoteFlowSource`, we place another query for testing it only.
- The case categorization is as follows:
  - `service1`: Exposed service with reads from properties and method calls, some of which are tainted and not tainted.
  - `service2`: Service that both receives data from service1 and service4 but does not propagate it further.
  - `service3`: Service without a CDS declaration, simulating extraction failure. Should be recognized as exposed, from overapproximation. Consists of identical property reads / method calls as those of `service1`.
  - `service4`: Service that is explicitly declared as internal only. Consists of identical property reads / method calls as those of `service1`, but is not a taint source from being unexposed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant