{"id":"CVE-2023-28640","aliases":["EUVD-2023-1056","GHSA-m6f8-hjrv-mw5f"],"status":"published","title":"Permissions bypass in Apiman could enable authenticated attacker to unpermitted API Key","description":"Apiman is a flexible and open source API Management platform. Due to a missing permissions check, an attacker with an authenticated Apiman Manager account may be able to gain access to API keys they do not have permission for if they correctly guess the URL, which includes Organisation ID, Client ID, and Client Version of the targeted non-permitted resource. While not trivial to exploit, it could be achieved by brute-forcing or guessing common names. Access to the non-permitted API Keys could allow use of other users' resources without their permission (depending on the specifics of configuration, such as whether an API key is the only form of security). Apiman 3.1.0.Final resolved this issue. Users are advised to upgrade. The only known workaround is to restrict account access.","severity":{"version":"3.1","score":6.4,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N","level":"medium","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-09","score":0.0034,"percentile":0.27639,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-269","CWE-280","CWE-862"],"published":"2023-03-27T20:46:33Z","modified":"2026-10-28T02:30:56Z","fixes":[{"ecosystem":"Maven","package":"io.apiman:apiman-manager-api-rest-impl","fixed_in":["3.0.0.Final","3.1.0.Final"],"sources":["ghsa","osv"]}],"affected":[{"source":"ghsa","ecosystem":"Maven","package":"io.apiman:apiman-manager-api-rest-impl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.0.0.Final"}]}]},{"source":"osv","ecosystem":"Maven","package":"io.apiman:apiman-manager-api-rest-impl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.1.0.Final"}]}],"versions":["1.0.0.Beta1","1.0.0.Beta2","1.0.0.Final","1.0.1.Final","1.0.2.Final","1.0.3.Final","1.1.0.Final","1.1.0.RC1","1.1.0.RC3","1.1.1.Final","1.1.2.Final","1.1.2.Preview1","1.1.2.Preview2","1.1.3.CR1","1.1.3.Final","1.1.4.Final","1.1.5.Final","1.1.6.Final","1.1.7.Final","1.1.8.Final","1.2.0.Alpha1","1.2.0.Alpha2","1.2.0.Alpha3","1.2.0.Beta1","1.2.0.Beta2","1.2.0.Beta3","1.2.0.Final","1.2.1.Final","1.2.2.Final","1.2.3.CR1","1.2.3.Final","1.2.4.Final","1.2.5.Final","1.2.6.Beta1","1.2.6.Beta3","1.2.6.Final","1.2.7.Beta1","1.2.7.Final","1.2.8.Final","1.2.9.Final","1.3.0.Final","1.3.1.Final","1.3.2.Final","1.3.3.Final","1.3.4.Final","1.3.5.Final","1.4.0.Final","1.4.1.Final","1.4.2.Final","1.4.3.Final","1.5.0.Final","1.5.1.Final","1.5.2.Final","1.5.3.Final","1.5.4.Final","1.5.5.Final","1.5.6.Final","1.5.7.Final","2.0.0.Final","2.1.0.Final","2.1.1.Final","2.1.2.Final","2.1.3.Final","2.1.4.Final","2.1.5.Final","2.2.0.Final","2.2.1.Final","2.2.2.Final","2.2.3.Final","3.0.0.Final","3.0.0.RC6","3.1.0.RC2","3.1.0.RC4","3.1.0.RC6"]}],"products":[{"vendor":"apiman","product":"apiman"}],"references":[{"url":"https://github.com/apiman/apiman/security/advisories/GHSA-m6f8-hjrv-mw5f","tags":["x_refsource_CONFIRM","x_transferred","Vendor Advisory","advisory","web"]},{"url":"https://www.apiman.io/blog/potential-permissions-bypass-disclosure/","tags":["x_refsource_MISC","x_transferred","Mitigation","Vendor Advisory","article"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-28640","tags":["advisory"]},{"url":"https://github.com/advisories/GHSA-m6f8-hjrv-mw5f"},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2023/28xxx/CVE-2023-28640.json","tags":["advisory"]},{"url":"https://github.com/apiman/apiman","tags":["package"]},{"url":"https://www.apiman.io/blog/potential-permissions-bypass-disclosure","tags":["web"]}],"sources":{"cve":[{"id":"CVE-2023-28640","title":"Permissions bypass in Apiman could enable authenticated attacker to unpermitted API Key","description":"Apiman is a flexible and open source API Management platform. Due to a missing permissions check, an attacker with an authenticated Apiman Manager account may be able to gain access to API keys they do not have permission for if they correctly guess the URL, which includes Organisation ID, Client ID, and Client Version of the targeted non-permitted resource. While not trivial to exploit, it could be achieved by brute-forcing or guessing common names. Access to the non-permitted API Keys could allow use of other users' resources without their permission (depending on the specifics of configuration, such as whether an API key is the only form of security). Apiman 3.1.0.Final resolved this issue. Users are advised to upgrade. The only known workaround is to restrict account access.\n","status":"published","published":"2023-03-27T20:46:33.4Z","modified":"2025-02-19T15:13:47.538Z","cvss":[{"version":"3.1","score":6.4,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N","level":"medium","assessor":"cna"}],"cwes":["CWE-269"],"updated_at":"2026-11-02T14:35:32.376766Z"}],"euvd":[{"id":"EUVD-2023-1056","description":"Apiman is a flexible and open source API Management platform. Due to a missing permissions check, an attacker with an authenticated Apiman Manager account may be able to gain access to API keys they do not have permission for if they correctly guess the URL, which includes Organisation ID, Client ID, and Client Version of the targeted non-permitted resource. While not trivial to exploit, it could be achieved by brute-forcing or guessing common names. Access to the non-permitted API Keys could allow use of other users' resources without their permission (depending on the specifics of configuration, such as whether an API key is the only form of security). Apiman 3.1.0.Final resolved this issue. Users are advised to upgrade. The only known workaround is to restrict account access.\n","status":"published","published":"2023-03-27T20:46:33Z","modified":"2025-02-19T15:13:47Z","cvss":[{"version":"3.1","score":6.4,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N","level":"medium"}],"updated_at":"2026-11-02T20:53:27.843209Z"}],"ghsa":[{"id":"GHSA-m6f8-hjrv-mw5f","title":"Apiman vulnerable to permissions bypass due to missing check on API key URL","description":"### Impact\n\nDue to a missing permissions check, an attacker with an authenticated Apiman Manager account may be able to gain access to API keys they do not have permission for if they correctly guess the URL. The URL includes Organisation ID, Client ID, and Client Version of the targeted non-permitted resource, and each of these can have arbitrary values.\n\nWhile not trivial to exploit, it could be achieved by brute-forcing or guessing common names.\n\nAccess to the non-permitted API Keys could allow use of other users' resources without their permission (depending on the specifics of configuration, such as whether an API key is the only form of security).\n\n### Patches\n\nApiman 3.1.0.Final and later resolves this issue. \n\n### Workarounds\n\nOnly provide Apiman Manager accounts to known users, do not allow anonymous/unknown users to create an Apiman Manager account.\n\nNote that this does **not** affect the Apiman Gateway.\n\n### References\n\n* [Blog post disclosing issue](https://www.apiman.io/blog/potential-permissions-bypass-disclosure/)\n","status":"published","published":"2023-03-27T22:17:57Z","modified":"2023-04-03T20:54:36Z","cvss":[{"version":"3.1","score":6.4,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N","level":"medium"}],"cwes":["CWE-269","CWE-280","CWE-862"],"updated_at":"2026-11-02T14:36:49.768564Z"}],"nvd":[{"id":"CVE-2023-28640","description":"Apiman is a flexible and open source API Management platform. Due to a missing permissions check, an attacker with an authenticated Apiman Manager account may be able to gain access to API keys they do not have permission for if they correctly guess the URL, which includes Organisation ID, Client ID, and Client Version of the targeted non-permitted resource. While not trivial to exploit, it could be achieved by brute-forcing or guessing common names. Access to the non-permitted API Keys could allow use of other users' resources without their permission (depending on the specifics of configuration, such as whether an API key is the only form of security). Apiman 3.1.0.Final resolved this issue. Users are advised to upgrade. The only known workaround is to restrict account access.\n","status":"published","published":"2023-03-27T21:15:12.667Z","modified":"2026-06-17T05:48:27.033Z","cvss":[{"version":"3.1","score":6.4,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N","level":"medium","assessor":"secondary"},{"version":"3.1","score":3.1,"vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N","level":"low","assessor":"primary"}],"cwes":["CWE-269","CWE-862"],"updated_at":"2026-11-02T14:07:51.883939Z"}],"osv":[{"id":"CVE-2023-28640","title":"Permissions bypass in Apiman could enable authenticated attacker to unpermitted API Key","description":"Apiman is a flexible and open source API Management platform. Due to a missing permissions check, an attacker with an authenticated Apiman Manager account may be able to gain access to API keys they do not have permission for if they correctly guess the URL, which includes Organisation ID, Client ID, and Client Version of the targeted non-permitted resource. While not trivial to exploit, it could be achieved by brute-forcing or guessing common names. Access to the non-permitted API Keys could allow use of other users' resources without their permission (depending on the specifics of configuration, such as whether an API key is the only form of security). Apiman 3.1.0.Final resolved this issue. Users are advised to upgrade. The only known workaround is to restrict account access.\n","status":"published","published":"2023-03-27T20:46:33.4Z","modified":"2026-10-28T02:30:56.001172857Z","cvss":[{"version":"3.1","score":6.4,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N","level":"medium"}],"cwes":["CWE-269"],"updated_at":"2026-11-02T15:44:31.468318Z"},{"id":"GHSA-m6f8-hjrv-mw5f","title":"Apiman vulnerable to permissions bypass due to missing check on API key URL","description":"### Impact\n\nDue to a missing permissions check, an attacker with an authenticated Apiman Manager account may be able to gain access to API keys they do not have permission for if they correctly guess the URL. The URL includes Organisation ID, Client ID, and Client Version of the targeted non-permitted resource, and each of these can have arbitrary values.\n\nWhile not trivial to exploit, it could be achieved by brute-forcing or guessing common names.\n\nAccess to the non-permitted API Keys could allow use of other users' resources without their permission (depending on the specifics of configuration, such as whether an API key is the only form of security).\n\n### Patches\n\nApiman 3.1.0.Final and later resolves this issue. \n\n### Workarounds\n\nOnly provide Apiman Manager accounts to known users, do not allow anonymous/unknown users to create an Apiman Manager account.\n\nNote that this does **not** affect the Apiman Gateway.\n\n### References\n\n* [Blog post disclosing issue](https://www.apiman.io/blog/potential-permissions-bypass-disclosure/)\n","status":"published","published":"2023-03-27T22:17:57Z","modified":"2026-09-10T03:49:53.142119728Z","cvss":[{"version":"3.1","score":6.4,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N","level":"medium"}],"cwes":["CWE-269","CWE-280","CWE-862"],"updated_at":"2026-11-02T15:46:51.463834Z"}]}}