Skip to content
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

Potential NULL pointer dereference bug in callInternal() #247

Open
hariramshankar opened this issue Sep 19, 2024 · 4 comments
Open

Potential NULL pointer dereference bug in callInternal() #247

hariramshankar opened this issue Sep 19, 2024 · 4 comments
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@hariramshankar
Copy link

In the function callInternal(), client->client->dataReceived is dereferenced unconditionally before it is checked for NULL:
https://github.com/kubernetes-client/c/blob/master/kubernetes/src/generic.c#L62

char* callInternal(genericClient_t *client,
                   const char *path, list_t *queryParameters, list_t *headerParameters, list_t *formParameters, list_t *headerType, list_t *contentType, const char *body, const char *method)
{
    apiClient_invoke(client->client, path, queryParameters, headerParameters, formParameters, headerType, contentType, body, method);

    if (client->client->response_code == 401) {
        return NULL;
    }
    char* elementToReturn =  strndup((char*)client->client->dataReceived, client->client->dataReceivedLen); <<<<<<

    if (client->client->dataReceived) {
        free(client->client->dataReceived);
        client->client->dataReceived = NULL;
        client->client->dataReceivedLen = 0;
    }

    return elementToReturn;
}
@ityuhui
Copy link
Member

ityuhui commented Sep 23, 2024

Thanks for finding this issue. Would you like to submit a PR to fix it?

@WookiesRpeople2
Copy link

Hi I was wondering if this issue is still open and if so I would like to work on this :)

@ityuhui
Copy link
Member

ityuhui commented Oct 10, 2024

Hi I was wondering if this issue is still open and if so I would like to work on this :)

Yes. It's still open now and welcome the contributions!

@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

5 participants