Exposing Swagger/OpenAPI documentation is primarily a risk if your API has underlying security flaws, as it gives attackers a precise roadmap to find them.
Those detail every endpoint, parameter, and data model, making it easier to discover and exploit vulnerabilities like broken access control or injection points.
While a perfectly secure API mitigates the danger, protecting your documentation is a critical layer of defense that forces attackers to work without a map.
Severity: info
Fingerprint: 5733ddf49ff49cd1aad035491a3b826fe90d52a7828489390e322c04b5177285
Public Swagger UI/API detected at path: /swagger/index.html - sample paths: DELETE /api/v1/TestRemoveAll GET /api/TestSplunk/ping GET /api/v1/AccountID GET /api/v1/AllPushNotifications GET /api/v1/AppVersionCheck GET /api/v1/B2CInstance GET /api/v1/Clean GET /api/v1/CustomerAccounts GET /api/v1/DbHealth GET /api/v1/Devices GET /api/v1/EligibleItems GET /api/v1/EquipmentDBA GET /api/v1/FeaturedArticles GET /api/v1/MasksAndDevices GET /api/v1/MySupportTeam GET /api/v1/Notifications GET /api/v1/Notify GET /api/v1/PAPComplianceStatus GET /api/v1/PatientCommPreferences GET /api/v1/PatientIds GET /api/v1/PatientProfile GET /api/v1/SentNotifications GET /api/v1/ShippingAddressReorder GET /api/v1/TestAllPushNotifications GET /api/v1/TestAuthorization GET /api/v1/TestGetAll GET /api/v1/TestGetNew GET /api/v1/TestNoAuthorization GET /api/v1/TestNotify GET /api/v1/UsageDataResmed GET /api/v1/UsageDataRespironics GET /api/v1/ValidateUser GET /api/v1/ValidateUserB2C POST /api/v1/AddContact POST /api/v1/DisconnectDevice POST /api/v1/Order POST /api/v1/PatientDevice POST /api/v1/RecurringOrderAgreement POST /api/v1/ReportAProblem POST /api/v1/RequestAccountDelete POST /api/v1/SendOTP POST /api/v1/SendOTPPhoneCall POST /api/v1/SendOTPSms POST /api/v1/SignTermsAndConditions PUT /api/v1/Contacts PUT /api/v1/InsuranceCoverage PUT /api/v1/NotificationStatus PUT /api/v1/RemoveAllRONotifications PUT /api/v1/ShippingAddress PUT /api/v1/TestResetNotificationStatuses PUT /api/v1/TestResetNotificationStatusesForPatient
Severity: info
Fingerprint: 5733ddf49ff49cd1aad035491a3b826fe90d52a7828489390e322c04d392f223
Public Swagger UI/API detected at path: /swagger/index.html - sample paths: DELETE /api/v1/TestRemoveAll GET /api/TestSplunk/ping GET /api/v1/AccountID GET /api/v1/AllPushNotifications GET /api/v1/AppVersionCheck GET /api/v1/B2CInstance GET /api/v1/Clean GET /api/v1/CustomerAccounts GET /api/v1/Devices GET /api/v1/EligibleItems GET /api/v1/EquipmentDBA GET /api/v1/FeaturedArticles GET /api/v1/MasksAndDevices GET /api/v1/MySupportTeam GET /api/v1/Notifications GET /api/v1/Notify GET /api/v1/PAPComplianceStatus GET /api/v1/PatientCommPreferences GET /api/v1/PatientIds GET /api/v1/PatientProfile GET /api/v1/SentNotifications GET /api/v1/ShippingAddressReorder GET /api/v1/TestAllPushNotifications GET /api/v1/TestAuthorization GET /api/v1/TestGetAll GET /api/v1/TestGetNew GET /api/v1/TestNoAuthorization GET /api/v1/TestNotify GET /api/v1/UsageDataResmed GET /api/v1/UsageDataRespironics GET /api/v1/ValidateUser GET /api/v1/ValidateUserB2C POST /api/v1/AddContact POST /api/v1/DisconnectDevice POST /api/v1/Order POST /api/v1/PatientDevice POST /api/v1/RecurringOrderAgreement POST /api/v1/ReportAProblem POST /api/v1/RequestAccountDelete POST /api/v1/SendOTP POST /api/v1/SendOTPPhoneCall POST /api/v1/SendOTPSms POST /api/v1/SignTermsAndConditions PUT /api/v1/Contacts PUT /api/v1/InsuranceCoverage PUT /api/v1/NotificationStatus PUT /api/v1/RemoveAllRONotifications PUT /api/v1/ShippingAddress PUT /api/v1/TestResetNotificationStatuses PUT /api/v1/TestResetNotificationStatusesForPatient
Severity: info
Fingerprint: 5733ddf49ff49cd1aad035491a3b826ffd58fbc1e2c5212ccc46c24f95205ed0
Public Swagger UI/API detected at path: /swagger/index.html - sample paths: DELETE /api/v1/TestRemoveAll GET /api/v1/AccountID GET /api/v1/AllPushNotifications GET /api/v1/AppVersionCheck GET /api/v1/B2CInstance GET /api/v1/Clean GET /api/v1/CustomerAccounts GET /api/v1/Devices GET /api/v1/EligibleItems GET /api/v1/EquipmentDBA GET /api/v1/FeaturedArticles GET /api/v1/MasksAndDevices GET /api/v1/MySupportTeam GET /api/v1/Notifications GET /api/v1/Notify GET /api/v1/PAPComplianceStatus GET /api/v1/PatientCommPreferences GET /api/v1/PatientIds GET /api/v1/PatientProfile GET /api/v1/SentNotifications GET /api/v1/ShippingAddressReorder GET /api/v1/TestAllPushNotifications GET /api/v1/TestAuthorization GET /api/v1/TestGetAll GET /api/v1/TestGetNew GET /api/v1/TestNoAuthorization GET /api/v1/TestNotify GET /api/v1/UsageDataResmed GET /api/v1/UsageDataRespironics GET /api/v1/ValidateUser GET /api/v1/ValidateUserB2C GET /api/v1/core-ping GET /api/v1/debug/token POST /api/v1/AddContact POST /api/v1/DisconnectDevice POST /api/v1/Order POST /api/v1/PatientDevice POST /api/v1/RecurringOrderAgreement POST /api/v1/ReportAProblem POST /api/v1/RequestAccountDelete POST /api/v1/SendOTP POST /api/v1/SendOTPPhoneCall POST /api/v1/SendOTPSms POST /api/v1/SignTermsAndConditions PUT /api/v1/Contacts PUT /api/v1/InsuranceCoverage PUT /api/v1/NotificationStatus PUT /api/v1/RemoveAllRONotifications PUT /api/v1/ShippingAddress PUT /api/v1/TestResetNotificationStatuses PUT /api/v1/TestResetNotificationStatusesForPatient
GraphQL introspection is enabled.
This could leak to data leak if not properly configured.
Severity: medium
Fingerprint: c2db3a1c40d490db1a0bbaa3b6ec530de8fd702fa9e8262a883448623b618c14
GraphQL introspection enabled at /graphql Types: 154 (by kind: ENUM: 5, INPUT_OBJECT: 37, OBJECT: 102, SCALAR: 10) Operations: - Query: Query | fields: buildings, coupon, customerDetails, customerMaskedPhone, deliverToMeSpots - Mutation: Mutation | fields: changePassword, claimOffer, deleteCoupon, deleteLineItem, logout Directives: deprecated, include, skip, specifiedBy (total: 4)
Exposing Swagger/OpenAPI documentation is primarily a risk if your API has underlying security flaws, as it gives attackers a precise roadmap to find them.
Those detail every endpoint, parameter, and data model, making it easier to discover and exploit vulnerabilities like broken access control or injection points.
While a perfectly secure API mitigates the danger, protecting your documentation is a critical layer of defense that forces attackers to work without a map.
Severity: info
Fingerprint: 5733ddf49ff49cd1aad035491a3b826fe90d52a7828489390e322c04d392f223
Public Swagger UI/API detected at path: /swagger/index.html - sample paths: DELETE /api/v1/TestRemoveAll GET /api/TestSplunk/ping GET /api/v1/AccountID GET /api/v1/AllPushNotifications GET /api/v1/AppVersionCheck GET /api/v1/B2CInstance GET /api/v1/Clean GET /api/v1/CustomerAccounts GET /api/v1/Devices GET /api/v1/EligibleItems GET /api/v1/EquipmentDBA GET /api/v1/FeaturedArticles GET /api/v1/MasksAndDevices GET /api/v1/MySupportTeam GET /api/v1/Notifications GET /api/v1/Notify GET /api/v1/PAPComplianceStatus GET /api/v1/PatientCommPreferences GET /api/v1/PatientIds GET /api/v1/PatientProfile GET /api/v1/SentNotifications GET /api/v1/ShippingAddressReorder GET /api/v1/TestAllPushNotifications GET /api/v1/TestAuthorization GET /api/v1/TestGetAll GET /api/v1/TestGetNew GET /api/v1/TestNoAuthorization GET /api/v1/TestNotify GET /api/v1/UsageDataResmed GET /api/v1/UsageDataRespironics GET /api/v1/ValidateUser GET /api/v1/ValidateUserB2C POST /api/v1/AddContact POST /api/v1/DisconnectDevice POST /api/v1/Order POST /api/v1/PatientDevice POST /api/v1/RecurringOrderAgreement POST /api/v1/ReportAProblem POST /api/v1/RequestAccountDelete POST /api/v1/SendOTP POST /api/v1/SendOTPPhoneCall POST /api/v1/SendOTPSms POST /api/v1/SignTermsAndConditions PUT /api/v1/Contacts PUT /api/v1/InsuranceCoverage PUT /api/v1/NotificationStatus PUT /api/v1/RemoveAllRONotifications PUT /api/v1/ShippingAddress PUT /api/v1/TestResetNotificationStatuses PUT /api/v1/TestResetNotificationStatusesForPatient
Exposing Swagger/OpenAPI documentation is primarily a risk if your API has underlying security flaws, as it gives attackers a precise roadmap to find them.
Those detail every endpoint, parameter, and data model, making it easier to discover and exploit vulnerabilities like broken access control or injection points.
While a perfectly secure API mitigates the danger, protecting your documentation is a critical layer of defense that forces attackers to work without a map.
Severity: info
Fingerprint: 5733ddf49ff49cd1aad03549115947422cebc70c8317dd1ba833674224b0b168
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
GET /api/v1/DobAllowed
GET /api/v1/GoogleApiKey
GET /api/v1/Logs
GET /api/v1/Message
GET /api/v1/ResendSmsInfo
POST /api/v1/DeliveryTimes
POST /api/v1/DobZip
POST /api/v1/Log
POST /api/v1/NewShippingAddress
POST /api/v1/OneTimeLink/{urlParam}
POST /api/v1/Order
POST /api/v1/PhoneNumber
POST /api/v1/PhoneNumberQr
POST /api/v1/SendEmailToForeignBranches
Severity: info
Fingerprint: 5733ddf49ff49cd1f3d88d6012d166df3ac6754165b3d84243ec20255fc481f9
Public Swagger UI/API detected at path: /swagger/v1/swagger.json - sample paths:
GET /api/v1/DobAllowed
GET /api/v1/GoogleApiKey
GET /api/v1/Logs
GET /api/v1/Message
GET /api/v1/ResendSmsInfo
POST /api/v1/DeliveryTimes
POST /api/v1/DobZip
POST /api/v1/Log
POST /api/v1/NewShippingAddress
POST /api/v1/OneTimeLink/{urlParam}
POST /api/v1/Order
POST /api/v1/PhoneNumber
POST /api/v1/PhoneNumberQr
POST /api/v1/SendEmailToForeignBranches
Exposing Swagger/OpenAPI documentation is primarily a risk if your API has underlying security flaws, as it gives attackers a precise roadmap to find them.
Those detail every endpoint, parameter, and data model, making it easier to discover and exploit vulnerabilities like broken access control or injection points.
While a perfectly secure API mitigates the danger, protecting your documentation is a critical layer of defense that forces attackers to work without a map.
Severity: info
Fingerprint: 5733ddf49ff49cd1aad035491a3b826fe90d52a7828489390e322c04d392f223
Public Swagger UI/API detected at path: /swagger/index.html - sample paths: DELETE /api/v1/TestRemoveAll GET /api/TestSplunk/ping GET /api/v1/AccountID GET /api/v1/AllPushNotifications GET /api/v1/AppVersionCheck GET /api/v1/B2CInstance GET /api/v1/Clean GET /api/v1/CustomerAccounts GET /api/v1/Devices GET /api/v1/EligibleItems GET /api/v1/EquipmentDBA GET /api/v1/FeaturedArticles GET /api/v1/MasksAndDevices GET /api/v1/MySupportTeam GET /api/v1/Notifications GET /api/v1/Notify GET /api/v1/PAPComplianceStatus GET /api/v1/PatientCommPreferences GET /api/v1/PatientIds GET /api/v1/PatientProfile GET /api/v1/SentNotifications GET /api/v1/ShippingAddressReorder GET /api/v1/TestAllPushNotifications GET /api/v1/TestAuthorization GET /api/v1/TestGetAll GET /api/v1/TestGetNew GET /api/v1/TestNoAuthorization GET /api/v1/TestNotify GET /api/v1/UsageDataResmed GET /api/v1/UsageDataRespironics GET /api/v1/ValidateUser GET /api/v1/ValidateUserB2C POST /api/v1/AddContact POST /api/v1/DisconnectDevice POST /api/v1/Order POST /api/v1/PatientDevice POST /api/v1/RecurringOrderAgreement POST /api/v1/ReportAProblem POST /api/v1/RequestAccountDelete POST /api/v1/SendOTP POST /api/v1/SendOTPPhoneCall POST /api/v1/SendOTPSms POST /api/v1/SignTermsAndConditions PUT /api/v1/Contacts PUT /api/v1/InsuranceCoverage PUT /api/v1/NotificationStatus PUT /api/v1/RemoveAllRONotifications PUT /api/v1/ShippingAddress PUT /api/v1/TestResetNotificationStatuses PUT /api/v1/TestResetNotificationStatusesForPatient
Exposing Swagger/OpenAPI documentation is primarily a risk if your API has underlying security flaws, as it gives attackers a precise roadmap to find them.
Those detail every endpoint, parameter, and data model, making it easier to discover and exploit vulnerabilities like broken access control or injection points.
While a perfectly secure API mitigates the danger, protecting your documentation is a critical layer of defense that forces attackers to work without a map.
Severity: info
Fingerprint: 5733ddf49ff49cd1aad0354926859dfa59193e65816ca82f029ea57c387ea33e
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
DELETE /users/{userId}
DELETE /users/{userId}/brands/{brandId}
DELETE /users/{userId}/roles/{role}
GET /dashboard/projects/measurements/monthly-counts
GET /dashboard/projects/total-count
GET /dashboard/projects/watch-counts
GET /dashboard/watches/total-count
GET /downloads/brands/{brandId}/measurements
GET /downloads/projects/{projectId}/measurements
GET /downloads/watches/{watchId}/measurements
GET /masterdata/brands
GET /masterdata/project-statuses
GET /masterdata/roles
GET /measurements
GET /measurements/paginated
GET /measurements/{measurementId}
GET /measurements/{measurementId}/picture
GET /networktime
GET /projects
GET /projects/{id}
GET /projects/{projectId}/testers
GET /users
GET /users/entra-search
GET /users/external-readers
GET /users/my-brands
GET /version
GET /watches
GET /watches/{watchId}
POST /projects/{projectId}/external-readers
POST /users/{userId}/brands
POST /users/{userId}/reinvite
POST /users/{userId}/roles
PUT /projects/{projectId}
PUT /users/{userId}/disable
PUT /users/{userId}/enable
Severity: info
Fingerprint: 5733ddf49ff49cd1aad0354926859dfa59193e65816ca82f029ea57c9ebf8859
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
DELETE /users/{userId}
DELETE /users/{userId}/brands/{brandId}
DELETE /users/{userId}/roles/{role}
GET /dashboard/projects/measurements/monthly-counts
GET /dashboard/projects/total-count
GET /dashboard/projects/watch-counts
GET /dashboard/watches/total-count
GET /downloads/brands/{brandId}/measurements
GET /downloads/projects/{projectId}/measurements
GET /downloads/watches/{watchId}/measurements
GET /masterdata/brands
GET /masterdata/project-statuses
GET /masterdata/roles
GET /measurements
GET /measurements/paginated
GET /measurements/{measurementId}/picture
GET /networktime
GET /projects
GET /projects/{id}
GET /projects/{projectId}/testers
GET /users
GET /users/entra-search
GET /users/external-readers
GET /users/my-brands
GET /version
GET /watches
GET /watches/{watchId}
POST /projects/{projectId}/external-readers
POST /users/{userId}/brands
POST /users/{userId}/reinvite
POST /users/{userId}/roles
PUT /measurements/{measurementId}
PUT /projects/{projectId}
PUT /users/{userId}/disable
PUT /users/{userId}/enable
Exposing Swagger/OpenAPI documentation is primarily a risk if your API has underlying security flaws, as it gives attackers a precise roadmap to find them.
Those detail every endpoint, parameter, and data model, making it easier to discover and exploit vulnerabilities like broken access control or injection points.
While a perfectly secure API mitigates the danger, protecting your documentation is a critical layer of defense that forces attackers to work without a map.
Severity: info
Fingerprint: 5733ddf49ff49cd1aad03549eb310bffbcade90f346cf10b9d81a7ad3e8796cf
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
DELETE /api/Pairs/devices/{deviceId}/shops/{shopId}
DELETE /api/Pairs/{shopDevicePairId}
GET /api/Health
GET /api/Notifications/current
GET /api/Pairs/device/{deviceTokenId}
GET /api/Pairs/shop/{shopId}
GET /api/Products/search/{pattern}
GET /api/Products/{reference}/picture
GET /api/QRCode/{shopId}
GET /api/QRCode/{shopId}/reset
GET /api/WarrantyCheck/{brandCode}/{id}
POST /api/Token/device
POST /api/Token/device/refresh
POST /api/transactional-data/manage-sellout
Severity: info
Fingerprint: 5733ddf49ff49cd1aad03549eb310bffbcade90f346cf10b9d81a7ad6484877f
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
DELETE /api/Pairs/devices/{deviceId}/shops/{shopId}
DELETE /api/Pairs/{shopDevicePairId}
GET /api/Health
GET /api/Notifications/current
GET /api/Pairs/device/{deviceTokenId}
GET /api/Pairs/shop/{shopId}
GET /api/Products/{brandCode}/search/{pattern}
GET /api/Products/{reference}/picture
GET /api/QRCode/{shopId}
GET /api/QRCode/{shopId}/reset
GET /api/WarrantyCheck/{brandCode}/{id}
POST /api/Token/device
POST /api/Token/device/refresh
POST /api/transactional-data/manage-sellout/device-id/{deviceId}
Exposing Swagger/OpenAPI documentation is primarily a risk if your API has underlying security flaws, as it gives attackers a precise roadmap to find them.
Those detail every endpoint, parameter, and data model, making it easier to discover and exploit vulnerabilities like broken access control or injection points.
While a perfectly secure API mitigates the danger, protecting your documentation is a critical layer of defense that forces attackers to work without a map.
Severity: info
Fingerprint: 5733ddf49ff49cd1aad03549eb310bffbcade90f346cf10b9d81a7ad3e8796cf
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
DELETE /api/Pairs/devices/{deviceId}/shops/{shopId}
DELETE /api/Pairs/{shopDevicePairId}
GET /api/Health
GET /api/Notifications/current
GET /api/Pairs/device/{deviceTokenId}
GET /api/Pairs/shop/{shopId}
GET /api/Products/search/{pattern}
GET /api/Products/{reference}/picture
GET /api/QRCode/{shopId}
GET /api/QRCode/{shopId}/reset
GET /api/WarrantyCheck/{brandCode}/{id}
POST /api/Token/device
POST /api/Token/device/refresh
POST /api/transactional-data/manage-sellout
Severity: info
Fingerprint: 5733ddf49ff49cd1aad03549eb310bffbcade90f346cf10b9d81a7ad6484877f
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
DELETE /api/Pairs/devices/{deviceId}/shops/{shopId}
DELETE /api/Pairs/{shopDevicePairId}
GET /api/Health
GET /api/Notifications/current
GET /api/Pairs/device/{deviceTokenId}
GET /api/Pairs/shop/{shopId}
GET /api/Products/{brandCode}/search/{pattern}
GET /api/Products/{reference}/picture
GET /api/QRCode/{shopId}
GET /api/QRCode/{shopId}/reset
GET /api/WarrantyCheck/{brandCode}/{id}
POST /api/Token/device
POST /api/Token/device/refresh
POST /api/transactional-data/manage-sellout/device-id/{deviceId}
Exposing Swagger/OpenAPI documentation is primarily a risk if your API has underlying security flaws, as it gives attackers a precise roadmap to find them.
Those detail every endpoint, parameter, and data model, making it easier to discover and exploit vulnerabilities like broken access control or injection points.
While a perfectly secure API mitigates the danger, protecting your documentation is a critical layer of defense that forces attackers to work without a map.
Severity: info
Fingerprint: 5733ddf49ff49cd1f3d88d6081c9af56d33546ee65ee64a061f27b274e929d9a
Public Swagger UI/API detected at path: /swagger/v1/swagger.json - sample paths: GET /disruptions/GetMessages GET /disruptions/Status GET /disruptions/cache/Clear GET /disruptions/cache/Read GET /notifications/GetNotifications GET /notifications/cache/Clear GET /notifications/cache/Read GET /stations/GetClosestStation GET /stations/GetStation GET /stations/GetStationSE POST /emailconsents
Exposing Swagger/OpenAPI documentation is primarily a risk if your API has underlying security flaws, as it gives attackers a precise roadmap to find them.
Those detail every endpoint, parameter, and data model, making it easier to discover and exploit vulnerabilities like broken access control or injection points.
While a perfectly secure API mitigates the danger, protecting your documentation is a critical layer of defense that forces attackers to work without a map.
Severity: info
Fingerprint: 5733ddf49ff49cd12ec8532c2ec8532c2ec8532c2ec8532c2ec8532c2ec8532c
Public Swagger UI/API detected at path: /swagger/index.html
The following URL (usually /.git/config) is publicly accessible and is leaking source code and repository configuration.
Severity: medium
Fingerprint: 2580fa947178c88602b1737db148c044b81b03713d63bb82370a6522fbf5dbd7
[core] repositoryformatversion = 0 filemode = true bare = false logallrefupdates = true [remote "origin"] url = https://github.com/christian-dior-couture/sch-diorstar-h5 fetch = +refs/heads/*:refs/remotes/origin/* [gc] auto = 0 [http "https://github.com/"] extraheader = AUTHORIZATION: basic eC1hY2Nlc3MtdG9rZW46Z2hzX1hQUW50RXc4QjVjSmE3V3MyZFk2OUNISE5DRm0wNDBDd3RsVg== [branch "develop"] remote = origin merge = refs/heads/develop
Severity: medium
Fingerprint: 2580fa947178c88602b1737db148c044b81b03713d63bb82370a65224532fe2f
[core] repositoryformatversion = 0 filemode = true bare = false logallrefupdates = true [remote "origin"] url = https://github.com/christian-dior-couture/sch-diorstar-h5 fetch = +refs/heads/*:refs/remotes/origin/* [gc] auto = 0 [http "https://github.com/"] extraheader = AUTHORIZATION: basic eC1hY2Nlc3MtdG9rZW46Z2hzX3NiVDlucE0wTW50bFpobDJGS2ZaSGQ5WHRqZWJzTTBkbVRURQ== [branch "release/1.9.1"] remote = origin merge = refs/heads/release/1.9.1
Severity: medium
Fingerprint: 2580fa947178c88602b1737db148c044b81b03713d63bb82370a6522cdab6cf9
[core] repositoryformatversion = 0 filemode = true bare = false logallrefupdates = true [remote "origin"] url = https://github.com/christian-dior-couture/sch-diorstar-h5 fetch = +refs/heads/*:refs/remotes/origin/* [gc] auto = 0 [http "https://github.com/"] extraheader = AUTHORIZATION: basic eC1hY2Nlc3MtdG9rZW46Z2hzX0pxcFJkeVBWaTNCM3dFTmZnbzkzc2lNMDRQREFGYTRKQXd2Mg== [branch "develop"] remote = origin merge = refs/heads/develop
Severity: medium
Fingerprint: 2580fa947178c88602b1737db148c044b81b03713d63bb82370a65229343de62
[core] repositoryformatversion = 0 filemode = true bare = false logallrefupdates = true [remote "origin"] url = https://github.com/christian-dior-couture/sch-diorstar-h5 fetch = +refs/heads/*:refs/remotes/origin/* [gc] auto = 0 [http "https://github.com/"] extraheader = AUTHORIZATION: basic eC1hY2Nlc3MtdG9rZW46Z2hzX3Q2bmVkR212WWptWmtjcGFwVUlFVnZ6bTZsZGdmODFaYnc5aQ== [branch "develop"] remote = origin merge = refs/heads/develop
Severity: medium
Fingerprint: 2580fa947178c88602b1737db148c044b81b03713d63bb82370a6522f0fff41d
[core] repositoryformatversion = 0 filemode = true bare = false logallrefupdates = true [remote "origin"] url = https://github.com/christian-dior-couture/sch-diorstar-h5 fetch = +refs/heads/*:refs/remotes/origin/* [gc] auto = 0 [http "https://github.com/"] extraheader = AUTHORIZATION: basic eC1hY2Nlc3MtdG9rZW46Z2hzXzVQYzdPVXFDRTJjeGNTdzlmQ1dsQm1qTDVxcUF3TTF2dDNqaQ== [branch "develop"] remote = origin merge = refs/heads/develop
dev-app-diorstarwechat.christiandior.cn 5 myst-devb.lincare.com 3 text2order-api-uat.lincare.com 2 chronos-api-qual.swatchgroup.biz 2 konnector-dev.swatchgroup.com 2 konnector-stg.swatchgroup.com 2 www.preprod1.dominos.com 1 myst-uatb.lincare.com 1 myst-tstb.lincare.com 1 api-combined-messages.southeasternrailway.co.uk 1 uat-storemgmt-racpad.rentacenter.com 1